edc-delivery-reviewlisted

# Delivery / Architecture Review Review a change along two separate axes: 1. **Goal / Spec Delivery** — did the implementation faithfully satisfy the originating issue, plan, PRD, task, or stated goal? 2. **Architecture Fit** — does the implementation belong in the touched module/layer and preserve the system's documented contracts? Do not merge or rerank the axes. A change can deliver the requested behavior while violating architecture, or fit the architecture while missing the goal. Report both side by side. Use edc-audit for code quality, maintainability, bloat, and test-value analysis. Use edc-review for security and adversarial review. ## Required references Read these bundled references before producing findings: 1. `references/spec-axis.md` — spec source discovery, requirement coverage, missing/partial/wrong/scope-creep taxonomy 2. `references/architecture-axis.md` — EDC context loading, module ownership, source of truth, API/error contract, migration, backward compatibility, rollout checks 3. `references/reporting.md` — side-by-side report format and verdicts ## Scope discipline This skill is read-only. Do not mutate source, tests, git state, context files, or plans. Write only the requested report artifact, or answer in chat if no artifact path was requested. When reviewing a diff, pin the base once and use it consistently: ```bash git rev-parse <base> git diff <base>...HEAD --stat git diff <base>...HEAD --name-only git log <base>..HEAD --oneline ``` If n