Repository navigation
Ground tour questions in reachable behavior - #47
Merged
Merged
Conversation
This was referenced Nov 12, 2026
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.
Tour explanations could turn a payload-free state into an unsupported transition claim, then ask the reviewer to resolve a problem the repository already rules out. For example,
Retryingcarrying no data does not establish thatShowncan enter it or lose content.Make review questions optional and require their premises to be traced through callers, guards, state writers, and consumers. Apply the same rule to planning and explanation prompts, provide captured Git identities for supporting source, and treat generated objectives as route context rather than facts. Distinguish planned transitions and direct test-state assignments from implemented production paths. Update the attached-agent instructions to match.
Validation: typecheck and 41 focused agent, syntax-evidence, and skill tests passed. Added and prepared three real-model evaluation fixtures covering guarded retries, planned transitions without a controller, and an actually reachable content-dropping retry. Model evaluations have not been run; this changes the generation contract and does not add a deterministic semantic validator or prove model compliance. The reported live review was inspected read-only and was not modified, regenerated, or closed.