rdmpw3275m-changelog-20260911-1925-tyrell-build19-repeated-inventory

Tyrell Build 19 completed its first required unchanged repeated repository inventory on the protected rdmbair15m5 canary; the same-process canary remains healthy and continues toward the six-hour and 24-hour gates.

Scope and state

• Coordinator host: rdmpw3275m; monitoring ticket holder: codex@rdmpw3275m/01a078a7.
• Canary host: rdmbair15m5 only.
• Stage: /Users/richh/.tyrell/build19-canary-20260911-ec03697.
• Guard PID 69716; daemon PID 69804; daemon process start Fri Sep 11 18:18:18 2026.
• Guard state remained soaking; no restart, rollback, app replacement, or fleet expansion occurred.
• Exact signed Build 19 daemon SHA-256 remained 03e365cec1b8219b3d4cc12384b42313936b850748a97727366e6595f4ee390b.
• Exact Build 19 app executable SHA-256 remained cfb51c67602f9cf6047e4b6bf609ee1a5e24fe99d907269fcf0548d7c5c2c072; installed CFBundleVersion remained 19.

Repeated-inventory evidence

• Inventory pass 1 completed at 2026-09-11 18:22:15 EDT: 38 roots across 29 bundle plans.
• Inventory pass 2 completed at 2026-09-11 19:22:48 EDT: the same 38 roots across the same 29 bundle plans.
• The reviewed guard compared exact sorted (name, size, mtime_ns) bundle manifests at the two pass boundaries and set completed_passes=[1,2] and unchanged_repeat=true.
• Independent current manifest control found 66 *.bundle entries with stat-manifest SHA-256 8c723b9164ebcb1fdebee84abaf90603ee7d9853f05d64a5c03798b4ba29ba84.
• The newest current bundle mtime was 2026-09-11 17:02:39 EDT, predating both canary inventory passes.
• After pass 2, the guard still reported the original PID, process-start identity, executable path, two live TCP descriptors, and bounded descriptor count.
• Both /api/status planes returned HTTP 200; all 16 concurrent permission probes returned valid HTTP 200 responses.

Inventory-workload memory evidence

• Three consecutive samples across the second inventory pass recorded physical footprint 468,961,032 -> 297,862,920 -> 113,804,920 bytes.
• Corresponding diagnostic RSS was 956,736 -> 1,058,192 -> 896,112 KiB.
• Corresponding CPU was 32.2% -> 2.7% -> 0.1%.
• This demonstrates a temporary full-inventory workload peak followed by prompt reclamation. The accepted policy explicitly retains transient peak as diagnostic and evaluates endpoint charged footprint plus growth at the six-hour and 24-hour boundaries.
• The already-passed 40-minute receipt remains SHA-256 be6a08b44cfece5dd6c0797946663b0a84186c7d79f49d5e2679ea8282f22a71; this milestone does not replace the later gates.

Commands and files changed

• Resolved the local host and verified Aqua ownership; ran the mandatory agent preflight with exit 0.
• Synchronized the fleet mailbox and read the exact Build 19 handoff receipt 20260911-184023-BF7D71FE.
• Cryptographically distinguished local SSH host key KT0oBLND... from canonical rdmsm4x host key 3D5x0tqX... before canonical ticket and check-in writes.
• Read the live canary state.json, latest.json, samples.jsonl, inventory.log, short-gate.json, process table, executable paths, signatures, hashes, endpoints, and descriptor/socket counts over SSH.
• Updated canonical ticket comments for TASK-20260911-01 and ISSUE-20260911-01 with re-runnable command text, raw observed values, and exit status.
• Refreshed only held leases for ISSUE-20260905-23, ISSUE-20260909-12, ISSUE-20260911-01, TASK-20260911-01, and TASK-20260906-01.
• Updated /Users/richh/.agent-coordination/checkins/codex-rdmpw3275m-tyrelld-build18-recovery-20260910.json from obsolete source-review state to Build 19 canary-monitoring state; JSON validation passed and local/canonical SHA-256 matched 4c07917a44b58f55a839148e5818a29c9cfd556fbeea65957f5a933f0352aeae after check-in sync.
• Added this file: /Users/richh/dev/LLM/Claude/changelogs/rdmpw3275m-changelog-20260911-1925-tyrell-build19-repeated-inventory.md.

Rollback, undo, and remaining work

• Exact signed universal Build 15 rollback daemon SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0 and the prior Build 17 app remain retained by the canary stage.
• Any later identity, health, sample-gap, permission, descriptor, memory, or dependency-integrity failure must continue to fail closed and restore the retained artifacts.
• Ticket lease heartbeats expire naturally and need no destructive undo. The check-in is an append/supersession control record and can be superseded by the next truthful status.
• Earliest six-hour-after-warm-up gate remains 2026-09-12 00:28:19 EDT.
• Required 24-hour boundary remains 2026-09-12 18:18:19 EDT.
• CPU review, fresh app functional proof, reboot stable-path proof, controller installation, and any deliberately staged broader rollout remain outstanding.
• The local agy lane remains non-resumable while every parent is complete or handoff-pending and there is no provider quota-reset event; canonical acceptance receipts remain outstanding.