docs: lead KB with durable session recovery - #23
Merged
Conversation
0thernet
enabled auto-merge (squash)
September 1, 2026 17:33
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.
Outcome
Reorients KB around its durable result: a Markdown note becomes a linked plan, and a later coding-agent session recovers the decision through context, exact search, backlinks, and Git. The public Agent Skill guidance now routes through the same concrete workflow.
Contract impact
No command or persisted format changes. The README keeps the release anchors but moves release notes behind the product narrative, exact install, recovery proof, scope, authority boundary, interfaces, and limits.
Verification
CI owns the repository aggregate gate because the required host scheduler is unavailable in this sandbox.