Tyrell 0.2.0 Build23 — signed candidate, not installed

Build23 fixes a proven activity-event retention defect. It is ready for the coordinator's protected canary; it is not runtime accepted, integrated into main, or deployed. Build21 remains rejected and must not be reinstalled. The separate app-only Build22/PR36 lane is unchanged; its daemon must never deploy.

Owner: codex@rdmsm4x/01a08a70. Next owner: codex@rdmpw3275m/01a078a7. Existing high BUG ISSUE-20260912-01 remains open.

Source and behavior

Source 093d653493be92aed0fb39779f52d5eaef04230b on existing branch codex/tyrell-build21-memory-20260914 in /Users/richh/dev/_handoff/tyrell-build21-memory-20260914/apps/Tyrell. Only five source/test/version files changed: BUILD_NUMBER, Version.swift, ActivityEventBufferActor.swift, SQLiteStateStore.swift, ActivityEventBufferActorTests.swift.

SQLiteStateStore previously persisted every activity event and also appended it to an unpersisted queue with no production drain. The new committed-event path updates the bounded cache after successful SQLite commit without retaining that redundant queue entry. Direct actor writers keep their genuinely pending events. No pending data was trimmed; no schema or gate changed.

Reproducible validation

• swift test --filter committedSQLiteEventsDoNotRemainQueuedForPersistence fails on unchanged be3e664 production sources: pending.isEmpty is false after200 committed events. This is the valid red run; an earlier missing-try test compilation error is separately named and not counted as regression evidence.
• swift test --filter ActivityEventBufferActorTests:8 tests pass, including the real SQLite regression and preservation of pending events through400 committed-cache inserts into a100-entry ring.
• swift test:exit0;553 XCTest reported,2 environment skips,0 failures;666 Swift Testing tests (22+487+65+92),0 failures. Skips: launchd descriptor visibility and remote canary43117 reachability. Log SHA256 08c196df01fb7f1f44218d9de2ebe861815671667a359e32acdde5058c06892d. The unchanged visual fixture used by the suite is included in the frozen packet.
• PYTHONDONTWRITEBYTECODE=1 python3 /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/run-contracts.py:11 suites pass, including the unchanged physical-memory gate contract.
• Independent Terra/high review ACCEPT for exact patch dc933c7a6e9ff0ee32f74d919df81e447b07e761ca2bfda7c12aa0c8b392362b. Review SHA256 7f153c5bc2c32b1005acac02c82c70ca964732b3d104d8c2d4b1d5e08aad3246. Review acceptance is source-lifecycle acceptance only. Its partial test-log observation is superseded by test-receipt.json.
• All16 dependencies used for Build21 retain the same commits; all18 inspected ECS repositories are clean. No library edits or pins changed. Source branch published to backup and fleet.

Signed artifact identity

Both artifacts are universal x86_64/arm64, signed by Developer ID Application: east coast science, llc (ZU2882L4HT), with hardened runtime and trusted timestamps. App notarization 54188fda-19b1-4c58-b3bf-f1732a6da11c and daemon 226fedec-cd54-4a3a-8503-88320daf5679 are Accepted, issues null. App is stapled; strict signature, Gatekeeper and archive round-trip checks pass. App execution --version reports0.2.0(23). The bare daemon is notarized and cannot carry a stapled bundle ticket.

Candidate canonical arm64 CDHash bb1e0064230fc271d4374d08938cc388d488412273430b3e7ae0757829908208. Designated requirement hash remains 9943c03ba47653aab0eacfd8fab8ea70d887d4392fd24832b96bffaa9c502aee.

What remains unproven

Build21's17.42→38.53MiB physical trajectory is not quantitatively attributed to this queue. Most growth is an18MiB step around the first inventory completion at27min, after the10min warm-up. Failure vmmap shows4.6MiB live allocation and22.4MiB fragmentation; a free-page count is not a retained object count. The async JSON replay plateaus and census standalone adds under1MiB on first call. Neither supports claiming a complete allocator cure.

The coordinator must retain the unchanged gate and rollback protections and capture allocation attribution around inventory completion. Candidate creation, notarization, canary acceptance, source integration and fleet deployment remain separate states. No installs, launchd changes, or main/Build22 edits occurred in this lane.

Preservation and next action

Frozen packet: /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/frozen-handoff. It contains exact source archive, source patch, source metadata, artifacts, test/review/notary logs, diagnostics, visual fixture, and verified signed prior Build15 daemon/Build17 app rollback copies. MANIFEST.sha256 covers file contents; recursive_manifest.py additionally covers directory/symlink/mode metadata. Hash receipts are outside the frozen directory to avoid self-reference.

Start by checking all manifest entries and artifact-receipt.json. Prepare the coordinator-owned canary using the exact daemon hash and prior rollback identity. Do not reinstall Build21, deploy Build22's daemon, silently merge app UI changes, or reuse this candidate's acceptance label without a successful runtime gate.

Undo for local source: this is an isolated branch; no installed state needs rollback. Preserve the packet and return the worktree to the owner before any source reversal. Root PROJECTS.md changes affect only the Tyrell row, with separate full-file backups and single-row receipts; restore just that row if needed after checking intervening changes. Notes and archive records document the source and root-index changes. No credentials are included.

Final producer receipts

Frozen manifest file SHA256: 64885d1fcb969911b7fe4f58f9ade039e91036d88c11d1619806f37d4b65fb5a. Recursive summary: 96325d8939f9f62b59d2f999522caec69faf8c01d4819780d59a445e59c30766;92 files,472843528 bytes. Every file verified. Strict codesign checks also pass on the frozen candidate and rollback copies.

Documentation commit9bef4bb8655554193fe5c15568d4f27353e14ed6 is verified on backup/fleet; source093d653 remains the exact artifact source. Worktree clean; canonical main75e8ab6 remains clean and unchanged.

Root-index candidate milestone changed only the Tyrell row. Before SHA256 bff493174abf3e737949ab3306d702e6471a815ac543c0b8ef03da4661b153bd, after df8865e6689bc67f2543654de45dfa37768de483ff65dde33bf2f4039232fc88; backup /Users/richh/dev/_handoff/tyrell-build23-memory-20260914/PROJECTS.md.before-build23-candidate. Initial rejection/dispatch backup and receipt remain adjacent. Restore only the prior row, preserving later unrelated changes.

Two sequential Terra/high review jobs were used; budget advice was proceed before each. Exact spend was not measured. No user credential action is required. Coordinator owns protected runtime verification; no candidate is installed by this producer.

User-requested relay: full handoff delivered to claude@rdmsm4x mailbox as20260914-165126-E7395726; persisted body verified. Read acknowledgment not yet observed. Coordinator ownership remains unchanged.