release: 0.7.0 — images, changelog, and the version cut - #17
Merged
Merged
Conversation
Problem Four pull requests merged into main without a changelog entry between them: the semantic compatibility doctor (#9), the explainable tool-surface review (#8), the capability planner (#7), and the toolchain bump (#15). The Unreleased section described only the Astra lane, so the three most user-visible additions since 0.6.0 existed in the code and in the README but nowhere in the release record. A changelog that silently omits four merges is worse than no changelog, because it is read as complete. Approach Document all four, then cut Unreleased as 0.7.0 and bring the three declared versions into agreement. Minor rather than patch: the release adds a second native implementation lane and three read-only diagnostics. Nothing is removed and no interface breaks, so it is not a major. Each entry records what the thing refuses to do, since that is the part with value: the planner refuses hosts that would silently weaken requested effort or advisor isolation; the review turns "the digest moved" into whether the change is permission-bearing; the doctor no longer reports a marker-only or weakened adapter as healthy. The toolchain entry records why the bump was applied by hand, so the next person does not reopen the Dependabot question. Verification `bun run ci` is green: verify.sh three-role checks pass, 82 tests across 6 files, validate, sbom (now emitting orrery-0.7.0.cdx.json, 18 packaged files, 0 runtime dependencies), and release-check. `bun run tag:check -- v0.7.0` passes, so the tag and all three manifests agree. Impact The release record now matches what shipped. Ready to tag v0.7.0 once merged.
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 last pull request before tagging v0.7.0. Three things: the README images, the release record, and the version cut.
1 · The three README images
docs/images/README.mdhas specified three images since the Astra release. They now exist.constellation.pngflow.pngrefusal.pngEach was checked against the shipped repository rather than accepted on sight. An earlier pass carried a FABLEWRIGHT wordmark and, in the proof image, two role filenames and a command that do not exist here —
orrery-sol-researcher.toml,orrery-terra-ops.toml,fw install. Publishing that would have put a claim on the front page that the shipped files contradict, under the words "LAUNCH PROOF".What is committed uses the real command, the three real filenames, and output whose load-bearing lines are verbatim from an actual run — the
INSTALL PASSEDline, theERROR: Astra destination is conflictline, andexit 1. The narrower progress lines between them are a readable dramatization of steps the installer genuinely performs (destination classification, the legacy-Luna check, the post-install exactness re-check) rather than literal stdout.Alt text describes content rather than naming files, so all three claims survive for anyone reading without images.
2 · The changelog catches up
Four pull requests merged into
mainwithout a changelog entry between them — #9, #8, #7 and #15. TheUnreleasedsection described only the Astra lane, so the three most user-visible additions since 0.6.0 existed in the code and the README but nowhere in the release record. A changelog that omits four merges is worse than none, because it is read as complete.validateso it cannot drift from the digest it explainsschema: 2; a marker-only or weakened adapter is no longer reported as healthytypescript5.9.2 → 7.0.2 (major, no source changes), with why it was applied by hand recordedEach entry leads with what the thing refuses to do, because on this project that is the part with value.
3 · The version cut
Unreleasedbecomes 0.7.0; the three declared versions agree.Minor, not major: a second native implementation lane and three read-only diagnostics are added, nothing is removed, no interface breaks. Whether this should instead be 1.0.0 is a maintainer's call rather than a semver one — and it is arguably the release that earns it.
Verification
VERIFY PASSEDthree-role · 82 tests across 6 files, 0 fail · validate (which link-checks the image paths, so the embeds and the files agree) · sbom now emittingorrery-0.7.0.cdx.json(18 packaged files, 0 runtime dependencies) · release-check · tag-check passes for v0.7.0.Risk
Documentation, images, and version metadata. No code, no behaviour change.