ecs0lib portfolio monitor: Build 8 accepted; Build 9 privacy and count defects routed

Recorded independent six-host acceptance of Tyrell Build 8, tracked active Build 9 integration, and routed two source-confirmed reusable defects without taking application or library source ownership.

Scope and authority

• Execution host: rdmsm4x.
• Fleet scope observed read-only: rdmsm4x, rdmbair13m5, rdmbair15m5, rdmpw3265m, rdmpw3275m, and jdmbair13m5.
• Work ticket: TASK-20260830-02, held only as the metadata-only codex@rdmsm4x/ecs0lib-monitor lease.
• Mutable scope used: this monitor check-in, its own ticket heartbeat/comment, immutable fleet-bus messages, this changelog, and its Apple Notes copy.
• No Tyrell, ecs0lib, ECSCloudKit, agentkit, or other application/library source was edited, staged, built in place, signed, installed, deployed, published, deleted, or transferred by this monitor.

Local state changed

• Updated /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-ecs0lib-portfolio-monitor-20260901.json with the 14:54 EDT evidence snapshot; JSON validation passed.
• Extended only TASK-20260830-02 as codex@rdmsm4x/ecs0lib-monitor through 2026-09-02T16:55:03-04:00 and appended four evidence comments through /Users/richh/dev/issues/bin/ticket; the later comments record the cleared conflict, corrected child-suite counts, immutable timestamp correction, the subsequently lapsed Build 9 root claim, and active writes after that lapse.
• Sent nine immutable coordination messages:
  • 20260902-144846-37915562: ecs0lib logging privacy blocker and bounded upstream-transfer offer.
  • 20260902-145330-1F477D83: agentkit multi-XCTest-bundle undercount reproduction and bounded repair offer.
  • 20260902-145330-77734695: Build 9 root-lease renew-or-release warning.
  • 20260902-145827-5AC3BA89: live Build 9 publisher cherry-pick conflict plus near-expiry lease warning.
  • 20260902-145943-1B5F5146: exact corrected counts for the two resolved Build 9 child receipts.
  • 20260902-150047-8D86F5B8: conflict-cleared follow-up; its observation time was mistyped as 14:00 instead of 15:00 EDT.
  • 20260902-150054-4E18AB9C: immediate immutable correction of that timestamp typo; the technical content was unchanged.
  • 20260902-150335-DA379E72: confirmed the Build 9 root claim had lapsed and requested same-owner reclaim or explicit evidence-backed closure before further work.
  • 20260902-150510-E1DBB2DF: reported two Build 9 documentation/state writes after the lease lapse and requested that further writes stop until same-owner reclaim or closure.
• Added this file at /Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260902-1455-ecs0lib-monitor-build8-build9-blockers.md.

Shared-library and portfolio truth

• ecs0lib remains at 90c3c6ddd6377be6012617d1934a5fbce5c028aa.
• The same 14 ownerless untracked Hardware/Provenance/test Swift files remain present, total 152835 bytes; every SHA-256 still matches the preserved manifest in the monitor check-in. They were not staged, built, adopted, or altered.
• ECSCloudKit remains clean at 93b9f700e7b73c02881b0a00007cb6f813720a43.
• Fresh canonical 52-root adoption remains:
  • ecs0lib: 26 package declarations / 22 production-source importers.
  • ECSCloudKit: 15 declarations / 1 production-source importer.
  • ProcessRunner: two archived superseded copies / zero active declarations.
• ISSUE-20260902-06, the ECS0HTTPServer failed-bind/same-instance-retry defect, remains open and unclaimed. The earlier exact two-path upstream offer remains owner-gated.

Tyrell Build 8 independent acceptance

• REV-20260902-01 resolved at 14:19 EDT for source commit 609ef4e391d24f180b74ca105b4ae5b78fd39c01; lifecycle/docs checkpoint 835345e850c909583283e21c39d1494e067668d0 is clean.
• Direct local and SSH inspection of /Applications/Tyrell.app on all six hosts reproduced:
  • version 0.2.0, build 8, display name Tyrell;
  • executable SHA-256 9f50f9fb5ff5eae7a96623b19002d04b64e9b1138e7205c534b2bb80bf091bca on every host;
  • x86_64 arm64 architecture;
  • identifier com.eastcoastscience.Tyrell, TeamIdentifier ZU2882L4HT, and strict deep code-signature verification exit 0;
  • exactly one app process per host;
  • HTTP 200 from both local status endpoints, ports 43118 and 43117;
  • a retained Build 7 rollback app on each host.
