Prepare production configuration

The deployment pins a supported Node version, injects secrets, uses an external session store, and documents its proxy chain. That contrast gives us something useful to test instead of a rule to memorize.

Local defaults are not production architecture, especially for memory state, cookies, proxy metadata, and shutdown. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.

The happy path can hide a bad design: you can promote the local process and memory store unchanged because the demo passed and still get one successful demo. Push past the demo. create a production checklist from the application trust boundaries and verify it in a staging environment, then test the condition most likely to prove the choice wrong.

The module is moving toward one outcome: Ship the notes app with black-box tests, production controls, and a failure matrix that can be rerun after changes. Save the before-and-after evidence now; it will make the final project review much more honest.

Deploy a disposable staging copy and verify cookies, IPs, limits, persistence, logs, health, and shutdown. Save the evidence, then explain which requirement would force you to choose a different design.