docs(#843): document event_payload for run-to-PR correlation

[fullsend-ai-coder]

Summary

• Adds a "Correlating dispatch-repo runs to source-repo PRs" subsection to the "Reading agent logs and artifacts" section in skills/retro-analysis/SKILL.md
• Documents that dispatch-repo run logs contain event_payload JSON with pull_request.head.sha, pull_request.number, and pull_request.base.ref for direct run-to-PR/commit mapping
• Includes a gh run view CLI example for extracting the payload

Context

PR #540 spent 7 review rounds building increasingly complex timestamp-based and branch-name-grep workarounds for run-to-PR correlation, only to discover in round 7 that event_payload provides the mapping directly. This change documents that method in the general tracing section so future agents and skill authors find it upfront.

Complementary to PR #834, which adds event_payload usage within the new flapping-detection section — this covers the general log-reading guidance used by all retro tasks.

Testing

• Verified the new subsection is positioned after the existing artifact-download code block and before the "Exploration strategy" section
• Confirmed no duplication with PR feat(retro): add flapping detection to retro analysis skill #834's flapping-detection section (different sections, different purposes)
• Doc linter (hack/lint-agent-docs) passes
• Secret scan passes

---

Closes #843

Post-script verification

• Branch is not main/master (agent/843-document-event-payload)
• Secret scan passed (gitleaks — 1a3086f5512b3700ab8e081c689cc7586c9af20f..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 1:07 PM UTC · Completed 1:18 PM UTC

Commit: c234e6c · View workflow run →

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] skills/retro-analysis/SKILL.md — This file is under the protected path skills/. The PR links to issue Retro-analysis skill should document event_payload for run-to-PR/commit correlation #843 and provides clear rationale for the documentation addition. Human approval is always required for protected-path changes, regardless of context.

Low

• [edge-case] skills/retro-analysis/SKILL.md:91 — The grep -o 'event_payload.*' command captures from event_payload to end-of-line only. If the event_payload JSON in the log is spread across multiple lines, only the first line would be captured. GitHub Actions structured logs typically use single-line entries, making this unlikely in practice, but the command differs from a jq-based approach that would handle multi-line JSON.

---

Labels: PR is a documentation-only change to a skill file

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[low] edge-case

The grep -o 'event_payload.*' command captures from event_payload to end-of-line only. If the event_payload JSON in the log is spread across multiple lines, only the first line would be captured. GitHub Actions structured logs typically use single-line entries, making this unlikely in practice.

Suggested fix: Consider adding a note that the command assumes single-line JSON log entries, or suggest jq for structured extraction if multi-line output is possible.