release: v0.6.27 — clear review residuals (disk leak, validator contracts, exit-2 coverage, roadmap drift)#13
Merged
Merged
Conversation
…esidual) saveState pruned terminal jobs past MAX_JOBS out of the persisted list but never deleted their on-disk artifacts, so the jobs dir grew unbounded as terminal history aged. It now removes the result envelope, config file, and log file for every terminal job dropped from the persisted set (active jobs are never pruned, so only aged-out terminal history is reclaimed). Added removeJobLogFile and wired the previously-dead removeJobFile export. Test: 105 terminal + 1 active job; the dropped oldest terminal job's result/config/log are removed while the kept newest terminal job and the active job retain theirs.
…ution path (review) - validate-fixture-metadata: enforce the docs/capture-fixtures.md contract — provider must match the fixture directory and name must match the file stem (a qwen/stream-success.meta.json with provider:"claude", name:"wrong-success" no longer passes). Added two rejection tests; the 17 shipped fixtures already comply. - opencode adapter: export runCompanion with an injectable spawn so the exit-2 soft-signal is tested at the execution layer (returns the stdout envelope on exit 2; throws with error.stdout attached on a hard exit 1), not only via the isHardCompanionFailure predicate.
Bump 0.6.26 -> 0.6.27 and add docs/release-notes-v0.6.27.md. Fix the docs/roadmap.md Current-state section + Snapshot line that still said the latest public release was v0.6.24 / 'not yet published' (only the Snapshot line had been touched before); advanced to v0.6.27 with nothing unreleased pending. Refreshed the README (en/zh/ja) Latest-release sections. A repo-wide scan confirms no other release-state claim is stale (docs/release.md stays v0.6.26 until publish, updated at mark-published). polycli-utils/timing keep their independent semver.
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
1 participant
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.
Clears the remaining residuals from the v0.6.26 Codex review. Three commits.
fix: reclaim disk artifacts for terminal jobs pruned past MAX_JOBS (residual) (
7871f28)saveStatepruned terminal jobs pastMAX_JOBSout of the persisted list but never deleted their on-disk artifacts, so the jobs dir grew unbounded. It now removes the result envelope, config, and log file for every terminal job dropped from the persisted set (active jobs are never pruned). AddedremoveJobLogFile, wired the previously-deadremoveJobFile. Test: dropped oldest terminal job's artifacts removed; kept newest + active retained.test: enforce fixture path/meta contract + cover OpenCode exit-2 execution path (review) (
d8089eb)validate-fixture-metadatanow enforces thedocs/capture-fixtures.mdcontract:providermatches the directory,namematches the file stem (aprovider:"claude", name:"wrong-success"inqwen/stream-success.meta.jsonno longer passes). Two rejection tests; the 17 shipped fixtures already comply.runCompanionis exported with an injectable spawn, so the exit-2 soft-signal is tested at the execution layer (returns stdout envelope on exit 2; throws witherror.stdouton hard exit 1), not just viaisHardCompanionFailure.release: prepare v0.6.27 + sync roadmap release-state drift (review) (
9d82e7f)docs/release-notes-v0.6.27.md.docs/roadmap.mdCurrent state section + Snapshot line that still said the latest release was v0.6.24 / "not yet published" (the prior PR only touched the Snapshot line). A repo-wide scan confirms no other release-state claim is stale.Verification (local):
npm test559/559,npm run release:checkexit 0 (bundles 5, fixture 17 with the new path/meta check, codex adapter 5, plugin validation, publish/pack dry-runs). Path B preserved.