1---2name: thrunt-forensics3description: Post-mortem investigation for failed THRUNT workflows — analyzes git history, artifacts, and state to diagnose what went wrong4---567<objective>8Investigate what went wrong during a THRUNT workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.910Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action.11Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation.12</objective>1314<execution_context>15@.github/thrunt-god/workflows/forensics.md16</execution_context>1718<context>19**Data sources:**20- `git log` (recent commits, patterns, time gaps)21- `git status` / `git diff` (uncommitted work, conflicts)22- `.planning/STATE.md` (current position, session history)23- `.planning/HUNTMAP.md` (phase scope and progress)24- `.planning/phases/*/` (PLAN.md, SUMMARY.md, FINDINGS.md, CONTEXT.md)25- `.planning/reports/SESSION_REPORT.md` (last session outcomes)2627**User input:**28- Problem description: $ARGUMENTS (optional — will ask if not provided)29</context>3031<process>32Read and execute the forensics workflow from @.github/thrunt-god/workflows/forensics.md end-to-end.33</process>3435<success_criteria>36- Evidence gathered from all available data sources37- At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)38- Structured forensic report written to `.planning/forensics/report-{timestamp}.md`39- Report presented inline with findings, anomalies, and recommendations40- Interactive investigation offered for deeper analysis41- GitHub issue creation offered if actionable findings exist42</success_criteria>4344<critical_rules>45- **Read-only investigation:** Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.46- **Redact sensitive data:** Strip absolute paths, API keys, tokens from reports and issues.47- **Ground findings in evidence:** Every anomaly must cite specific commits, files, or state data.48- **No speculation without evidence:** If data is insufficient, say so — do not fabricate root causes.49</critical_rules>
3dcom2711