reportlisted

# Orchestration Report The user wants an audit report of a completed orchestration. ## Report Generation Protocol 1. **Find the orchestration**: - First, check if `$ARGUMENTS` contains `--export json` or `--export csv`. If so, extract the export format and remove the `--export <format>` flag from `$ARGUMENTS` before proceeding. Store the export format for step 3.5. - If the remaining `$ARGUMENTS` is empty: Use the most recent file in `.orchestray/history/` - If the remaining `$ARGUMENTS` is provided: Find the matching orchestration in `.orchestray/history/` - If no history exists: Report "No completed orchestrations found. Run `/orchestray:run [task]` first." 2. **Read the orchestration record**: Parse the JSON file from history. Also read `.orchestray/history/{orchestration}/events.jsonl` if it exists. Parse each line as JSON. For each parsed event, normalize the type field: use `event.type || event.event` as the canonical event type. This ensures backward compatibility with pre-v2.0.2 events that used `"event"` instead of `"type"` as the key name. Collect all events for this orchestration. 3. **Generate the report** in this format: ``` ## Orchestration Report **Task:** [original task description] **Started:** [timestamp] **Completed:** [timestamp] **Duration:** [elapsed time] **Status:** [success/partial/failure] ### Agent Activity | Agent | Task | Status | Files Changed | |-------|------|--------|---------------| | architect | [subtask] | success | [f