A forge answers every request in its first ten minutes: no 503 "Waking up" on a POST, and no unclean restart after it is made #11155

Why. Probe 2026-11-10 on a forge made seconds earlier: the first "Create app" POST answered 503 "Waking up" and the app was not created; two minutes later /probe-puas/forge/commits/main answered 503 again, and the forge's log showed restarts=4 unclean=4. A buyer's first five minutes had two errors. (/probe-puas/forge/commits/main also answered 404 once the forge was up.)

What.

• Find why a new cell restarted four times uncleanly in its first minutes (read probe-puas's run history and the parent's child forge name=probe-puas log lines) and fix the cause, not the count.
• A request that arrives while a forge wakes is held and answered when it is up (bounded, e.g. 20 s), for POSTs as well as GETs, or is refused before any side effect with a page that retries on its own. A form submit is never lost.
• A forge made within the last ten minutes is not put to sleep by the idle sweep.
• /<org>/forge/commits/main answers on a new forge.

Acceptance. A test makes a cell, then issues a POST during its wake and gets the result, not a 503. The spawn's own proof (the one /forges shows) includes "no unclean restart in the first ten minutes" and alarms when it fails.