finding-reconciliationlisted

Merge the independent A/B/C findings tables into one adjudicated ledger in `07-verification/documentation-verification-report.md` — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to its own Critical finding, and splitting repairs into agent-repairable and owner-decision. Use when all three verification passes have returned their findings at Phase 9, or when ingesting an externally-produced audit. This skill MUST be consulted because publishing the findings table before repair is what makes the audit trail real, and because treating a lone dissenting pass as noise is exactly the correlated-error failure the three-pass design exists to prevent.
synaptiai/synapti-marketplace · ★ 6 · AI & Automation · score 77

Install: claude install-skill synaptiai/synapti-marketplace

# Finding Reconciliation Phase 9. Turns three independent findings tables into one adjudicated ledger, then drives repair and re-audit. ## Iron Law **PUBLISH THE FINDINGS TABLE BEFORE ANY REPAIR, AND RE-AUDIT IN FRESH CONTEXTS AFTER. A finding seen by one pass is still a finding.** A package that quietly fixes what it found and reports only the clean end state has destroyed its own audit trail. The pre-repair table is the evidence that verification happened. ## Never loaded by a verifier This skill must not appear in any pass agent's `skills:` list. If a verifier could load the merge logic, it would reason about corroboration and drift toward the consensus it expects the other passes to reach — which is the correlated-error failure the whole three-pass architecture exists to prevent. `tests/agent-independence.test.sh` enforces this mechanically. It is a structural guarantee, not a convention. ## Order of operations 1. **Collect raw.** Read each pass's table from `.dossier/runs/<id>/pass-{A,B,C}.md` verbatim. Do not edit, do not summarize, do not reorder. 2. **Normalize** to the canonical field set. 3. **Deduplicate** by `(location_normalized, claim_hash)`. Keep the highest severity. Merge the problem descriptions when they add different context — do not discard the second one's reasoning. 4. **Stamp corroboration** as `N/3`. 5. **Detect disagreement** and promote it. 6. **Publish the pre-repair table.** This is a commit point, not a draft. 7. **Split** into agent-rep