docs: correct skill verification claim to PR workflow only (#211)

The skip-if-skill callout in step 13 of the prompt-agent tutorial

claimed the workflow skill triggered a first verification run of

both agentops-pr.yml AND agentops-deploy-dev.yml. That over-claims:

- agentops-pr.yml triggers on pull_request or workflow_dispatch. The

  skill dispatches it as a sanity check, which is the verification run

  step 13 expects users to see in the Actions tab.

- agentops-deploy-dev.yml triggers on push to develop (or

  workflow_dispatch). The skill does not dispatch it. The first real

  run happens at the end of the section, after the user merges the

  baseline PR into the trunk branch.

The callout now mentions only agentops-pr.yml and explicitly tells

the reader that the deploy-dev run will fire later, on the merge.

Also moves the PR #210 changelog entry from [0.3.1] (already

released) to [Unreleased] where it belongs, and folds the correction

into the same entry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: placerda

CHANGELOG.md

@@ -5,24 +5,31 @@ This format follows [Keep a Changelog](https://keepachangelog.com/) and adheres
 
 ## [Unreleased]
 
-## [0.3.1] - 2026-05-29
-
 ### Changed
-- **Tutorials: state directly that the workflow skill already wired the first run.**
+- **Tutorials: skip-if-skill callouts now state the skill's outcome directly and accurately.**
   The `step 13` callout in `docs/tutorial-prompt-agent-quickstart.md` and the
   baseline-run paragraph in `docs/tutorial-end-to-end.md` previously opened
   with "if you used the workflow skill, this is already done…" plus a
   manual-fallback block. That conditional framing was confusing because the
   preceding step (`step 12` of the prompt-agent tutorial, `step 5` of the
   end-to-end tutorial) only documents the workflow-skill path — there is no
   alternative wired-by-hand path the reader could have taken. Both callouts
-  now state the skill's outcome directly ("the workflow skill already
-  committed your changes, pushed `main`, and triggered a first verification
-  run of …"), and the redundant `git add` / `commit` / `push` and
-  `gh workflow run agentops-pr.yml --ref main` blocks have been removed (the
-  skill already triggers the first run). A small `gh run list` /
-  `gh run watch` snippet remains as an opt-in way to wait on the run from
-  the terminal instead of the Actions UI.
+  now state the skill's outcome directly, and the redundant `git add` /
+  `commit` / `push` and `gh workflow run agentops-pr.yml --ref main` blocks
+  have been removed (the skill already triggers the first run). A small
+  `gh run list` / `gh run watch` snippet remains as an opt-in way to wait
+  on the run from the terminal instead of the Actions UI. The previous
+  wording also over-claimed that the skill triggered verification runs of
+  **both** `agentops-pr.yml` and `agentops-deploy-dev.yml`; the skill only
+  dispatches the PR workflow as a sanity check (`workflow_dispatch`), while
+  `agentops-deploy-dev.yml` triggers on the first real merge into the trunk
+  branch. The callout now reflects this accurately and notes that the
+  deploy-dev run happens at the end of the section, not during the skill's
+  setup.
+
+## [0.3.1] - 2026-05-29
+
+### Changed
 - **Tutorials now flag the workflow skill's setup actions as redundant in the manual follow-up steps.**
   When users run the `agentops-workflow` skill in the CI-wiring step of either
   the prompt-agent tutorial (step 12) or the end-to-end tutorial (step 5, the

docs/tutorial-prompt-agent-quickstart.md

@@ -763,16 +763,17 @@ have something to compare against.
 
 The workflow skill in step 12 already committed your local changes,
 pushed `main` to the GitHub remote, and triggered a first verification
-run of both `agentops-pr.yml` and `agentops-deploy-dev.yml` as part of
-its end-to-end setup. Open the repo's **Actions** tab and confirm both
-runs are green:
+run of `agentops-pr.yml` (via `workflow_dispatch`) as part of its
+end-to-end setup. Open the repo's **Actions** tab and confirm both the
+`Stage Foundry prompt candidate (PR)` and `AgentOps eval (PR gate)`
+jobs of that run are green.
 
-- `agentops-pr.yml` — both `Stage Foundry prompt candidate (PR)` and
-  `AgentOps eval (PR gate)` jobs are green.
-- `agentops-deploy-dev.yml` — has a matching run that also went green.
+`agentops-deploy-dev.yml` does not run yet — it triggers on a real
+merge into your trunk branch (or on `workflow_dispatch`), and the first
+merge happens at the end of this section.
 
-If you want to wait on the first PR run from the terminal instead of
-the Actions UI:
+If you want to wait on the first PR-workflow verification run from the
+terminal instead of the Actions UI:
 
 ```powershell
 $runId = gh run list --workflow agentops-pr.yml --branch main --limit 1 --json databaseId --jq '.[0].databaseId'