dos-unsticklisted

# dos-unstick — the recurring-blocker remediation sweep > **Stop the cause, not the instance.** A one-off unblock fixes today's stall; > `/dos-unstick` asks the different question — *what keeps blocking progress > across runs, and what one change would unblock it?* It mines the run archive, > normalizes every blocker to a canonical **cause key**, clusters the recurring > ones, ranks by recurrence × measured stall-cost, and proposes a **structural** > fix per cluster. Read-only; it writes no code and surfaces findings, never acts. The shape: **mine the trail → key each blocker → cluster the recurring ones → rank → propose a structural fix → surface.** The recurrence fold is the kernel's (`recurring_wedge`); the cause TAXONOMY is `[reasons]` data — a host adds a cause by declaring a reason, never by editing this skill. ## Inputs - `--runs <N>` (optional) — how many most-recent runs to sweep (default: a recent window). `--since <Nd|Nh>` overrides with a time window. - `--min-recurrence <N>` (optional) — a cause is "recurring" at N+ distinct runs (default 2 — the `recurring_wedge` `DEFAULT_MIN_RECURRENCE`). ## Step 0 — Discover the layout + the cause taxonomy ```bash dos doctor --workspace . --json ``` Read `paths.runs` (the run-archive dir to sweep) and run `dos man wedge` to read the **closed reason vocabulary** — the canonical cause keys this workspace knows. **Use these; never hardcode a run path or a cause string.** A cause the workspace cares about is a declared