David decided: Kill assignment planner agents with a simple feature flag

David instructed that assignment planner calls be halted, and when the agent proposed two options — consume the queued changes vs preserve them for replay — David cut through the design debate:

The main design choice is this: while the switch is off, do we want assignment-related changes to be consumed or to remain pending for replay later?

David's answer was direct: he wanted consume mode, then confirmed deployment immediately. He also audited the flag's blast radius:

does this affect module planners or lecture notes in anyway? it shouldnt!!!

Once confirmed it was scope-limited, he committed:

push n commit and set the env vars in production such that it behaves how i want - no assignment plans or runs for now