Bug

When using archon workflow approve <id> <comment> from the CLI, each approval creates a new conversation with a fresh cli-{timestamp}-{random} ID instead of continuing in the original conversation. This causes interactive workflows (like archon-interactive-prd) to spawn multiple separate conversations in the Web UI.

Steps to Reproduce

1. Start an interactive workflow: archon workflow run archon-interactive-prd "Build a chat bot"
2. Node initiate runs → pauses at foundation-gate → Conversation 1 created
3. Run archon workflow approve <id> "My answers..." → Conversation 2 created
4. Approve again → Conversation 3 created
5. Approve again → Conversation 4 created

Observed

Single workflow run 4c4ec384... produced 4 separate conversations in the Web UI:

13:18:58 | cli-...-lmxcm3  | Comedy Chat Bot Frontend  ← initial
13:20:46 | cli-...-ittxza  | Comedy Chat Bot Frontend  ← resume after gate 1
13:24:36 | cli-...-5kwolq  | Comedy Chat Bot Frontend  ← resume after gate 2
13:27:38 | cli-...-0onqoi  | Comedy Chat Bot Frontend  ← resume after gate 3

Expected

All workflow steps should appear in a single conversation thread, so the user can follow the full interactive flow in the Web UI.

Cause

Each archon workflow approve invocation is a standalone CLI process that generates a new conversation ID. The resume logic reconnects to the same workflow_run_id but creates a fresh conversation record.

Suggested Fix

The workflow approve command should look up the original conversation ID from the workflow run record (conversation_id or parent_conversation_id) and reuse it for the resumed execution, so all messages stay in one thread.

Related

• fix(workflows): interactive-prd approval gates missing capture_response #1001 — approval gates missing capture_response: true
• fix(workflows): interactive-prd generate node writes to .claude/ which is blocked #1002 — generate node writes to .claude/ which is blocked