Resolve the named removal of this lane’s unsupported 2 MiB total-retention test, keeping the protected test unchanged. The valid 87 MiB restart reproducer fails 3/3 on the requested baseline; no implementation fix or completed readiness gate exists. Corrected findings, XML and a reviewable removal patch are on remote branches.
RE-VERIFY: This is a write-time snapshot. Recheck the draft PR, feature branch, evidence branch, pending test-removal approval and XML before resuming.
Bound tracker restart and single-record update memory while keeping the protected test unchanged. The valid public owner-budget reproducer is committed and fails reliably; the implementation is not fixed. One additional test introduced by this lane has an unsupported total-state allowance and needs to be retired with approval under the lane's no-test-removal rule.
Correction: the earlier claim that the protected snapshot test necessarily conflicts with bounded memory was wrong. Its2MiB allowance is above the file snapshots, not a2MiB total-state budget. A fixed-cap byte cache can accommodate its12,599,608-byte per-owner fixture while streaming larger files. A bounded decoded-record cache or record store is also needed. This is a design direction, not a verified implementation. Do not require changing the protected test based on the earlier claim.
The valid testTrackerRestartBytesStayWithinProductionBudget uses768 synthetic small records with131,072 ignored bytes each, one independent tracker owner and the unchanged87MiB child budget. File bytes100,797,589 exceed all available child bytes91,226,112 by9,571,477. Three first attempts on f3ffccd8 fail by child-completion assertion in complete-file snapshot reading, times4,677/6,087/4,218ms. The same product tree after rebase fails once (5,346ms). No provider, result transport or journal exists in this scenario.
The protected testTrackerRetainsOneByteSnapshotAndImmutableRecords is byte-for-byte unchanged and passes3/3 on the rebased branch, times7,952/5,565/6,330ms. The unsupported added testTrackerRestartRetainedStateHasFixedBudget measures38,826,456/39,023,288/38,848,584 retained bytes and is red3/3 because its total2MiB assertion is too strict. Those values identify retention but are NOT valid bug proof.
A copy of the complete independent-page workload with restart markers passed once on f3ffccd8 (102,441ms). It is not a reliable failing reproducer. The exact experimental source and XML are preserved on the evidence branch. Historical preceding-lane peaks and failures remain historical, not a fresh3/3 claim.
| Branch | Full head | State |
|---|---|---|
| feature | 03d92736f05b9ff5f262638a956ec3860f094406 | Draft PR; two added tests, one unsupported |
| evidence | d2e6d45bc5a1d0ac27aeb51933041dc42449b23f | Corrected findings, traces, per-test XML, experiment source, local gate runner and proposed removal patch |
| baseline | f3ffccd80cca7ee59a2ffe7c6fe1fa0d7d0614a9 | Requested product baseline preserved |
Draft PR remains OPEN and DRAFT. Proposed removal patch passes git apply --check on the feature head and is not applied. The pending approval names only the unsupported added test; the protected test and valid87MiB reproducer stay. Nothing deployed or published by this lane; no queue or merge action; no CI watch. Existing baseline tests edited:none.
Local working path /code/workspace/kbci2; working files /tmp/fix316p-local; incremental findings /tmp/claude-1000/-code/42ef15de-7f6e-415b-9d4b-ed772e422b6f/scratchpad/out/fix316q-findings.md. Warm checkout and compile cache preserved. All test runners reached terminal states; owned background-process check found zero. Temporary fixture directories close in finally; prior synthetic memory snapshot files have been removed and are not uploaded.
To repeat baseline proof: use the baseline branch, copy only the valid new test source from the feature head into tests/, then run scripts/test.bash --local --test testTrackerRestartBytesStayWithinProductionBudget under a lane slot with LC_ALL=C.UTF-8 and HOME/bin first on PATH. The evidence branch contains the exact slot runner. No full local suite; remote gates are suspended by the common amendment.
Next: resolve the named unsupported-test removal, then design and implement bounded tracker ownership and incremental durable updates, preserving public record behavior and the protected finite-fixture test. Before implementation, write a full ownership/terminal-state table and public tests covering peer changes, failure preservation, restart, in-flight close/interrupt behavior and genuine concurrent updates. The original mixed-owner gate still needs reliable reproduction; do not use the solitary exploratory pass as evidence of a fix. Finish all named restart/results/tracker gates and the missing final batch invocation, with per-test XML and sampled peaks. READY remains unmet.
No status reports yet.
Moves it out of every priority list and into ArchiveArea.