Repository navigation
changeset: consolidate the 0.7.0 release notes - #168
Conversation
The 130 pending changesets describe internals as often as they describe what a 0.6.1 user notices, so shipping them verbatim makes the 0.7.0 release body a changelog instead of notes. Fold them into 14 themed entries — the mechanism 0.4.0 used (b21eaff "changeset: consolidate the 0.4.0 release notes") — so `changeset version` writes one curated "what's new" section plus its themed items, and CHANGELOG.md, the GitHub Release body, and the docs site's /changelog stay one text. Every item traces to the changeset that produced it: each item line ends in a hidden `<!-- changesets: ... -->` comment naming its sources, and this message carries the same theme -> sources mapping. Four items cover sibling changesets that describe one behaviour (the author fingerprint, the revert memory, the published review.json key names, and corpus grading), and a change that both adds a feature and breaks a shape appears twice — once in its theme, once under breaking — so no source is lost and no breaking step goes unnamed. Start point: .scratch/factory/roadmap-next/RELEASE-NOTES-draft.md, written against 104 of these changesets. Refreshed against every pending changeset on main 7d488f9: 24 arrived after the draft, and 2 more (backtest-reverts, run-print-stage) predate it but were missing from it. Headline (00-what-s-new.md, 5 sentences): Verdict 0.7.0 is a breadth release. It adds a local code index, a read-only `serve` surface with a browser UI, and a backtest harness that mines past bug fixes from your own history, replays them against your agent, and scores the result. Review output gains an auditable provenance receipt, diff-coverage attestation, advisory risk scoring, and an optional validation pass that floors each finding on the evidence behind it, while the CI gate now checks coverage by default. Posting grows a secret guard, honest per-host capability reporting, and a summary-comment option, GitLab and Forgejo join GitHub as full publish targets, and lens packs, declared recipes, and reported verification make the review pipeline itself data. Thirteen pre-1.0 changes alter behaviour — each names the migration step below — and the known limits close the notes. Theme -> sources (minor unless noted, all under .changeset/): 00-what-s-new.md <- the headline, no items 01-new-commands-and-flags.md <- backtest-mine backtest-replay backtest-reverts backtest-score bounded-foreground-waits fix-all-batch handoff-verb incident-memory ingest-sarif panel-verification post-summary-comment reaction-scoped-fix recipes-format report-html risk-queue run-agent run-print-stage skill-management thread-resolve 02-local-code-index.md <- blast-radius-index-hint fetch-index-impact index-blast-radius index-callers index-corpus-bugs index-graph index-impact-budget index-scanners index-transitive-tests 03-review-quality-and-provenance.md <- author-routing author-routing-hint author-routing-record author-routing-skill author-routing-trend context-sources coverage-scoring-basis diff-coverage-attestation fetch-reverts ignore-overrides ignore-suppression learnings-propose null-ranges-malformed post-content-digest post-content-recovery post-live-authority post-verdict-reconciliation prompt-key-shapes prompt-rigor-key reactions-trend resolution-rate rigor-validation risk-score rule-exposure rule-pack-import withheld-capabilities 04-safety-and-trust.md <- curl-token-argv learnings-evidence line-break-guards mention-neutralization post-secret-guard punctuated-mentions run-argument-credential setup-verdict-hardening skill-install-preflight store-lock-and-listing strikethrough-mentions verify-indirection verify-out-owner-only verify-sandbox verify-sandbox-macos 05-agents-and-mcp.md <- agent-definition-display mcp-config-hosts mcp-mutation-class run-repair-loop self-review-loop 06-hosts-and-ci.md <- doctor-provider-adopt-gitlab forgejo-post github-action gitlab-incremental gitlab-publish ready-calibrate-gitlab 07-serve-and-ui.md <- cache-content-budget cache-small-content inventory-budget-exact serve-live-updates serve-s1 serve-s2-discovery serve-s3-cost-precision serve-ui vanished-threads 08-lens-packs.md <- lens-dispatch-deltas lens-packs-s1 pack-add-backup-warning pack-layers pack-staging-stale pack-test packs-lock 09-measurement.md <- bench-adjudication bench-corpus-followups bench-keyword-guard bench-real-pilot benchmark-clean-controls benchmark-controls-metrics 10-breaking-changes.md <- bench-real-pilot bundle-name-guard gate-coverage-default gate-live-all-hosts gate-tier-validation honest-capabilities index-import-shadow managed-parent-symlinks pack-source-allowlist provenance-receipt provider-from-remote typed-truncation verify-env-allowlist verify-indirection verify-out-owner-only verify-static-gate-bypasses write-bundle-symlinks 11-fixes.md <- backtest-partial-clone fetch-refusal-next-steps next-usage-basis-plain pr-wait-inconsistent-reads read-verb-re-enter record-cost-name-warnings release-asset-sigpipe review-residuals upgrade-hints-quoting windows-watchdog-no-hang windows-watchdog-resume-retry 12-docs.md <- defaults-at-a-glance docs-site-restructure troubleshooting 13-known-limits.md <- verify-indirection verify-sandbox-macos verify-static-gate-bypasses 04-safety-and-trust.md, 11-fixes.md, 12-docs.md, and 13-known-limits.md ship as patch; the rest as minor. One minor changeset is enough to cut 0.7.0. Breaking (13 items in 10-breaking-changes.md), each with its _Migrate:_ step: the `index blast-radius` truncation receipt, `gate` checking coverage by default, `gate --live` reading every host, unknown gate tiers, the default-deny verify child environment, the verify command shapes that used to run (`verify-networked` and the new `verify-indirection` arm), the owner-only `.verify.out`, guarded bundle paths, provider inference from origin, the `capabilities` split, the `pack add` source allowlist, the benchmark `provenance.base_sha`/`head_sha` requirement, and the rebuilt-code-index requirement. Known limits (13-known-limits.md) are the three from STA-436's 2026-11-16 status comment: the macOS sandbox covers the network half only, the string gate is a tripwire rather than a boundary (`sh "$V"` still passes it), and a backslash before a CRLF line ending is not joined as a continuation. Counts: 130 changesets read, 14 consolidated entries, 126 item lines (123 content items plus the 3 known-limit lines), 13 breaking, 5-sentence headline. Verification: bun fmt --check .changeset/*.md -> All 14 files are formatted. go test ./internal/archtest/ -count=1 -> ok (changeset frontmatter guard) bash evals/one.sh doc-coverage -> PASS (135 cases)
The notes are user-facing copy, so a British spelling has no place in them: behaviour -> behavior (00-what-s-new.md, 10-breaking-changes.md) unrecognised -> unrecognized (10-breaking-changes.md) labelled -> labeled (09-measurement.md) Swept all 14 files for the rest of the class — colour, honour, favour, cancelled/-lled, licence, defence, grey, centre, programme, catalogue, modelling, judgement, artefact, towards, whilst, and every -ise/-isation verb — and found no other hit. Copy only: no item, mapping, or bump level moves.
🦋 Changeset detectedLatest commit: 2cb5e0a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedToo many files! This PR contains 144 files, which is 44 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.
|
Part of STA-436 (release 0.7.0).
What
This consolidates the 130 pending changesets into 14 themed, user-facing ones, the same way 0.4.0 did it (
b21eaff, "changeset: consolidate the 0.4.0 release notes"):00–13, becausechangeset versionorders entries by filename._Migrate:_step, and a known-limits list (macOS sandbox network-only; the string gate is a tripwire andsh "$V"passes; backslash before CRLF fails safe).<!-- changesets: … -->mapping to its source changesets.Evidence
docs/manual.md,benchmark.md,troubleshooting.mdandCONTRIBUTING.md.bin/verdict --helpand the source changesets. Its only blocker, four British spellings, is fixed in2cb5e0ad4.bun fmt --check .changeset/*.md, the archtest and thedoc-coverageeval pass.Before the release
Any changeset merged after this PR (for example STA-425's) needs folding into these notes before #58 is merged, or it appears as a raw line.