ecs0lib canonical integration coordination

Coordinated a one-writer canonical-host ecs0lib integration, verified the result, staged the collision-aware app adoption queue, and released the writer claim for owner review.

Scope

• Coordination host: rdmbair15m5.
• Changed local files: the integration check-in, canonical integration receipt, and this changelog.
• Changed remote state: a dedicated branch/worktree and handoff directory on rdmsm4x; three additive ticket comments.
• No provider state, secret, app checkout, installed app, release, publication, signing, or deployment changed.

Verification

• Patch hashes and tree identities matched.
• Canonical-host ThreadSanitizer suite: 123 tests, zero failures, no reported race.
• Canonical-host release build, JSON parsing, package description, diff check, and clean-worktree check passed.
• The dirty canonical main checkout retained its original six modified documentation/web files.
• Live read-only app collision inventory recorded clean candidates and hold lanes before any retrofit.

Files and messages

• /Users/richh/Documents/Codex/2026-08-30/all-apps-going-forward-should-have/outputs/CANONICAL-INTEGRATION-RECEIPT-2026-08-30.md
• /Users/richh/.agent-coordination/checkins/codex-rdmbair15m5-ecs0lib-canonical-integration-20260830.json
• Claim message 20260830-165130-DFE81597.
• Adoption message 20260830-165556-03293706.

Backup and undo

• Local artifacts are additive. The remote integration is isolated to branch codex/global-app-capabilities-v1.1-20260830 and worktree /Users/richh/dev/_worktrees/ecs0lib-codex-global-app-v1.1.
• Do not remove that branch or worktree until the canonical owner records acceptance, rejection, or supersession.

Outstanding owner actions

• Canonical owner reviews the branch and release metadata.
• App owners claim one retrofit lane at a time.
• Signing, deployment, publication, and fleet verification remain explicitly pending.