cross-reviewlisted

## Role Sprint-end cross-cutting quality gate, scoped to **product-wide integrity**: the whole-repo `codebase-audit` over the **accumulated codebase at HEAD** — the scope no per-PBI diff review can reach — along the four audit axes (`spec-conformance`, `logic-defect`, `redundancy`, `product-security`) defined in `../codebase-audit/SKILL.md` § Role (axis table lives there). **This skill does not spawn aspect reviewers.** Requirement conformance, functional quality, security, maintainability, and docs consistency are reviewed **per PBI** inside the pipeline before the PBI reaches `awaiting_cross_review`; their review docs and `review_doc_path` are authored there, not here. Do not write `aspect-*.md`, build per-PBI digests, or run any aspect FAIL routing / re-loop in this ceremony. The audit is **non-blocking**: PBIs already passed their per-PBI aspect reviews before reaching this ceremony, so the audit never reverts them. Every finding is PO-adjudicated, and the ones routed to `next_sprint` become draft PBIs for the **next** Sprint (separate `codebase-audit-s{N}.md` report, identity-deduped across Sprints). At ceremony end every reviewed PBI transitions `cross_review → done`. Full audit protocol: `../codebase-audit/SKILL.md` (context (a)) + `../codebase-audit/references/axes.md`. ## Inputs - `state.json` (overall project phase: `pbi_pipeline_active` or `review`) - `backlog.json` → all Sprint PBIs at `status ∈ {awaiting_cross_review, escalated}` (id, title). Only `await