adversarial-case-builder

# Adversarial Case Builder — the strongest *evidence-bound* objection Build the single strongest evidence-bound case to reject **$ARGUMENTS**, then defend it point-by-point. Emit `adversarial-case-builder.memo.md`. Run **LAST**, AFTER `/evidence-ledger` (so `claims.json` exists) and AFTER the auditor skills (so the merged `*.findings.json` exist). > 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It runs > LAST and synthesizes the ledger + the other auditors' findings into one memo. Even > though it is **memo-only** (the adjudicator caps it at `info`, so it adds no verdict > weight), the no-new-signal cadence rule still applies: its output changes only when > the **ledger / the findings / the paper** change, never with the wall clock. > Schedule the *work that precedes it* — ledger + auditors done → run this **once**. > (Mirrors ARIS's external-cadence doctrine.) > Adapted from ARIS `kill-argument`, with **one deliberate downgrade: memo-only.** In > a forensics pipeline the headline-attack is most useful as a *synthesis of > already-anchored evidence*, not a free-floating LLM critique — that free-floating > mode is exactly the "LLM slop grading LLM slop" failure this repo exists to refuse. > So here every attack point must cite an existing ledger `claim_id` or `finding_id`, > and the skill never emits verdict-bearing findings: `tools/adjudicate_findings.py` > lists `adversarial-case-builder` in `ZERO_WEIGHT_SKILLS` and caps anything from it at > `in...