docs: record stable 0.1.2 release evidence - #47
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
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.
Summary\n\n- record the completed stable 0.1.2 public options and permanent tag-bound release evidence\n- update roadmap, compatibility, release runbook, and durable agent guidance to remain release-neutral while preserving dated immutable evidence\n- document the finite attestation-convergence replay and final control state\n\n## Verification\n\n- npm run format:check\n- npm run lint\n- npm run typecheck\n- focused docs/release tests: 494 passed\n- git diff --check\n- full npm run verify reached all offline gates and reported 576 tests, but the final self-contained check correctly stopped because this documentation PR worktree was intentionally dirty; CI will run the clean copied-tree gate