• Direct canary receipt readback on rdmbair15m5 reproduced mode 600, schema 3, accepted status, nonce b8-20260902-1405-609ef4e, exact host/bundle/team/candidate fields, passed app-probe contract, and SHA-256 5ea5aba675a3f5c7de2b3502abb2326fc3c11b5ce71ddf068eee308d26459495.
• Unauthenticated activity access returned HTTP 401.
• spctl --assess still rejects with exit 3 on all six hosts. This accepts the private Apple-Development fleet artifact/runtime/rollback slice; it does not claim notarized or public Gatekeeper distribution.

Tyrell Build 9 current state

• Root integration ticket FEAT-20260902-03 remains in progress. Its worktree /Users/richh/dev/_worktrees/tyrell-build9-integrated-20260902 was clean at ee285ad and includes:
  • the private read-only iOS CloudKit reader;
  • production ECS0Persistence DatabaseValue/DatabaseRow use;
  • the source-confirmed shared logging/networking gate;
  • iOS CloudKit readiness/offline evidence.
• Retained Swift log /Users/richh/dev/_handoff/tyrell-build9-integrated-swift-test-20260902-1438.log has SHA-256 59303dc3898ae82378d0aca5d2b9e590cbd6d55032f4dac82741519fa0ffa7bd, exit 0, and zero failures.
• Retained simulator log /Users/richh/dev/_handoff/tyrell-build9-integrated-ios-test-20260902-1445.log has SHA-256 0f9e6ac3b6b77d52d40bc82fb1465a30e7c703056ffb781b77c38541b5710226, reports 22 tests / 0 failures, and contains TEST SUCCEEDED.
• UI-20260902-02 resolved at clean commit 8989b7f and was integrated as ee285ad.
• FEAT-20260902-04 resolved at clean source-only commit 6d394b4. At 14:58 EDT the root worktree was actively cherry-picking that commit: seven publisher paths were staged and SESSION-STATE.md was the sole unmerged path. The owner resolved it additively; by 15:00 the integration worktree was clean at 317dfe2. After the root claim lapsed, SESSION-STATE.md and docs/architecture/2026-09-02-build9-acceptance.md were modified at 15:03-15:04 and remained dirty at 15:05. The monitor did not inspect their content, add, abort, resolve, test, commit, or otherwise touch the source lane. Integrated post-cherry-pick gates remain pending evidence.
• REV-20260902-02 is blocked and released with clean docs commit ab563ddd8e7bb818ccd8e9fbe86223a691b6e2ce; no logging runtime migration was accepted.
• The root Build 9 lease did not heartbeat after its 14:33 claim and became stale at 15:03 while the ticket remained in progress and integrated post-publisher gates were not recorded. The holder received exact renew-or-release/preservation warnings, a conflict-cleared follow-up, a confirmed-lapse notice, and a specific ownership-conflict notice after two files changed post-lapse. This monitor will preserve those files and will not steal or reclaim the source lane.

Reusable defect 1: ecs0lib logging privacy and severity

Source inspection at ecs0lib 90c3c6d confirmed:

• ECSUnifiedLogging retains complete message strings in its ring buffer and emits them with public privacy.
• ECS0ActivityLogger retains complete free-form messages and publicly emits subsystem/message fields.
• ECSSyslog publicly emits the complete message.
• ECSUnifiedLogging has explicit debug/error/fault branches, while warning and notice fall through to info.
• queryLogs(minLevel:) performs equality-like filtering rather than minimum-severity filtering.

Tyrell correctly rejected a runtime migration that would weaken its current privacy/severity behavior. Message 20260902-144846-37915562 offers an upstream repair only after an explicit ticket and path transfer for Sources/ECS0System/ECSUnifiedLogging.swift, Sources/ECS0System/ECS0System.swift, Sources/ECS0System/ECSSyslog.swift, and focused tests. The offer requires typed levels/categories, public literals plus explicitly labelled private fields, proof that a raw private value is absent from retained/Codable/sink surfaces, and severity/filter/concurrency/eviction coverage.

Reusable defect 2: agentkit test-count undercount

• Existing FEAT-20260901-25 says agentkit_swift_test_count correctly counts XCTest and Swift Testing.
• At agentkit commit a3355439eebf24da8c788aea61d10f6aa914593b, /Users/richh/dev/lib/agentkit/lib/verify.zsh selects only the maximum XCTest aggregate using sort -rn | head -1.
• On the retained Build 9 Swift log it reports 184 386 570.
• Raw top-level XCTest-bundle summaries are:
  • TyrellCoreTests.xctest: 30.
  • TyrellAppSupportTests.xctest: 11.
  • E2ETests.xctest: 184.
  • XCTest total: 225.
