Bring the roadmap up to date and prepare v2.3.0 - #213
Merged
404SecNotFound merged 1 commit intoSep 26, 2026
Merged
404SecNotFound merged 1 commit into
404SecNotFound merged 1 commit into
Conversation
The roadmap's sequencing table stopped at 4.5. Everything #210 landed is now a row: the end-to-end review fixes, the FORMAT-V2-DESIGN §4.8 password-and-shares slot, the paper vault's second pass (set code, presets, version-25 symbols, self-contained strips, the printout check), photo and live camera scanning, and RECOVERY.md being executed by recovery_test.py. Phase 8 now says what it waits on: the owner, after the next tag. The Cut table's steganography row records why the audio carrier stays: it is documented as a carrier, not steganography, and claims nothing that row cuts. TEN-X-PLAN.md said Bet 1 (camera scanning) was on hold in three places. It shipped in 22c7cdf and 161e919, and the decoder decision that held it was taken as BarcodeDetector where present and pinned jsqr where not. The plan now says so, and says what from the sketch did not ship. Release prep: package.json and the lockfile go to 2.3.0, a minor version because the changelog carries an additive format change (slot type 0x03), and the changelog's Unreleased section becomes the v2.3.0 heading. SECURITY.md's supported-versions table names only "latest release" and needs no change. Gates run on this tree: test:release-notes, test:release-gate and test:release-recipe all pass. The tag itself is the owner's to push: git tag -a v2.3.0 and git push origin v2.3.0.
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.
Stacked on #212 (shares
CHANGELOG.md); GitHub retargets tomainwhen #212 merges. Docs and version only, no code.Roadmap drift
recovery_test.py. Phase 8 now says what it waits on: the owner, after the next tag.docs/FORMAT-AUDIO-STEGO.mddocuments it as a carrier, not steganography, and it claims nothing that row cuts.22c7cdfand161e919; the decoder decision that held it was taken asBarcodeDetectorwhere present and pinnedjsqrwhere not. The plan now says so, and says what from the sketch did not ship (arrival detection from the printed URL, a separate Heir Mode).Release prep
package.jsonand the lockfile to 2.3.0. Minor, because the changelog carries an additive format change (slot type0x03). If the owner wants a different number, only these two files and the changelog heading change.## Unreleasedbecomes## Keymaker v2.3.0.SECURITY.mdsupported-versions table names only "latest release", so it needs no change.Gates
test:release-notes,test:release-gate,test:release-recipeall pass on this tree. The browser version tests readpackage.json, so they follow the bump.Owner action after merge
An annotated tag:
release.ymlrefuses a lightweight one, and the message becomes the release's "What changed".Generated by Claude Code