Code Freeze & Release Management

Closest to 'silent in production until users hit it' (d9). The detection_hints confirm 'automated: no' and the code_pattern describes misuse like annual freezes blocking security fixes or freezes not communicated to all teams — these are process failures that produce no compiler, linter, or tool warnings. They only surface when teams feel the pain of a delayed security patch or a last-minute bug wave in production.

Closest to 'touches multiple files / significant refactor in one component' (e5). The quick_fix describes replacing a full code freeze with a deployment freeze combined with feature flags. This isn't a one-line patch — it requires adopting feature flag infrastructure, updating deployment pipelines, and aligning team process across multiple work streams, touching multiple components even if not a full architectural rewrite.

Closest to 'strong gravitational pull' (b7). Code freeze applies to 'web, cli' contexts broadly, tagged as devops and process. A poorly implemented freeze shapes the entire release cadence and affects every team's planning, testing, and delivery rhythm. Every change during the freeze period is evaluated against whether it violates the freeze, creating a persistent gravitational force on all development decisions throughout the freeze window.

Closest to 'serious trap (contradicts how a similar concept works elsewhere)' (t7). The misconception field explicitly states: 'Code freezes always improve quality — long freezes create backlog pressure that rushes QA; feature flags with continuous delivery are more effective.' This is a serious inversion — the intuitive belief (more freeze = better quality) directly contradicts the actual outcome (long freezes compress and degrade QA). Competent developers applying general 'slow down = safer' reasoning will guess wrong.