doc: clarify run-at tactic positions - #253
Merged
Merged
Conversation
ejgallego
force-pushed
the
codex/runat-position-guidance
branch
from
September 7, 2026 14:00
79b57ac to
df47386
Compare
ejgallego
marked this pull request as ready for review
September 7, 2026 14:00
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.
This PR clarifies which proof state a
run-atprobe uses, so tactic replacements are tested at the intended position. It extends the existing Position Semantics reference with the three-linesimpexample and keeps setup and skill reminders brief.Thanks to Bas Spitters (@spitters) for the clear report and reproducer in #239.
goals before/goals afterinspect tactic states without configuring subsequent execution.