launch-production-web-productlisted

# Launch Production Web Product Use this Delivery Mission for one end-to-end web-product launch. The mission composes existing SEF contracts; it is not a replacement for Codex or for the project repository. ## Operating rule Treat Project State as the canonical delivery truth. Never claim a higher delivery state because the model believes work is complete. A transition is valid only through the M1 Project State API with the evidence kind required for that target state. ## Inputs the agent structures From the user's outcome, prepare the mission spec with: - one concrete first-delivery outcome; - blocking acceptance criteria; - explicit technical failure surfaces actually present: persistent data, material data change, identity/access, billing and external integrations; - JIT Expertise needs only for selected current/provider/framework contracts that materially affect the mission. Do not ask the user to choose ordinary technical implementation details when repository evidence, authoritative documentation and engineering judgment can resolve them. ## Mission loop 1. Initialize or validate Project State. 2. Read only the state domains returned for the next action. 3. Discover the current Codex tool inventory through the active harness and pass the explicit snapshot to M4. 4. Resolve the tool requirements for the next action. 5. Compile or refresh any required JIT capsules from current authoritative evidence. 6. Load only the Stable Expert Packs returned as active for th