pbi-pipelinelisted

## Inputs - PBI assignment (backlog.json entry for assigned PBI) - requirements.md path - Related catalog specs (read-only references) - .scrum/config.json - 6 PBI Pipeline sub-agent definitions (subset of the 11 catalog sub-agents verified by install-subagents): `pbi-designer`, `pbi-implementer`, `pbi-ut-author`, `codex-design-reviewer`, `codex-impl-reviewer`, `codex-ut-reviewer` - 5 Integrity-stage aspect reviewer definitions (the remaining catalog sub-agents), spawned in the per-PBI Integrity stage: `requirement-conformance-reviewer`, `functional-quality-reviewer`, `security-reviewer`, `maintainability-reviewer`, `docs-consistency-reviewer` ## Outputs - Source code + test code committed to the PBI branch in the PBI worktree via `.scrum/scripts/commit-pbi.sh`. Never commit directly with raw `git commit`: a raw `git commit -A` would stage the `.scrum -> ../../../.scrum` symlink that `create-pbi-worktree.sh` installs, and that symlink would then propagate to `main` on the per-PBI merge. `commit-pbi.sh` does a two-step `git add -A` then `git reset --quiet HEAD -- .scrum` to drop the symlink; only the wrapper is safe. (The single-step pathspec form `git add -A -- ':!.scrum'` returned rc=1 under git 2.36+ when `.scrum` is already gitignored — see `commit-pbi.sh`'s in-file comment for the rationale.) - .scrum/pbi/<pbi-id>/ artifacts (design, reviews, metrics, feedback, summaries, pipeline.log, ut/ac-coverage-r{n}.json) - backlog.json `items[