Merged PR census: 3 / 15 / 73 / 92 across October 1–7 / 8–14 / 15–21 / 22–31. The count includes mirror, CI, tests and documentation—not 183 user-facing features or a measure of effort. Final CI jobs means Validate, deployed-stage E2E and Deploy Production in one exact build. No monthly line-churn total is asserted.
-The final October merge, ceffbf327, completed CI at 19:45:36 UTC on October 31. Validate, deployed-stage E2E and Deploy Production all succeeded. This supersedes the earlier pending #397 snapshot and the failed intermediate #369 run.
It proves those jobs ran successfully—not independent production browser acceptance, package installation, or owner approval.
GitHub release records were observed for 0.2.0 and 0.2.1 on October 14, 0.2.2 on October 26 and 0.2.3 on October 29. Seven packages have 0.2.3 records.
Later merged conversion, upgrade and preview work must not be described as a verified new package release. No independent npm install was performed for this report.
The repository evidence establishes specific builds and test outcomes, not completion of the entire connect → edit → save → preview → publish journey across all supported environments. The remaining open PRs and package rollout conditions must be assessed separately.
#362 remained open with a new October 31 head: validation passed, but deployed-stage E2E failed. #363 remained an open draft despite successful exact-head CI. Neither is counted as a merged October result.
Mirror workflow and test configuration were repaired; preview-session diagnostics were added without claiming a behavior fix. The separate landing integration supplied CMS blocks, routes and shared site data for a more representative editing surface.
Billing-off removed an unmet production dependency while retaining billing coverage in staging. Public cloud-astro packaging expanded what users could install. Two regression batches then repaired rich text, fragments, indexing and related behavior found in 0.2.0; #210’s validation and deployed-stage E2E were independently checked.
The focus moved to writes: tab isolation, safe Git commits, non-overwriting media moves and correct MDX write-back. Refresh and workspace security received targeted fixes. Generated Typia contracts and repository commands through rig.yaml improved consistency, but did not finish the separate StateBus migration.
Invite routing, page state, block actions and undo gained corrections and regression coverage. GitHub authority was reconciled with existing workspaces, not just fresh previews. The How it works site update landed after browser proof; dependency-review and mirror workflows moved to a self-hosted pool.
Keyless editing was followed by sharing, static-site previews, agent tooling and consistent media processing. GitHub reinstall recovery and large-push handling addressed operational failures. After 15:24 UTC, #398 added queued imports, #400 added a doctor warning and #401 fixed a DOM-test teardown race. The final default-branch CI and production job succeeded before the month closed.
Evidence is classified by what was actually read. Historical PR proof is useful, but it is not a new run of the product. No review-round counts or approval claims have been reconstructed from incomplete records.
-| Area | Observed proof | Boundary / next check |
|---|---|---|
| Write isolation | PR #224: exact-head Validate and deployed-stage E2E passed. CI evidence. | Confirms that tested snapshot, not every later build or all multi-tab environments. |
| Content parsing | PR #239 reports red/green regressions; successful Validate and deployed-stage E2E were checked independently. CI evidence. | This verifies a specific hardening change, not closure of the entire security backlog. |
| Keyless editor | PR #344 reports Chromium/Firefox/WebKit, static-output parity and draft-preview proof; exact-head validation/E2E passed. CI evidence. | Live Vercel was not exercised; reported cold-open time was 6–7 seconds against a three-second target. |
| Docs/gallery #362 | Head aa056647, committed October 31 at 21:46 UTC: Validate succeeded, deployed-stage E2E failed and production was skipped. The log shows an editor-page assertion timing out. Failed E2E job. | Still open. The earlier lint/artifact failure is historical, not the current blocker. A fresh stage was deployed in this run; its current browser availability was not tested. |
| Publish summary #363 | Head 76bb09e: Validate and deployed-stage E2E succeeded; production skipped. Exact-head CI. PR reports 52 Nx tasks, 226 Storybook tests and 162 real-Git-runtime tests. | Still an open draft. Preview expired October 30; authenticated publication and team acceptance remain unestablished. |
| Final pipeline | ceffbf327: Validate, deployed-stage E2E and production deployment all succeeded. Final October run. | Do not infer owner acceptance, customer-site upgrades or new public package publication from CI success. |
The next coordinated package release and real-site upgrade checks remain necessary. Repository quotas were implemented without enabling a quota value in that PR. The affected repository’s recovery, preview-site updates and sender-domain readiness require operational confirmation.
StateBus #84 remained an open draft in the collected evidence; full-page docs preview is still unavailable. Evidence retention also remains a separate issue: a path in a log or a green job is not proof that screenshots are retrievable now.
The expandable rows below are a deliberately small, verified sample: two files from #197, one from #398 and one from #400. Counts are per-PR diffs, not month-wide unique-file totals. Links point to inspected lines at the final October default-branch commit. This avoids inventing a monthly diff from a PR census.
A navigable selection of real merge commits behind this narrative. Captions describe the associated PRs; this is not a complete commit log.
The following records summarize decisions evidenced by merged PRs. They are report summaries—not newly ratified project ADRs.
The verified merged-PR author counts are 89 for alex-mextner, 80 for NikoT2 and 14 for other authors. These are repository authorship counts—not sole-credit, personal activity or effort measurements. PR census.
The separate October 6 landing/CMS integration and How it works website update are credited through their repository records rather than private correspondence. No customer-acquisition, revenue or campaign result is asserted.
Recommendations from the evidence gaps—not new commitments assigned to the team.
Source context: PR #362 · PR #363 · PR #377 · PR #395 · PR #320.
Reporting window: October 1–31, 2026 (UTC). The original repository evidence ended at October 31, 15:24 UTC. A targeted November 1 read-only refresh covered all October 31 merged PR search results, selected exact-head/default-branch workflows and the latest public GitHub releases. It added three merges and replaced stale pending/failed-build descriptions with their terminal outcomes.
Repository evidence includes the month’s PR census, 66 directly checked PR records in the original evidence set, selected jobs, public release records and the landing commit. This report is a selective technical synthesis, not an exhaustive audit of every branch, ticket, deployment or user scenario. No new product tests, npm installation, production browser audit, business-metric estimate or screenshot recapture was performed.
Some repository evidence links are access-controlled and require permission to view. This public report contains no private correspondence, customer identifiers, credentials or detailed security exploit mechanisms. Merge, release, deployment and product acceptance remain distinct evidence levels.
+ Restored block dragging and Undo after adding a block. Dashboard + New Page opens the create dialog. New unpublished pages display + Draft, including after translation edits. +
+ ++ Invites open the workspace the user joined. Writes stay on the + repository, branch and site shown in their tab, even when another + tab changes workspace. +
+ ++ CMS commits preserve unrelated staged files. Asset moves do not + overwrite an existing file. Draft images render in the canvas, and + primary-root MDX saves return to the original file. +
+ ++ Integrated Saba’s completed design into the production site. Added + responsive, enlarged-text and reduced-motion checks, and removed + the visible jump during delayed hydration. +
++ #342 + · Production +
++ Added standalone CMS and composed app catalogues, interactive + state stories, desktop/mobile captures, and deployed-stage checks + for editor routes and primary actions. +
++ #217 + · + #244 + · + #226 + · + #300 + · + #304 + · + #309 +
++ Current preview, 5 November. Separate from the October merges above. +
++ Added Light, Dark and System controls with visible selection, + keyboard navigation and touch targets. Current-head CI and + deployed-stage E2E passed; the implementation awaits team approval. +
++ #489 + · + Preview + · + Deployed E2E +
++ Theme control on production and PR #489, captured at the same 1440px + viewport on 5 November. The new control is on the preview only. +
+
+ 
+ + Protected Storybook: + Main + · + Publisher preview #404 + · + Theme-picker preview #489. Forge sign-in is required. +
++ Published these catalogue snapshots and added their links to PR + descriptions. The publisher and automatic link refresh are implemented + in + #404 + and + #509; both await merge approval. +
++ Publisher deployed-stage E2E. PR #404 includes the sandbox-path fix for prefixed catalogues; Main + tracks the merged branch. +
++ How it works: production deployment and E2E + · + Interactive Storybook scenarios and screenshot workflow + · + Theme-picker deployed-stage E2E. +
+These eleven PRs have October merged_at timestamps. Merge metadata takes precedence over stale “not merged” wording in PR descriptions. Counts are limited to this repository and window; no file, line or commit totals are inferred by adding overlapping PR diffs.
| UTC date | PR | Integrated result | Merge SHA |
|---|---|---|---|
| 10-14 | #810 | Headless async toolkit and bounded, fail-closed package export. | da611247 |
| 10-16 | #825 | Extension 0.1.75 version and changelog cut. | b0c3a512 |
| 10-30 | #837 | Dependency updates and bounded MCP request handling. | ecd0b8f1 |
| 10-30 | #807 | API docs preserve ordinary names that resemble compiler symbols. | f32c4cf9 |
| 10-30 | #802 | Generated immutable commands, shared publication/history and full-entry budgets. | 659d9ef4 |
| 10-30 | #826 | Operation authority prevents stale work from publishing another owner’s state or feedback. | 5acccf19 |
| 10-30 | #803 | Validated immutable record adapter using the existing Runtime. | f862a797 |
| 10-30 | #832 | Whole-entry specialization, immutable save capture and keyed-row completion updates. | b1723e89 |
| 10-30 | #833 | Checked keyed-row patch boundary for actual text edits. | 6002c639 |
| 10-30 | #834 | Certified cold JSON import without an extra whole-document clone. | 4568a6b3 |
| 10-31 | #809 | Multi-file live examples, browser compilation and traceable benchmark tooling. | 7669cfbd |
Author accounts in this verified set: alex-mextner on eight PRs and smoothbricker on three. Account names are not silently mapped to people or used as a complete contribution census.
#823 at a4caec76 separates read-only selection observation from mutation authority, keeps newer selection from being overwritten by an earlier move, and preserves manual text around move/save. AI recovery remains read-only and starts only after an explicit Fix with AI click.
The source-bound result manifest records byte-exact restore, selection retention and zero AI requests before the click versus one afterward. The PR records 188 focused tests, 13/13 native assertion sets and ten consecutive typing → move/write → typing → save scenarios. CI run 38942173036 independently reports success for this head. These are historical proofs, not a fresh VS Code run in this reporting pass.
Remaining: integrate the stacked branch, reassess its current release readiness, and complete real host/SaaS, Undo/Redo and overall product acceptance. The linked typing/selection screenshot is an existing artifact; it was not visually re-inspected for this report.
#831 moves 36 style values from root-panel state to section-local subscriptions. Its 17 October source-bound report measures the same controlled Inspector workflow at source e8dd27e4.
| Metric | Parent | Field-local candidate |
|---|---|---|
| Root-panel calls per 1,000 edits | 1,013 | 13 |
| Whole-layout calls per 1,000 edits | 1,001 | 2 |
| Main-thread work per 1,000 edits, CPU ×1 | 1,314.97 ms | 799.52 ms |
| Application + added library code | 3,282 lines | 3,191 lines |
| Actual right-webview gzip | 373,130 B | 375,534 B |
Interpretation: the tested stress workflow does less broad UI work, but total code savings are small and the bundle grows. An equally localized native control is comparable; the equal-eight-write comparison does not establish a CPU advantage. This is not measured physical typing latency, developer productivity or live AST/HMR acceptance.
#822 adds real issue-completion checkboxes, separate selection, focus restoration and duplicate-action protection. The PR describes Chromium/WebKit coverage, but its final full gate and deployed-lab acceptance are not established here. The latest metadata shows it still open at 20ef733c, now targeting main after #809 merged; older stacked-branch wording is not used as current status.
#832 integrates complete-entry specialization and work elimination. Its research report reports completion-handler medians at 1,200 visible Boards rows of 63.2 → 1.0 ms in Chromium and 93 → 1 ms in WebKit. The comparison uses pinned application artifacts and a synthetic API. It does not cover the entire edit/move/Undo/Redo workflow or production traffic.
The cost is retained: the complete state-lib entry is 42,166 gzip bytes versus 37,132 for the equally optimized baseline; small fixtures retain extra heap. Handler and next-frame timings are not field INP or completed paint. The historical measurements were not rerun after the 30 October replay. Its replay note lists focused compiler/Node/site checks and explicitly says eight Wasm contracts were not run.
Engineering approach: preserve one Runtime; make operation ownership explicit; compare complete application entries and retain adverse results. Upstream library integration does not close the separate application-adoption and staging tasks.
Evidence is separated into repository state, historical test execution and delivery acceptance. No product test suite or benchmark was newly executed to prepare this report.
CI and Security Scan passed. The actual Tests job log was read in the prior evidence pass: 7,834 app passed, 7 skipped, 0 failed; 1,040 native passed; all 79 site gates passed.
Those counts belong to tested merge-ref 1d526fb9 (head d4cca87 plus base 81d0b05), not all later main revisions. The PR records explicit owner acceptance for its bounded reviewed tree; it is not blanket acceptance of the month’s work.
The refresh confirms CI run 41059658812 and six other returned workflows failed at #837 head 539fe4c. CI run 41236201667 and six other returned workflows also failed at #809 head ecd65533.
#837 describes a local verification fallback. The precise hosted failure cause was not independently established from job annotations here. A merged branch or a PR’s local verification narrative is not labeled as passing hosted CI.
#825 is merged. Its reported E2E matrix is 1,815 passed, 26 failed, 33 flaky, 1,228 skipped; this is not a fully green matrix. The PR attributes failures to pre-existing issues or flakes, and documents false-positive multi-select checks in the older version.
Registry APIs/pages in the prior check did not yield usable proof of both stores’ actual 0.1.75 versions. Publish run, release SHA and both registry versions remain to be reconciled.
Canvas #823 and Inspector #831 are open, even where saved tests or CI are green. Companion harness #169 also remained an independent open PR in the previous evidence snapshot.
Fresh tree-specific readiness checks and human acceptance remain required before a new production release of the product. The report does not establish that those gates have been completed.
Core evidence: GitHub PR metadata, selected source-bound reports/manifests and historical CI results from hyperide/hyper-saas. The 1 November refresh confirmed all eleven October merges and the highlighted candidate states. An October-updated-PR search for alex-mextner/hyper-canvas-draft returned no matches; this is not a claim of no commits or no work there.
No unrelated bot projects, rig results or conloca results are included. No total LOC, file count, review count, productivity percentage or universal completion claim is invented. Evidence links may require repository access. The findings do not establish a new product deployment or blanket product acceptance.
+ Updated the extension version and changelog. The release + preparation is merged into main. +
++ #825 +
++ Updated the extension and root dependencies, added dependency + regression tests, and bounded MCP request handling. +
++ #837 +
++ Bound push credentials to the checked project, preserved its + transport settings, and kept authentication failures out of raw + logs. This was part of #810, alongside the toolkit and docs + changes in the StateLib report. +
++ #810 +
++ The async toolkit, immutable records, operation ownership, + complete-entry compiler and cold-import changes are covered in the + separate StateLib report. +
++ The + tests, types and extension build + and + security scan + passed for the merged #810 change. +
++ Added framework-neutral async state and validated immutable + records on the existing Runtime. Production and testing exports + are separate. +
+ ++ Prevented superseded async work from publishing state or feedback + under a newer operation. +
++ #826 +
++ Added fixed-entry compilation and output rollback. Immutable save + capture and keyed-row completion updates avoid redundant document + work. +
++ #832 +
++ Certified a JSON field while importing it, then adopted that exact + root. The normal copying replace API keeps its existing behavior. +
++ #834 +
++ Preserved ordinary API names in generated docs and fixed quoted + attributes leaking into diagram captions. +
+ ++ Diagram caption rendering, captured for #810. The same fixture now + displays the label without leaking attribute text. +
+
+ 
b"> appears in the caption.
+ 
+ + Original browser captures from 14 October, retained with + #810. +
++ Documentation browser tests + · + Runtime, types and build checks. Source and test details for compilation and import are attached to + #832 + and + #834. +
+