feat: workaround decision logs — detection, template, @WA tags, lifecycle (closes #22)

[hailcpy]

Summary

Full implementation of #22 in four commits matching the agreed plan. Design as confirmed: single docs/decisions/ pool, single numbering sequence, type: workaround frontmatter as the contract, NNNN-wa-<slug>.md filename convention, distinct @WA tag prefix (no separate docs directory).

1. judge.py — marker: citations + type-aware sections

• New evidence type marker:"<added line>" — the mirror of removed: over a commit's + lines; pins a workaround's own HACK/pin comment to the commit that introduced it.
• ADRs declare type: in frontmatter; the verifier selects the verifiable section per type (Considered Options for MADRs, Evidence for workaround logs). Absent/unknown → madr, fully backward compatible.

2. analyze.py — detection + record_type routing

• scan_workarounds: deterministic, bounded (20 commits / 4000 added lines per candidate). Strong signals — marker patterns (HACK|WORKAROUND|KLUDGE|XXX, monkey.?patch, polyfill, shim, FIXME/TODO …until/upstream/temporary) in added diff lines, or workaround-shaped file additions (shim/adapter/polyfill, patches/, *.patch) — flip record_type to workaround. Message wording alone is recorded but never flips (prose is too weak).
• An architectural candidate with markers stays a decision with a WORKAROUND: markers present note — the ADR mentions it; no double records.
• Config: detect_workarounds (default on), extra_workaround_markers (project regexes). CLI shows [WA] per candidate.
• New repo_workaround fixture with planted marker / structural / dual / clean cases.

3. Template + docs

• references/workaround-log-template.md: Trigger / Workaround / Evidence / Scope / Removal Condition + worked example + status lifecycle. The Removal Condition is the point — a decision records why, a workaround records until when.
• SKILL.MD routing table + lifecycle section; README section.

4. judge.py — check-workarounds lifecycle command

• For each status: active record: greps its marker: citations in the working tree (markdown excluded so the record's own citation can't satisfy the check) → flags "possibly removed — update status"; flags records with no trackable citations; --check-upstream (opt-in, needs gh) flags linked GitHub issues that have CLOSED → "removal condition may be met".
• Report-only by design; --strict exits 1 for CI.

Test plan

• 174 passed, 1 xfailed (was 156 on main — 18 new tests).
• New coverage: marker verify pass/fail, record-type frontmatter parsing, workaround Evidence kept/dropped/collapse, MADR regression (Evidence section ignored for madr), detection routing on all four planted fixture cases, detection disable + extra-markers config, check-workarounds present/removed/non-active/untrackable/madr-exclusion, end-to-end verify of a record citing the fixture's real HACK line.
• CLI smoke-tested: analyze.py shows [WA] on exactly the two planted workarounds; check-workarounds goes ok → FLAG when the marker is deleted from the tree; --strict exit codes verified.

Closes #22

🤖 Generated with Claude Code