chore: sync gh-aw workflows to upstream HEAD (cb66d12 → 524090c)

.github/aw/actions-lock.json

@@ -1,9 +1,9 @@
 {
   "entries": {
-    "github/gh-aw-actions/setup@v0.68.3": {
+    "github/gh-aw-actions/setup@v0.68.7": {
       "repo": "github/gh-aw-actions/setup",
-      "version": "v0.68.3",
-      "sha": "ba90f2186d7ad780ec640f364005fa24e797b360"
+      "version": "v0.68.7",
+      "sha": "69af89ae134d818caa7743b23ad966ce03914a27"
     }
   }
 }

.github/workflows/implementer-agent.md

@@ -144,4 +144,4 @@ If `inputs.iteration` is greater than 3:
 - Never add dependencies that aren't in the plan. If the plan implies one, pick the minimal option and document in PR body.
 - If the plan is wrong (contradicts the spec, impossible in this repo): stop, do NOT open a partial PR. Add `state:blocked` on the issue and post a comment explaining what's wrong with the plan. A human will resolve.
 - One concern per PR. If the plan isn't scoped that way, that's a planner bug — report via state:blocked + comment.
-- The dispatch in step 7 is the real handoff. `state:review-needed` is decorative.
+- The dispatch in step 7 is the real handoff. `state:review-needed` is decorative.

.github/workflows/planner-agent.md

@@ -52,7 +52,7 @@ safe-outputs:
   dispatch-workflow:
     workflows: [implementer-agent]
     max: 1
-source: verkyyi/github-agent-runner/catalog/agent-team/planner-agent.md@cb66d12806d7f00d220f11e964bc27dfec672913
+source: verkyyi/github-agent-runner/catalog/agent-team/planner-agent.md@524090c08c194faea62a6368059258ec7d310b95
 ---
 
 # Planner Agent

.github/workflows/reviewer-agent.md

@@ -68,7 +68,7 @@ safe-outputs:
   dispatch-workflow:
     workflows: [implementer-agent]
     max: 1
-source: verkyyi/github-agent-runner/catalog/agent-team/reviewer-agent.md@cb66d12806d7f00d220f11e964bc27dfec672913
+source: verkyyi/github-agent-runner/catalog/agent-team/reviewer-agent.md@524090c08c194faea62a6368059258ec7d310b95
 ---
 
 # Reviewer Agent
@@ -143,7 +143,15 @@ Then take the **one** action matching the verdict:
   <!-- /agent-team:summary -->
   ```
 
-  To fill in the `<spec-run-id>`, `<plan-run-id>`, `<impl-run-id>` fields: use `gh run list --workflow=<name>.yml --json databaseId,createdAt,conclusion --limit 10` and pick the most recent successful run of each stage that precedes yours in time. If a run-id lookup fails for any stage, write `(run link unavailable)` in that row instead of guessing — don't block the pipeline on a cosmetic link.
+  To fill in the `<spec-run-id>`, `<plan-run-id>`, `<impl-run-id>` fields, use the workflow display name (not the file name):
+
+  ```
+  gh run list --workflow="Spec Agent"        --json databaseId,createdAt,conclusion --limit 10
+  gh run list --workflow="Planner Agent"     --json databaseId,createdAt,conclusion --limit 10
+  gh run list --workflow="Implementer Agent" --json databaseId,createdAt,conclusion --limit 10
+  ```
+
+  Pick the most recent **successful** run of each stage that precedes yours in time. If a run-id lookup fails for any stage, write `(run link unavailable)` in that row instead of guessing — don't block the pipeline on a cosmetic link.
 
 - **Kickback** → Add `state:impl-needed` to the issue (cosmetic breadcrumb). Remove `state:review-needed`. **Dispatch the implementer-agent workflow** with:
     - `issue_number`: from your input

.github/workflows/spec-agent.md

@@ -40,7 +40,7 @@ safe-outputs:
   dispatch-workflow:
     workflows: [planner-agent]
     max: 1
-source: verkyyi/github-agent-runner/catalog/agent-team/spec-agent.md@cb66d12806d7f00d220f11e964bc27dfec672913
+source: verkyyi/github-agent-runner/catalog/agent-team/spec-agent.md@524090c08c194faea62a6368059258ec7d310b95
 ---
 
 # Spec Agent