rdmsm4x-changelog-20260902-1434-tyrell-build9-source-integration
Tyrell Build 9 source integration checkpoint
Integrated the tested private iOS CloudKit snapshot reader and the first behavior-proven ecs0lib persistence migration into one clean Build 9 branch, so the next iOS and shared-runtime slices have a stable source base without changing the accepted Build 8 fleet runtime.
Scope
- Host:
rdmsm4x - Source-only; no app or daemon install, signing, CloudKit write, device deployment, or fleet runtime mutation.
- Canonical dirty checkout was not edited.
- Integration worktree:
/Users/richh/dev/_worktrees/tyrell-build9-integrated-20260902 - Branch:
codex/tyrell-build9-integrated-20260902 - Checkpoint commit:
c563cbba6c73058cd2b17346a918cb39736452e8
Files and source changes
- Integrated iOS snapshot client and architecture gate documentation from the isolated iOS lane.
- Integrated production SQLite binding and row handling through
ECS0Persistence.DatabaseValueandECS0Persistence.DatabaseRowfrom the isolated shared-runtime lane. - Updated
/Users/richh/dev/_worktrees/tyrell-build9-integrated-20260902/SESSION-STATE.mdwith the integrated source identity, validation, rollback boundary, and active Build 9 ticket. - Opened and claimed
FEAT-20260902-03as the Build 9 integration umbrella.
Verification
- Focused shared-persistence tests: 2 of 2 passed against real SQLite.
- Complete Swift package suite after both integrations: exit 0, zero failures.
- iPhone 17 Pro simulator suite: 22 of 22 passed, including five CloudKit snapshot tests.
git diff --check: passed.- Final integration worktree: clean at the checkpoint commit above.
Safety boundary
- CloudKit remains a private remote projection; the Tyrell master remains authoritative.
- No production CloudKit record, zone, schema, account, entitlement, or data was modified.
- No physical-device signing, installation, launch, or notification acceptance is claimed.
- Production Build 8 remains installed and running across the fleet.
Rollback
- Source rollback: move the Build 9 integration branch back to parent
701788f2d368cba49224c70735f0d67f2d3c3293, or omit commits5d003f0,18b1cb2, and701788fwhen forming a successor branch. - Runtime rollback is not required because this checkpoint made no runtime or deployment change.
Outstanding work
- Accept a sanitized master publisher only after fake-transport, allowlist, provenance, and fail-closed tests pass; a real private-zone write is a separate owner-approved gate.
- Accept the iOS readiness UI and shared logging migration only after their isolated full gates pass.
- Networking migration remains deferred until transport, concurrency, cancellation, and privacy equivalence are proven.