coding-session-forensics

To diagnose a stuck DekSpec construction session, analyze git repository and worktree evidence to detect failure fingerprints like orphaned worktrees or mid-red crashes, generating a structured forensic report with root-cause hypotheses and recovery commands.

DekSpec construction sessions fail or hang due to common anomalies like stuck loops, orphaned worktrees, and mid-red crashes. Analyzing git, worktree, and linkage evidence identifies these specific failure fingerprints to determine the root cause.

Perform a post-mortem analysis on a failed coding session by collecting git, worktree, bead, and linkage evidence. This process detects anomalies and outputs a structured forensic report with a root-cause hypothesis and recommended recovery commands.

Yes, you need access to the session's git repository and DekSpec audit tools to analyze a DekSpec session. Evidence collection relies on examining git history, worktrees, and linkage data to accurately detect failure modes.

The best way to recover from an orphaned worktree in DekSpec is to run a forensic analysis to detect the anomaly, then execute the specific recovery commands provided in the generated structured report to restore the session state.