Add Forge Server Runtime V1 and EP simulator

[pcvantol]

Assignment: L1-FORGE-SERVER-RUNTIME-V1-20260922 / #141 r18.

Scope

• production-grade foreground Forge Server Runtime V1 over the existing Forge application/runtime services;
• explicit existing data root, stable opaque instance identity and one mutating writer lease per instance;
• two independent instances on one machine, each with its own state, listener, auth boundary and provider context;
• authenticated versioned HTTP API plus CLI parity for health, readiness, version/schema/source/artifact, Mission governance/controller, peer configuration/preflight and deployment readback;
• instance-owned provider context with explicit executable, HOME, CODEX_HOME and configuration; no ambient PATH fallback or credential migration;
• deterministic stateful EP HTTP simulator exercised through the production Forge EP HTTP client;
• rolling-planning coverage for terminal-A-before-B and single-action completion without invented work;
• restart, lease, idempotence, stale/conflicting identity and transport-failure qualification;
• OpenAPI, Postman and executable route-drift checks;
• frozen deployment contract, architecture record and operator/update runbooks;
• installed-wheel qualification and production-release workflow gates for the exact published artifact.

Exact-head evidence

Head: cb8a6033c26e1726e117023dc99aa094197c1711

• bash scripts/validate.sh: PASS — 950 tests, one existing opt-in skip;
• PRODUCT_VERSION=PASS version=2.7.33;
• offline generated-projection validation: PASS;
• fresh isolated install from the exact-head wheel: PASS;
• installed qualifier: two simultaneous Server instances, headless foreground start, clean SIGTERM, real EP simulator HTTP boundary, one idempotent submission, no production EP/provider contact;
• candidate wheel SHA-256: 9ed2ccd3507377ffe01d6cebfa6b7aee67942658097194f26a3215952424b1cc.

The candidate wheel hash is implementation-head evidence only. The normal protected version-finalization and release workflow will produce and independently qualify the final 2.7.34 published wheel.

Boundaries

• no Engineering Platform or Forge Platform product mutation;
• no production activation or installation;
• no Mission-3, CENTRAL reset, T0 or new Mission;
• no implicit runtime initialization and no EP proxy route;
• no credential material is persisted in Forge provider context.

FORGE_SERVER_RUNTIME_DEPLOYMENT_CONTRACT = FROZEN