ecs0lib monitor: Build 8 candidate and devsite delivery evidence

Re-established the canonical shared-library and app-portfolio monitor, preserved every active owner boundary, independently reproduced the new Tyrell Build 8 artifact identity and its remaining Gatekeeper hold, recorded the separately owned iOS integration, and verified a real devsite publication-delivery gap.

Scope

• Execution host: rdmsm4x
• Read-only evidence scope: canonical ecs0lib, ECSCloudKit, 52 filtered app roots, Tyrell Build 8 and next-build iOS worktrees, fleet audit/health/stability reports, and com.eastcoastscience.devsite
• Metadata-only write scope: this monitor's check-in, TASK-20260830-02 heartbeat/comment, two immutable fleet-bus messages, this changelog, and the matching Apple Notes entry
• No app or library source, other ticket lifecycle, running process, Homebrew state, signature, deployment, publication, credential, or deletion state was changed

Files changed

• /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-ecs0lib-portfolio-monitor-20260901.json
• /Users/richh/dev/issues/open/TASK-20260830-02-monitor-shared-libraries-and-repair-reus.md through the ticket CLI's authorized heartbeat/comment operations
• /Users/richh/.agent-coordination/mail/20260902-140655-887BF5D9__from-codex-rdmsm4x__to-codex-rdmsm4x-claude-rdmsm4x__tyrell-build8-candidate-and-ios-integration-monitor.md
• /Users/richh/.agent-coordination/mail/20260902-140746-38C0D88F__from-codex-rdmsm4x__to-claude-rdmsm4x__devsite-delivery-gap-independent-reproduction.md
• /Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260902-1410-ecs0lib-monitor-build8-and-devsite.md

Shared-library and portfolio evidence

• ecs0lib remains at 90c3c6ddd6377be6012617d1934a5fbce5c028aa with the same 14 ownerless untracked Hardware, Provenance, and test files. Their aggregate size remains 152,835 bytes and every SHA-256 matches the preserved manifest.
• ECSCloudKit remains clean at 93b9f700e7b73c02881b0a00007cb6f813720a43.
• A fresh scan of 52 immediate canonical app roots returned 26 ecs0lib declarations and 22 production-source importers; ECSCloudKit remains 15 declarations and one importer. Two superseded ProcessRunner copies remain archived and no active declaration exists.
• ISSUE-20260902-06 remains open and unclaimed; the previously offered exact two-path upstream HTTP-server repair remains owner-gated.

Tyrell evidence and ownership

• REV-20260902-01 remains owned by codex@rdmsm4x/01a04277-a949-77f1-8f07-57ff6a8ff90f. Its isolated worktree is now clean at 609ef4e391d24f180b74ca105b4ae5b78fd39c01; canonical Tyrell remains at 25405a7a5b93c262dbdafdb7da84c9868382e652 with unrelated dirty documentation and icon paths.
• Read-only candidate checks reproduced bundle com.eastcoastscience.Tyrell, version 0.2.0 (8), executable SHA-256 9f50f9fb5ff5eae7a96623b19002d04b64e9b1138e7205c534b2bb80bf091bca, arm64 full CodeDirectory SHA-256 8f4dcff092840b870e01f90df1692e24c1d09c2c8485d913e2fc1472b167110d, x86_64 arm64, TeamIdentifier ZU2882L4HT, strict signature success, and headless Tyrell 0.2.0 (8).
• spctl --assess --type execute independently returned rejected with exit 3. The designated canary and fleet remain on Build 7, so there is no Build 8 canary or fleet acceptance.
• TASK-20260902-06 is separately claimed by claude@rdmsm4x/pid39057. Its isolated next-build worktree is clean at f597d317b0d2462e9169b9bc040508d5e33c7714, which is Build 8 plus the source-only iOS reader cherry-pick. The prior source/mock/simulator-only acceptance boundary remains; no production CloudKit, signing, device, or deployment acceptance was added.

Fleet delivery evidence

• The 14:01 independent fleet audit found all six hosts reachable, launchd jobs healthy, and every self-reported agent count equal to the external measurement; the earlier 13:46 count discrepancy cleared without healing.
• com.eastcoastscience.devsite shows a real 12-hour-20-minute completion gap in publish.log, from 2026-09-02 01:40:55 EDT to 14:01:21 EDT. Launchd reports a 1,800-second interval, 37 runs, current state running, and last exit 0. The 14:01 generator phase succeeded while downstream build_site.py remained active beyond six minutes. This was reported as a delivery/cadence defect, not as a dead process, and no process was signalled.
• The health job's eight loose-versus-packed Git-ref alerts remain a known false positive: each packed ref is an ancestor of its forward-moving loose ref. The repair evidence was already routed to the fleet lead.

Commands and tools used

• Fleet bus sync, unread-message inspection, immutable send
• git rev-parse, git status, git log, git diff --name-status, git diff --check, and git worktree list
• Filtered find/rg portfolio scan and SHA-256 comparison against the monitor manifest
• Ticket show, claims, heartbeat, and comment with explicit Codex identity
• Read-only PlistBuddy, shasum, codesign, lipo, application --version, and spctl checks
• Read-only launchctl print, ps, pgrep, stat, and log inspection for the site publisher

Verification

• Monitor check-in parses successfully with jq after the update.
• Shared-library commit, dirty-path, file-count, byte-count, and hash evidence match the prior accepted baseline.
• Build 8 artifact identity matches the current release audit, while the independently reproduced spctl rejection preserves the release hold.
• The monitor lease now expires at 2026-09-02T16:08:20-0400.

Undo and outstanding owner actions

• Coordination messages are immutable and should not be deleted. If a factual correction is required, append a corrective reply.
• Ticket heartbeat/comment and the check-in are an append-only evidence record; do not rewrite lifecycle history. A correction should be a new comment/check-in delta.
• The Tyrell release owner must decide the intended Gatekeeper/distribution boundary, produce a fresh nonce-bound canary receipt, and supply an exact final test-log handoff before independent release acceptance.
• The iOS integrator owns the exact isolated ios/**, architecture documentation, and SESSION-STATE.md paths under TASK-20260902-06 until release.
• The fleet lead owns diagnosis or repair of the devsite delivery gap. This monitor offered bounded read-only timing verification after the current run exits.