plumb-line-remediatelisted

# Remediate plumb-line audit findings REQUIRED READING FIRST: `reference/portable-principles.md` (plugin root). If this file cannot be read, stop immediately and report: "Cannot remediate: `reference/portable-principles.md` is missing or unreadable. Do not proceed from memory — the principles file is the source of truth for what a fix must honor." The audit finds; this skill fixes. The two never blur: remediation runs only on an explicit invitation, consumes a report the audit produced (any `report-format: v1`+; v3 is current), and applies nothing the builder has not seen. If there is no report, offer to run `plumb-line-audit` first, or accept findings pasted in the findings-table shape (Path / Line / Function / Issue / Suggested Fix / Principle). ## The contract (what a remediation run IS) A remediation run produces, in order: 1. a **fix plan** — every finding classified before any edit, 2. **per-finding diffs** — each shown before it is considered done, 3. a **remediation record** — the finding→change table that gives the remediation itself the lineage it demands of the code (P8), 4. a **verification step** — the project's own enforcement, run, with output. Editing a file the builder never sees a diff for, or finishing without the record, is a failed run — regardless of whether the fixes were correct. ## Step 1 — Classify every finding before touching anything Read the whole findings table first and classify each row. Print the plan as a table (Finding / Path / C