• Raw Swift Testing runs are 258, 71, 57, and 0, totaling 386.
• The complete count is therefore 611, not 570. Every run passed; the defect affects count/no-drop evidence, not the PASS result.
• The same defect propagated into the two child closeouts:
  • /tmp/tyrell-build9-ios-observability-swift-test.log, SHA-256 c42148ed8527102d420b4b2d2523342dd185bd0bc357b6808c8f8d99c5b1e5c2, contains 225 XCTest plus 386 Swift Testing = 611 complete passing tests, not the recorded 570.
  • /tmp/tyrell-build9-cloud-publisher-full.log, SHA-256 b2ba123a6fe979f5f2c2325a4fa3b4aad1b972ffe64fa303a6382b093dd139a3, contains 235 XCTest plus 386 Swift Testing = 621 complete passing tests, not an unqualified 235.
• Both /tmp logs are ephemeral. Their owners were asked to retain them and append corrective lifecycle evidence before relying on the counts.
• Existing self-tests cover one XCTest aggregate and do not reproduce multiple .xctest bundles among nested suite and duplicate All tests rollups.
• The agentkit tree contains an unrelated dirty lib/integrity.zsh; the monitor preserved it and made no edit.
• Message 20260902-145330-1F477D83 routes the exact evidence and offers an isolated two-path repair (lib/verify.zsh, tests/test_agentkit.zsh) only after transfer.

Fleet services

• The 14:46 independent fleet audit found all six hosts reachable, all launchd jobs healthy, and all claimed agent counts equal to external process measurements; no healing action was needed.
• publish_site.zsh PID 16936 remains sleeping after roughly 54 minutes. /Users/richh/dev/data/publish.log has not advanced since 14:01 and /private/tmp/devsite.out plus /private/tmp/devsite.err remain empty. The previously routed cadence/delivery defect is still active; the monitor did not signal or restart the process.

Commands and evidence instruments

• Fleet coordination: agent_msg.zsh sync, inbox --unread, send, and immutable mail-file inspection.
• Tickets: ticket search, ticket show, ticket claims --all, ticket heartbeat, and ticket comment, always with explicit Codex identity for the monitor lease.
• Repositories and artifacts: git status --short --branch, git log, git rev-parse, shasum -a 256, lipo -archs, codesign -dv, codesign --verify --deep --strict, spctl --assess, pgrep, and direct local/SSH HTTP probes.
• Logs/source: rg against exact XCTest/Swift Testing rollups and the three ecs0lib logger implementations; stat, ps, and lsof for the publisher.
• Check-in validation: python3 -m json.tool /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-ecs0lib-portfolio-monitor-20260901.json returned exit 0.

Backup, rollback, and undo

• No product source was changed, so no product-source backup was created or required by this monitor.
• Build 8 rollback apps remain present on all six hosts and identify as Build 7; deployment rollback is owned by the release lane, not this monitor.
• The 14 ownerless ecs0lib files are preserved in place and their exact hashes remain recorded in the monitor check-in.
• Fleet-bus messages are immutable. Correct them only with a follow-up message; do not rewrite the originals.
• Ticket evidence is additive. Correct it with a later comment. If recurring monitoring stops, release only TASK-20260830-02 with --as codex@rdmsm4x/ecs0lib-monitor.
• Supersede the check-in with fresher observed evidence rather than deleting product or owner-held state.

Outstanding owner actions

• Claude Build 9 root owner: heartbeat, deliberately resolve, or release FEAT-20260902-03 before its active lease lapses.
• Build 9 child owners: finish and hand off FEAT-20260902-04 and reconcile the already integrated UI-20260902-02 ticket lifecycle.
• ecs0lib owner: create/assign an upstream logging-privacy ticket and exact path lease if the offered repair is wanted; separately decide ownership of the 14 untracked Hardware/Provenance/test files and ISSUE-20260902-06.
• agentkit owner: accept FEAT-20260901-25 refinement or provide a separate exact ticket/path transfer for the multi-bundle counter repair.
• Devsite owner: diagnose the still-sleeping publisher and restore time-bounded completion evidence without killing unknown-owner work.
• Tyrell lead: reconcile completed iOS work with the still-live TASK-20260902-06 claimant rather than treating a commit as lifecycle acceptance.