[autoform][deicyde] Rebuild execution overlay on main contracts

[zibo-yang]

Summary:
Reconstruct Deicyde/main as an additive execution overlay on cleaned main. Restore Orchestrate, specialist subagents, deterministic claim-backed scheduling, and dependency-free Claude/Codex/Muse prover adapters while consuming the canonical Markdown runtime, claim board, and Lean services owned by main.

Harden execution with post-claim revalidation, unique workers, bounded retries and steering, cancellation-safe subprocess cleanup, compare-and-swap rollback, declaration-level edit confinement, Lean-backed type and axiom verification, and authoritative statement/proof transitions.

Test Plan:

• uv run --extra dev pytest -q tests/test_worker_executor.py tests/test_worker_scheduler.py tests/test_prover_execution.py tests/test_orchestrate_overlay.py (90 passed)
• uv run --extra dev --extra repl ruff check autoform_cli autoform_worker servers tests
• make check-example
• Full pytest: 402 passed, 1 skipped; six unchanged shared Lean-runtime lifecycle tests failed intermittently on macOS and will be gated by Linux CI.

[Deicyde]

Current head should remain draft. Reproduced blockers:

• The axiom-audit module name is derived from the repository path, not Lake's srcDir; the bundled example generates import src.CabannesThesis instead of import CabannesThesis.
• Proof confinement snapshots only Lean and four Lake files, then commits before validating the roadmap transition. Markdown, CI, Python, Git state, unrelated article fields, and unrelated top-level example declarations can change without rollback.
• Statement verification accepts forbidden kinds such as axiom, leaving no proof boundary for the next phase.
• CLI signals never set the cancellation event, so SIGTERM/SIGHUP/SIGINT can orphan a new-session prover after its heartbeat and claim die.
• The CLI proof prompt has drifted from the worker prompt, and the driver window/stdout queue are unbounded for long agent runs.

These are execution-integrity issues, not documentation polish. Keep #44/#54/#55 from landing on this base until the overlay is transactional and the statement/proof contracts have one tested implementation.