rdmpw3275m-changelog-20260911-2032-tyrell-build19-pass3-memory-transient

Tyrell Build 19 remained healthy through unchanged inventory pass 3, but the pass produced a reproducible six-to-seven-minute charged-memory plateau near 801 MiB before reclaiming to 107.5 MiB; this materially extends the existing inventory and memory-gate issues without yet constituting a gate failure.

Scope and state

• Coordinator host: rdmpw3275m; canary host: rdmbair15m5 only.
• Canary stage: /Users/richh/.tyrell/build19-canary-20260911-ec03697.
• Guard PID 69716; daemon PID 69804; daemon process start Fri Sep 11 18:18:18 2026.
• Exact Build 19 daemon SHA-256 remained 03e365cec1b8219b3d4cc12384b42313936b850748a97727366e6595f4ee390b.
• Guard state remained soaking. No process restart, rollback, artifact replacement, or fleet expansion occurred.

Pass 3 evidence

• Pass 3 completed at 2026-09-11 20:23:20 EDT, again reporting 38 roots across 29 bundle plans.
• Guard evidence remained completed_passes=[1,2,3] and unchanged_repeat=true.
• Charged physical footprint was 127,387,208 bytes immediately before the pass, then 768,280,448 bytes at completion.
• It reached an observed maximum of 840,075,280 bytes (801.158 MiB) and remained near 840 MiB through seven consecutive one-minute samples.
• At 20:30:21 EDT, it reclaimed to 112,723,576 bytes (107.502 MiB).
• Diagnostic RSS moved from 554,352 KiB to 1,380,800 KiB, then down to 878,032 KiB.
• The daemon retained the same PID, process-start identity, executable path, 41–42 descriptors, and 2 TCP descriptors. Both status planes and all 16 permission probes remained HTTP 200.
• A direct footprint/vmmap control during the plateau reproduced 839,944,208 charged bytes. The largest allocator categories were Malloc Large (empty) at approximately 500.2 MiB dirty and Malloc Small (empty) at approximately 259.5 MiB dirty; SQLite Page Cache had only about 9.1 MiB resident.

Interpretation and gate risk

• This is a real periodic charged allocator plateau after an unchanged hourly inventory, not merely RSS inflation. It also fully reclaimed without intervention, so it is not yet evidence of a permanent leak or a failed acceptance gate.
• The physical-footprint-v2 policy intentionally treats peak as diagnostic and evaluates endpoint charged footprint plus growth at the six-hour and 24-hour checkpoints.
• The measured inventory interval is approximately 3,632.6 seconds because the next one-hour timer starts after each pass completes. Extrapolating that observed cadence places pass 7 approximately three minutes before the fixed 00:28:19 EDT six-hour endpoint.
• If a similar plateau repeats, the fixed endpoint may land inside active inventory work. This is a phase-alignment risk, not a predicted result presented as fact; the actual six-hour receipt remains authoritative.
• The canary guard was deliberately left unchanged mid-run so the evidence remains comparable and auditable.

Commands and state changes

• Resolved rdmpw3275m, ran the mandatory agent preflight with exit 0, synchronized the fleet mailbox, and found no new Tyrell or local-agy receipt.
• Read and monitored state.json, latest.json, samples.jsonl, inventory.log, process identity, artifact hash, endpoints, descriptors, footprint, and vmmap over authenticated fleet SSH.
• Waited for pass 3 and subsequent one-minute samples until the plateau independently demonstrated reclamation.
• Refreshed only the five tickets held by this monitoring task.
• Added re-runnable command text, raw observations, and interpretation to canonical TASK-20260911-01, ISSUE-20260911-01, and ISSUE-20260911-15.
• No duplicate issue was opened because the finding directly extends the existing inventory and memory-gate tickets.
• Added this changelog file: /Users/richh/dev/LLM/Claude/changelogs/rdmpw3275m-changelog-20260911-2032-tyrell-build19-pass3-memory-transient.md.

Rollback and outstanding work

• Exact signed universal Build 15 rollback daemon SHA-256 dbc440bd54b85a54dd6c4150b23b3e508bff7d8d8080687d81b9ba7ac2cbbcf0 and the retained Build 17 app remain the fail-closed targets.
• The six-hour endpoint at approximately 2026-09-12 00:28:19 EDT must be observed and independently reproduced; it must not be inferred from this transient.
• The 24-hour memory gate, CPU review, fresh app functional canary, reboot stable-path proof, controller installation, and any staged broader rollout remain outstanding.
• Local agy process count remained zero with unchanged manifest and status hashes; no parent or provider-reset condition justified a resume.
• Undo is unnecessary for monitoring reads. Ticket lease heartbeats expire naturally, and comments are additive evidence. No canary runtime state was mutated.