docs: show steady-state foundry-agent.json (action reused) in step 13#215
Merged
Merged
Conversation
The example JSON in step 13 previously showed action: bootstrapped with candidate_agent: travel-agent:1 and an explanation that the two version numbers are expected to differ until the environment has caught up to the seed. In practice the merge-triggered deploy is almost never the run that bootstraps by the time the user reaches step 13, the skill's verification dispatch in step 12 plus the first PR run have already settled dev to travel-agent:2, so the merge deploy reports action: reused with candidate_agent: travel-agent:2 matching source_agent. The example now: - shows the steady-state shape taken from a real recording, - uses runner-resolved absolute paths the user actually sees /home/runner/work/<your-repo>/..., - uses a real 64-char prompt_sha256 and a real ISO timestamp. The three-outcome list reused / created / bootstrapped below the JSON keeps the bootstrap case as the documented edge condition. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Why
Step 13 of the prompt-agent tutorial showed an example
foundry-agent.jsonwithaction: bootstrappedandcandidate_agent: "travel-agent:1", framed as "if this merge-triggeredrun is the one that finally settles the bootstrap", followed by an
explanation that
source_agentandcandidate_agentare expected todiffer until the env catches up.
In practice this is almost never what the user sees. By the time the
merge-triggered deploy runs at step 13, the skill's verification
dispatch in step 12 + the baseline PR run have already settled dev to
travel-agent:2. The merge deploy therefore reportsaction: reusedwith
source_agent == candidate_agent == travel-agent:2. PO confirmedthis against a real recording of run #26690922142 in
placerda/agentops-prompt-quickstart.What changes
docs/tutorial-prompt-agent-quickstart.mdstep 13:(
action: reused, equalsource_agent/candidate_agent,real-world
prompt_sha256and ISO timestamp).prompt_file/eval_configfrom the user-friendlyrelative paths to the runner-resolved absolute paths that the
artifact actually contains
(
/home/runner/work/<your-repo>/<your-repo>/.agentops/...), with aone-sentence note explaining why.
steady-state case (instead of the bootstrap case).
actionvalues(
reused/created/bootstrapped) so that the bootstrap caseis now documented as a clearly-marked edge condition, not the
primary example.
CHANGELOG.md—[Unreleased] → Fixedentry above the previous"matches what the workflow skill actually does" entry.
Validation
python -m pytest tests/ -x -q→ 802 passed, 3 skipped.Related
https://github.com/placerda/agentops-prompt-quickstart/actions/runs/26690922142
"both workflows verified" claim).