Introduce the campaign coordinator compatibility seam

[maajix]

Parent

#5

What to build

Add a deterministic campaign coordinator command that can load current engagement state, accept campaign events, and return the next eligible work plus an explicit completion outcome without changing existing command behavior. This is the expand step that gives later slices one stable behavioral seam.

Acceptance criteria

• A new engagement and an existing version-1 engagement can both be opened through the coordinator.
• The coordinator accepts a synthetic campaign event and returns durable normalized state plus next-work and completion results.
• Existing lead lifecycle, scope, finding, audit, and command behavior remains compatible.
• Black-box command tests cover the coordinator seam without inspecting internal helpers.
• No active engagement or network target is read by the tests.

Blocked by

• None — can start immediately.

[maajix]

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