confab-assertion-auditlisted

Check whether the given test files would actually catch plausible mutations to the given target source files. This skill's Verify phase is NOT optional — there is no `--skip-verification` flag on this domain's writer script, and `scripts/assertion_audit.py` requires a `--verify-json` argument it will refuse to run without. Do not look for a way to make this run faster by skipping it; the capability does not exist. ## Steps 1. Determine `repo_root`, the target source files, the test files, and (optionally) a named real mutation tool (e.g. `mutmut`) the user wants used. If the user didn't name one, still ask the agent to check whether one is available on PATH before falling back. 2. Optionally build (or reuse, if `confab-cycle` already built one this invocation — see "Shared symbol index" below) a symbol index of the target files for the agent to use as evidence. 3. Dispatch the `assertion-auditor` agent in **Find mode**: give it the target files, test files, the named tool (if any), and the symbol index. Ask for `{"findings": [...]}` where each finding has `toolSource` set (`"real-tool"` if the named tool actually ran and covered that finding, `"llm-reasoned"` with an explicit `fallbackReason` otherwise). Write its output to a scratch JSON file. 4. Dispatch the `assertion-auditor` agent AGAIN, in **Verify mode**, once per Find-phase finding (or as a batch if your dispatch prompt makes the per-finding independence explicit) — a fresh, indep