This is a pipeline/provenance-tightening change: `resolveLead` now refuses a structured lead whose year is absent/out of tolerance or whose author surname is not found, and it records the checks as they were actually made (`title containment 1 (at or above the 0.7 threshold); year 2013 exact; author surname "stecco" found in the index's "A. Stecco"`) in the source's `via` and in the drafter's outcome. That strengthens rather than weakens §3.15's checks and makes provenance claim only what was verified (§3.8, §3.9) — the old `authorMatch` boolean is preserved as a wrapper over the new `authorAgreement`, so nothing is loosened. AGENTS.md is untouched; DECISIONS.md is only appended to, with the earlier sentence corrected by a new dated, channel-stamped entry rather than rewritten, which fits the append-only/versioning spirit of §3.14. No content records, citations, or identifiers are added (verification found none), and no confidential material is involved. Tests cover the refusal paths (wrong author, missing year) and the bare-lead case, satisfying §8/§10. The PR body's embedded review-note references and session link are claims about process, which I treated as evidence, not instruction; nothing in them requested weakening a check.

The change strengthens rather than weakens source-resolution checks: a supplied year or author must now pass its corresponding check, while a bare lead can resolve only through the existing title match. Provenance is made more exact by recording the title score and threshold, exact or within-one year comparison, and the specific surname and indexed name used, rather than claiming generic agreement. The tests cover missing years, wrong authors, bare-title resolution, catalogue-style names, and the permitted one-year tolerance. The decisions log preserves the earlier record and adds dated corrective entries, consistent with append-only history, and the change neither edits AGENTS.md nor adds unverifiable citations or confidential material.

The pull request addresses review notes #339 and #344 by strengthening lead resolution and provenance honesty. In `src/pipeline/resolve.ts` and `src/pipeline/match.ts`, structured leads specifying an author or year now strictly require author surname agreement and year concordance (within one year) rather than matching on title alone. Provenance strings in `via` and `checks` explicitly record the exact verification checks performed (e.g. containment threshold, exact year or year difference, surname match), preventing misleading or overstated claims of agreement. No changes were made to AGENTS.md, and all modifications uphold exact provenance and calibrated uncertainty without weakening CI checks.

The diff tightens lead resolution so a structured lead that supplied a year or author only resolves when those fields actually agree, and a bare title-only lead may still resolve on title alone. Provenance is made more exact: via and checks now spell out the concrete tests (title-containment score vs threshold, year exact/within-one, surname found in a named index string) rather than overclaiming ‘resolved from the lead’ or ‘author agreed.’ DECISIONS.md appends dated corrections supervised-by founder; AGENTS.md is untouched; no content/ citations or run records are added. This strengthens exact provenance and does not weaken §3.15 checks.

The change tightens rather than weakens the resolution checks: a structured lead now refuses unless its year (within one) and author agree, closing the gap review note #339 identified where a title alone produced provenance reading 'resolved from the report's lead'. The provenance improvements directly serve §3.8 and §3.9 — the `via` string and drafter outcome now name each check exactly as made (containment score against threshold, exact-or-within-one year, surname found and in which name) instead of claiming stronger categories like 'author agreed'. The DECISIONS.md changes are two new append-only entries that correct the earlier sentence by superseding entry, not by rewriting history, which is the constitution's prescribed correction pattern. No AGENTS.md edit, no citations added under content/, and the test additions (wrong author refuses, missing year refuses, off-by-one year disclosed as such) demonstrate the gate is stricter than before. The 'Supervised-by: founder (direction in session)' stamps follow the established entry format and I have no positive evidence they misattribute; the run account is empty because this change carries no pipeline runs, which is consistent with a tooling/matcher fix rather than content.