Use one engagement identity across command phases

[maajix]

Parent

#5

What to build

Make recon, pentest, and report resumable phases of one engagement identity so a pentester can move between the independent commands without archiving useful state or receiving a stale-context failure.

Acceptance criteria

• Running recon, then pentest, then report against unchanged scope and configuration resumes one engagement identity.
• The current phase is durable and survives interruption.
• Recon, pentest, and report remain independently invokable.
• A real scope, configuration, or source-identity change still fails closed as stale.
• Synthetic integration tests prove all supported phase transitions.

Blocked by

• Introduce the campaign coordinator compatibility seam #6 — Introduce the campaign coordinator compatibility seam

[maajix]

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