rdmsm4x-changelog-20260902-1406-tyrell-next-build-ios-cloudkit-integration

Prepared an isolated, source-only next-build candidate that integrates Tyrell's sanitized iOS CloudKit snapshot reader without changing Build 8, devices, daemons, signing, or CloudKit data.

Scope

• Host: rdmsm4x.
• Project mode: Tyrell Production.
• Worktree: /Users/richh/dev/_worktrees/tyrell-build-next-ios-cloudkit-20260902.
• Branch: codex/tyrell-build-next-ios-cloudkit-20260902.
• Base: 609ef4e391d24f180b74ca105b4ae5b78fd39c01.
• Candidate commits: f597d31b6cf6112da2d8e95cd106bc9c4014ae2a and ca3048cf11cf9fd48cdc0b1c9810da7a4c029055.

Changes

• Cherry-picked the resolved, isolated iOS CloudKit reader delivery into the new linked worktree with no conflicts.
• Added docs/architecture/2026-09-02-ios-cloudkit-next-build-gates.md, which is the integration handoff and records device readiness, the master-side sanitized publisher boundary, and the historic-chat future decision checklist.
• Added a resumable top checkpoint to SESSION-STATE.md.
• Registered and claimed TASK-20260902-06 for the bounded integration lane.
• Published a pointer-only fleet coordination check-in.

Verification

• swift test passed with exit 0. Its runners reported zero failures across the observed XCTest and Swift Testing runs.
• cd ios && xcodegen generate --spec project.yml passed; the generated Xcode project is ignored.
• xcodebuild -project ios/TyrellMobile.xcodeproj -scheme TyrellMobile -configuration Debug -destination 'platform=iOS Simulator,id=9A616E58-92CC-4635-AFA3-66D23CB454C8' test passed with 22 XCTest cases and 0 failures, including 5 CloudKit snapshot cases.
• The test simulator was shut down after completion.
• git diff --check 609ef4e391d24f180b74ca105b4ae5b78fd39c01 HEAD passed.
• The active Build 8 worktree still reports the unchanged expected commit 609ef4e391d24f180b74ca105b4ae5b78fd39c01 and a clean status.
• Read-only device discovery found rdip17air connected and rdip17p unavailable; neither was signed, installed, launched, or otherwise changed.

Rollback and outstanding owner actions

• Before source acceptance, abandon only this isolated linked worktree and branch after retaining the handoff. After a later merge, revert f597d31b6cf6112da2d8e95cd106bc9c4014ae2a if source rollback is needed.
• No CloudKit record, zone, schema, account, or production data was created or changed, so no remote-data rollback is required.
• The release owner must separately authorize and verify the master publisher, Apple provisioning, first rdip17p canary, then the independent rdip17air repeat. Historic chat remains a separate privacy/security/product phase.