Repository navigation
fix: rank Done retention correctly and prepare guarded fdev archive schedule - #5261
Merged
Merged
Conversation
added 4 commits
November 2, 2026 20:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Done-retention planner excluded live-blocker-protected cards before choosing the newest 200, shifting the retention cutoff. Rank every valid terminal Done card first, keep the newest 200, then protect older blockers. Prepare the guarded daily fdev writer while retaining the hosted counts-only observer.
Refs #5170
The sibling archive installer stages immutable scripts and two disabled user units. It preserves the existing tend installer/runtime-hash/XDG checks and never calls systemd or changes tend configuration. Exact private activation/reader/binding pins, Root's accepted first-real receipt, durable directory/custody anchoring, an unresolved-run latch and strict settled-effect grammar remain mandatory.
Validation and preparation:
569c473f; all 10 registry PR chore: reconcile published coherent 0.114.4 #5260 paths and the accepted report are preserved. The only extra census change is the archiver script SHA. No src/ or tools/ diff. The archive external-route evidence now pins the same reviewed script SHA while preserving its predecessor identity, Root approval date and unresolved writer classification.The candidate is based on actual #5260 merge
07229d66, not its pending7d709fe1head; their trees match. Original archive candidates85b003d/569c473fand pending-basead735826remain preserved. The source preparation performed no installation, activation or native write; original candidates and evidence remain retained.The original CI cohort passed all 10 required contexts but its broader edge check failed on the stale archive external-route SHA. That first failure is retained. A narrow evidence-only repair passed the actual maintained Python structural subgates, all 66 validator selftest identities, and a stale-pin negative control; no CLR or workflow replay was used for the repair. Changed-source hosted qualification remains distinct.
Root retains source/requiredCI integration, current qualified reader/enrollment pairing, first guarded archive with independent readback, and scheduled activation/native proof. This merge continues the same Delivery and cannot claim full #5170 acceptance.
architecture-map: unaffected