tracebacklisted

# traceback — Delivery Alignment Gate Verify one chain with file evidence: approved source -> implementation -> test mapping -> executed validation traceback is not a linter, test runner, or duplicate code review. Review Gate judges code quality; traceback proves delivery traceability. ## Hard rules 1. Derive requirements only from approved source artifacts. 2. Preserve stable requirement IDs across reruns. 3. Treat summaries as views; 'alignment.json' is the machine truth source. 4. Distinguish test mapping from an actually passed validation run. 5. Re-read files. Never infer coverage from naming or proximity alone. 6. Block stale evidence when source hashes, Git HEAD, or workspace fingerprint changed. 7. Record critical gaps, waivers, and skipped traceback in Canon. ## Input resolution Resolve the first available approved source: 1. Canon task page § Artifacts: 'design_doc_path', 'fix_plan_path', 'acceptance_checklist_path', or public contract. 2. Project + branch -> Canon task page using '/home/yhr/.agents/repos/agent-skills/references/canon-task-resolution.md'. 3. Explicit user-provided path. If no approved source exists, use 'mode: skipped'; record the reason in Canon. Do not invent a specification from code. ## Output contract Write only: .planning/<task-or-workflow-slug>/ ├── alignment.json ├── alignment.md └── traceback-gate.json Read 'references/alignment-schema.md' before creating or updating 'alignment.json'. - 'alignment.jso