Bug Report

Description

When the bmad-quick-dev workflow introduces new type variants, error codes, or DB values, the spec's Code Map only covers the primary code path. Existing consumers of the parent type/column are not enumerated during planning (step-02), leading to regressions in untouched code that the review step (step-04) misclassifies as "pre-existing" (defer) instead of "caused by this story."

Steps to Reproduce

1. Use bmad-quick-dev to implement a bugfix that adds a new error variant to a union type
2. Step-02 planning populates Code Map with only the files being directly modified
3. Other consumers of the union type (shadow copies, string-literal switches, untyped error maps) are not listed
4. Step-04 review correctly finds the gaps via edge-case hunter, but classifier marks them as "defer" because the Code Map has no consumer inventory to cross-reference

Expected Behavior

Step-02 should enumerate all consumers of new type variants/DB values in the Code Map. Step-03 should HALT if consumer tracing was missed.

Proposed Fix

Two minimal additions (~388 chars total): consumer tracing instruction in step-02-plan.md, precondition check in step-03-implement.md.