2026-09-24 — automated release verified; manual review pending

Corrected production API 0693e0f, RTC source 068c1eac, CLI 0.26.2 (dcd17050) and Python 0.20.0 (ef1d353) are deployed/published. Fresh public package integrity/install checks, hosted docs and extracted skill files, live released-client core/HTML checks, and four paired CLI/Python MERGE/EXACT examples passed. Public skills PR30 merged 3c3d55c and a fresh isolated installation passed 39 file checks and seven generator tests.

The frozen live pilot completed 100/100 acknowledged edits, 50 per format, across ten private fixtures. Every edit used one upload and passed source and native identity checks. Plan SHA256 remains 577376fb23110cd7baec52451fe89f73bb295aff118b927db31f396008c3ae8f. Actual live proof is 2026-09-24-pilot-run.json and pilot-evidence.json in dreamlake-server/docs/notes-acceptance/. The separate automated validator reports liveChecksPerformed: false because it validates recorded evidence; it is not the live execution. No extra pilot writes were repeated for closure.

The manifest is automated-verified-manual-pending. Browser concurrent writers, rich references/assets, source round trips, menu/keyboard boundaries and heading surface parity remain for the user's production review. Receipts are coherent post-acknowledgement observations, not an assertion that all peers are synced or that a revision stays current. Performance measurements retain their documented scope; no universal zero-slowdown claim is made.

Release PR715 links the manifest and sanitized receipts. Master Note/issue706 reflect the released contract. This closure changes internal evidence and the public-skills submodule pin only; no runtime behavior or end-user procedure changes, so no public skill regeneration is needed for this internal page. Final owning-docs deployment follows the merge; user/global agent reload is not claimed.

Historical implementation record (superseded pending statements)

The following dated entries preserve the implementation-time state. Their pending, unset and no-live-pilot statements are historical, not current status.

2026-09-23 — Notes release acceptance

PR 9 of Notes master plan #706 adds a release manifest and operator acceptance harness. Required RTC SDK/server and CLI releases are explicitly unset until actually published. The manifest fails closed while schema, dependency, docs/skills, deployment and browser compatibility evidence is missing.

The offline benchmark compares generation/parse time, bytes and exact-source validity for both owned formats. Live core acceptance requires a dedicated fixture Note and tests selected-format Bash stdin uploads, exact readback, untouched RTC identities, stale rejection and no-op verification. Alternative format results remain offline; each logical edit commits once.

Owning operator procedure: dreamlake-server/docs/notes-release-acceptance.md. The source module has isolated acceptance tests; actual deployed verification requires fulfilled release gates and a recorded run. The earlier local RTC MongoDB/bridge tests establish rollback/restart, Unicode/disjoint edits and an exactly-one-winner concurrency check, not hosted compatibility.

No public skill impact: this page documents internal release operation, not a new end-user interface. Public Notes/CLI/RTC procedures are owned by their respective feature PRs and must be synchronized and freshly installed before release. Merge, packages, docs deployment, public skill publication, installed readback and live verification remain separate.

Acceptance gap review

PR9 now separates availability preflight from final live-evidence gates. The operator harness verifies registry tarball integrity and actual package identity, fresh Notes/CLI/RTC skill downloads, and both read formats through direct API and CLI read/diff. Offline pilot validation checks the frozen 100-edit plan, private fixture inventory, exact receipts and five manual UI evidence categories. These are acceptance tools and pending evidence requirements, not live receipts. No public-skill impact: this internal noindex development note and server operator harness add no end-user operation or public procedure.

The pilot now has an executable offline planner and gated live driver. Ten distinct private fixtures, 100 deterministic edits and format assignments are frozen before execution. One stdin upload per edit, durable pre-send intent, source/revision checks and native identity checks stop on uncertainty. This implementation and offline rehearsal do not claim a live pilot.

An API-only stage adapter now avoids the CLI-before-API release dependency. It uses a separately created private fixture and released SDK, verifies selected API read formats, stale/no-op behavior, legacy reads and one native committed batch from two same-baseline competitors. Final released-CLI gates stay strict.

2026-09-24 — cumulative deployment with user acceptance afterward

The release operator now has explicit deployment manifest and automated pilot validation phases. All automated evidence remains required, including 100 successful private-fixture edits; pending browser/UI acceptance is reported separately for the user's production test. The default final phase remains strict. No RTC algorithm, persistence or writer coordination is changed. No public skill impact: these are internal release evidence controls only.

A staging run exposed an acceptance-harness mismatch: conditional RTC snapshots return native CRDTMessage[], while the harness inspected persistence-row wrappers. The journal assertion now checks the actual wire contract, rejects missing/duplicate/extra batches, and records the failed phase without exposing private source. Regression tests cover that shape. The earlier fixture remains retained and unverified; corrected acceptance uses a new private fixture. This fix changes no server or RTC runtime behavior.