rdmsm4x-changelog-20260902-1959-tyrell-build15-ecs0-persistence-adoption-plan

Recorded an owner-gated, read-only plan for a future Tyrell ECS0 pooled-SQLite adoption so no unpublished upstream candidate is mistaken for a runtime migration.

Scope

• Host: rdmsm4x only.
• Read-only inputs: Build 14 Tyrell at dac86cace5326e7c12baa5ce780391aa4a6003a4 and isolated ECS0 pool candidate 1d82123f3a222489a319cec816c30a41a35a9dde.
• No database, daemon, application, package publication, canonical source, credential, or service was changed.

Files written by this planning task

• /Users/richh/dev/_handoff/tyrell-build15-ecs0-persistence-adoption-plan-20260902.md
• /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-tyrell-build15-ecs0-persistence-adoption-20260902.json
• This changelog file.

Evidence and outcome

• Ticket TASK-20260902-10 was opened, claimed, heartbeated, and resolved with raw commit, ancestry, call-surface, and preservation evidence.
• Build 14’s concrete store has 27 read and 16 write closures over Tyrell’s single locked native SQLite handle. Its schema and authority code remain Tyrell-owned.
• The isolated pool candidate is not reachable from canonical ecs0lib HEAD. Its closure-scoped API cannot safely substitute for Build 14’s raw-handle, multi-statement DDL, and automatic immediate-transaction facade without a real Tyrell adapter and upstream publication.
• Decision: no source-only adapter or adoption claim. The handoff records the smallest future Tyrell-owned adapter, required tests, data snapshot procedure, rollback, and publication gate.
• Handoff SHA-256: 2c4fada9c14ce5f37805a955312a20d3fcbc5148cb6b75ff13eaaa680ea827fb.

Preservation and rollback

• Canonical ecs0lib’s six ownerless untracked path entries containing 14 files were not touched.
• Build 14 was initially clean; four later root-owned post-audit hardening modifications were preserved untouched and excluded from the persistence baseline.
• There is no source commit, database mutation, or runtime action to roll back. To undo this planning record, retain or ignore the handoff/check-in/changelog; do not delete another owner’s worktree or canonical files.

Outstanding owner action

The ecs0lib owner must accept and publish the pooled-SQLite candidate (or successor) to canonical ecs0lib. The Tyrell owner must then approve a fresh isolated implementation worktree and a temporary-database compatibility/concurrency validation before any runtime selection.