Repository navigation
Release 1.6.8: archive integrity, the start check, permits, check reuse and Haiku 5.5 - #34
Merged
Merged
Conversation
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.
Release 1.6.8: archive integrity, the start check, permits, check reuse and Haiku 5.5.
archive-run re-read the plan and spec from their live paths on every call and replaced any archived copy that differed, so a rerun could leave an archive holding a plan the run never ran. When a run had two launches and only one set of transcripts reached the archive, nothing compared the two. Now archive-run pins the plan and spec to the sha256 the latest setup recorded (the live file, else
git showorgit cat-file --filtersat each recorded setup head) and reportskept,pinned,replacedor aplan_unpinned/spec_unpinnedwarning. It counts the launches the ledger records against those archived (launches_missing, index keylaunches_recorded; the audit adds a gap per missing launch).--ledger DIRarchives from another ledger,--notes FILE...adds hand-written notes, and a run-owned folder'sderive.jsonandsetup.jsonare archived.Also in this release:
checks_failed_at_startinstead ofchecks_failed(still rejected).checks.widening); reference.md says to name shared files rather than folders.--permit) and the ledger, so the task's check is not widened for it.--record-setup,--record-setup-none), and a resumed integration whose merges made no commit reuses an earlier passing check at the same head (scripts/reuse-checks,checks_reused).lighttasks and runs a docs-only final fix and the start check; one that does not finish reruns on Opus. Reviewers and every other gate stay on Opus. run-report has ahaikutier.ledger acceptcovers every reason.Built by the parallel-lanes run r168 on 1.6.7 (11 tasks in 4 lanes and a join, 115 min, 31 agents, no fix rounds; 14 final-review findings, all fixed). The Haiku change was built directly after the run. Before the release, the release branch's archive-run was run on two real past runs in a temp copy of the history folder: plan and spec pinned to the recorded versions, launches 3 of 3 and 2 of 2, and one audit's 54 stale-spec gaps gone. Full suite on Windows (Python 3.15): 1862 tests, 1846 pass, 16 skipped, 0 fail.