ql-deep-review — whole-feature post-implementation review

Purpose

quantum-loop's built-in two-stage review gate (ql-review: spec-compliance → code-quality) operates on ONE story at a time inside ONE worktree. It does not detect:

Cross-story divergence (e.g., story A uses 'google' as a secret key while story B uses 'google-api-key' for the same constant).
Post-merge regressions (test that was green in isolation breaks after integration).
Drift from original user intent (paraphrase chain from intent → design → PRD → plan → code).
Low-signal comments that look like findings but lack evidence (CRA actionability is 0.9-19.2% per Chowdhury 2604.03196; human baseline is ~60%).

ql-deep-review closes these gaps with a whole-feature review that runs AFTER all stories in a wave / feature pass the per-story gate.

When to use

After ql-execute emits COMPLETE for a wave and before merging the feature branch to master.
After cherry-picking or merging a foreign branch whose conflict-resolution changed semantics.
Manually, when suspicion of cross-story drift is high (e.g., follow-on work after a long autonomous run).