Contract legacy orchestration after coordinator cutover

[maajix]

Parent

#5

What to build

Complete the expand-contract migration by removing redundant prompt-only scheduling and obsolete mode behavior after every command and agent uses the coordinator, while preserving existing engagement compatibility and keeping the full safety suite green.

Acceptance criteria

• Existing version-1 engagement state remains readable or is migrated explicitly without being treated as coverage-complete.
• No command or completion path maintains a competing authoritative scheduler.
• Obsolete command-mode identity behavior and duplicate convergence rules are removed.
• Command, agent, and operator documentation describes the final command semantics and campaign outcomes consistently.
• Static contract tests are retained only for wiring that cannot be tested through the coordinator seam.
• The complete Python, shell, scope, rules-of-engagement, audit, reporting, and workflow regression suites pass.
• The working implementation has one authoritative completion decision.

Blocked by

• Deliver the autonomous full-pentest command #14 — Deliver the autonomous full-pentest command

[maajix]

Implemented in 6137933 on branch agent/autonomous-campaign-coordinator. Full Python (159) + shell regression suites green.