Current Status
State: partially ready after read-only retention-preview dogfood on August 6, 2026. Safety, live-thread protection, default text/JSON behavior, diagnostics, and five bounded enabled-policy pages passed; no eligible candidate was observed.
Next action: exercise a later page or aged/synthetic corpus that yields at least one candidate, then validate its reason, proposed compression path, and recoverable-byte estimate while repeating the non-mutation inventory.
Blocked by: no native issue blocker.
Waiting for: a corpus or later page containing at least one eligible candidate.
Last verified: August 14, 2026 during the full open-issue audit; no newer candidate-path evidence was found.
Finish Line
Every Code session storage remains fully resumable for active and explicitly retained sessions while terminal/inactive rollout history is compressed or archived under a documented bounded policy. Users can preview and apply cleanup safely, active leases are never removed, storage growth is observable, and migration/retention behavior has automated tests.
Next Action
Run the enabled-policy JSON preview against an aged/synthetic corpus or continue to a later page until at least one candidate appears. Validate the candidate reason, proposed compression path, and recoverable-byte estimate, and repeat the before/after existence, size, and mtime inventory to prove the candidate branch remains read-only.
Relationships
Current Status
State: partially ready after read-only retention-preview dogfood on August 6, 2026. Safety, live-thread protection, default text/JSON behavior, diagnostics, and five bounded enabled-policy pages passed; no eligible candidate was observed.
Next action: exercise a later page or aged/synthetic corpus that yields at least one candidate, then validate its reason, proposed compression path, and recoverable-byte estimate while repeating the non-mutation inventory.
Blocked by: no native issue blocker.
Waiting for: a corpus or later page containing at least one eligible candidate.
Last verified: August 14, 2026 during the full open-issue audit; no newer candidate-path evidence was found.
Finish Line
Every Code session storage remains fully resumable for active and explicitly retained sessions while terminal/inactive rollout history is compressed or archived under a documented bounded policy. Users can preview and apply cleanup safely, active leases are never removed, storage growth is observable, and migration/retention behavior has automated tests.
Next Action
Run the enabled-policy JSON preview against an aged/synthetic corpus or continue to a later page until at least one candidate appears. Validate the candidate reason, proposed compression path, and recoverable-byte estimate, and repeat the before/after existence, size, and mtime inventory to prove the candidate branch remains read-only.
Relationships