shoc-pr-review-runner/templates/failure-summary.md

# Failure summary template

Used when a run fails before a review could be produced. Classify the failure
(spec §22) before reporting it — never disguise an environment failure as a
code result, and never blame the PR for an inherited or environmental problem.

- Workflow run: <run URL>
- Failed stage: <resolve | checkout | backend gates | frontend gates | evidence | agent | validation>
- Classification: delta defect | inherited-base issue | governance issue | review-environment issue
- What happened: <exact error, with log path in the run artifacts>
- Evidence preserved: <artifact names>
- Next step: <re-run | fix PR | fix runner | escalate>
feat: SHOC PR review runner, phase 1 Manually-dispatched GitHub Actions workflow that reviews SHOC pull requests in a clean environment: exact-head checkout of shoc-frontend-new and shoc-backend, clean build/test gates, a truthful evidence report, a single-shot Fireworks review, deterministic output validation, and published artifacts. The runner never writes to the product repositories or their pull requests. The review checklists move here from the reviewers' local Cursor commands so the instructions live outside both product repos. Phase 1 does not provision a database, start either application, or run live browser flows; the evidence report records those as NOT_RUN so a review cannot claim them. Security architecture: building a PR executes its author's code, so the workflow is split. The gates job runs that code holding no Fireworks key and revokes its App token first; the review job holds the key, executes no product code, and re-checks out this repo fresh. Product checkouts live outside the workspace, the App token is downscoped at mint time, gate results fail closed on any duplicate key, changed files are read from git objects rather than the filesystem, and the validator re-checks every claim against the gate table. 2026-07-29 12:04:27 -04:00			`# Failure summary template`

			`Used when a run fails before a review could be produced. Classify the failure`
			`(spec §22) before reporting it — never disguise an environment failure as a`
			`code result, and never blame the PR for an inherited or environmental problem.`

			`- Workflow run: <run URL>`
			`- Failed stage: <resolve \| checkout \| backend gates \| frontend gates \| evidence \| agent \| validation>`
			`- Classification: delta defect \| inherited-base issue \| governance issue \| review-environment issue`
			`- What happened: <exact error, with log path in the run artifacts>`
			`- Evidence preserved: <artifact names>`
			`- Next step: <re-run \| fix PR \| fix runner \| escalate>`