gza-summarylisted

# Gza Summary Produce an operator triage summary by combining dedicated gza surfaces, then recommend the next concrete actions. ## Process ### Step 1: Gather task data Run these commands to collect the canonical source data: **Failed-task history:** ```bash uv run gza history --status failed ``` **Unimplemented plan/explore work:** ```bash uv run gza advance --unimplemented ``` Until `uv run gza unimplemented` exists, `uv run gza advance --unimplemented` is the canonical surface. **Unmerged code work:** ```bash uv run gza unmerged ``` **Queue state, including blocked rows:** ```bash uv run gza next --all ``` **Optional failed-recovery decision surface:** ```bash uv run gza watch --restart-failed --dry-run ``` ### Step 2: Analyze the output Treat each command as the authoritative surface for one domain: **From `uv run gza history --status failed`:** - Treat this as factual failed-task history, including attempts that were later retried or resumed successfully - Suggest factual follow-up like `uv run gza log <full prefixed task id>` when operators need details - Use `uv run gza watch --restart-failed --dry-run` when operators need the current failed-task recovery decision surface - Do not treat this as a replacement for the old mixed-bucket `gza incomplete` output **From `uv run gza unmerged`:** - Each listed row is completed code work that still needs merge/review/sync attention - Prefer gza-native guidance like `uv run gza merge <full prefixed task id>` or `uv r