Moonshot In Session Coordinator

Role

Run the phase loop in the current session without letting implementation chatter accumulate here. The current session stays as a thin coordinator. Each implementation/verification round is delegated to a fresh forked phase-attempt-agent.

Use this only when:

• moonshot-phase-runner returned executionMode: in-session-coordinator
• execution artifacts already exist for the active phase

Do not use this for:

• simple one-shot implementation
• delegated terminal runs that already use agent-loop.sh

Execution

• Main session responsibility:
  • select the next actionable phase
  • build minimal attemptInput
  • spawn fresh forked attempts
  • merge summaries only
  • update phase-status.yaml
• Attempt responsibility:
  • run moonshot-orchestrator in phaseAttemptMode