docs: seal teaching against the final staged diff - #16
Merged
Conversation
…docs Know-Code-Verified: ea53884420ab9b9d3935dee90c39602824b352fe040d7847c373487252689c86
chtnnh
marked this pull request as ready for review
August 24, 2026 13:23
PR SummaryCursor Bugbot is generating a summary for commit 6bcf0d8. Configure here. |
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.
Closes #13
Summary
Corrects the documented know-code workflow so teaching is sealed after implementation and staging, against the final intended diff hash.
The previous order told users to run
know-code taughtbefore editing. Any subsequent implementation changed the hash and immediately invalidated that seal, creating unnecessary re-sealing and instructions that disagreed with the CLI’s artifact binding.Documentation updates
Verification
npm run lintnpm run build:docsgit diff --check