#1122 Capture lede decisions as an accumulating corpus

[williamthorsen]

What

After a pull request merges, agents are now instructed to ask the author whether the agent's lede (the paragraph summarizing the change) shipped as written or was rewritten before merge. Each decision adds to a body of evidence for refining the lede guidance: the agent's draft, the text that shipped, and the guidance in force at the time. A pull request that merged elsewhere can be recorded on request.

Why

Every lede rewrite discarded the knowledge that produced it. A ## What section was replaced with a better one, and the pair — what was wrong, what fixed it — existed only for the moment of the edit. Nothing accumulated, so refining the lede guidance had no evidence base and proceeded from recall.

The texts were already on disk, in the pull-request and merge artifacts, but the author's judgment about them was not, and it cannot be recovered from the texts. A third of the differing pairs in history are heavy rewrites that partly reflect commits landed during review rather than lede refinements, and a lede that shipped unchanged is ambiguous between "this was good" and "there was no time to fix it."

Details

🎉 Features

• A decision is recorded only when the author affirms one. Declining writes nothing, and the absence of a record explicitly does not mean the lede was accepted — a lede that shipped unchanged under time pressure is not an accepted lede. The corpus therefore yields less data on a busy week rather than misleading data.
• Records are recallable as a group and by work type, and carry a content fingerprint of the guidance in force, so they group by guidance generation with nothing bookkept at install time.
• The author's explanation is free text. Naming which rule a fix invoked belongs to the refinement pass reading the corpus, not to the moment of capture — a fixed rule list offered at capture time would presuppose which rules matter, which is the question the corpus exists to answer.
• Decisions are stored as knowledge-base events alongside the existing knowledge base, so recall, validation, and store resolution are the ones already in use.

♻️ Refactoring

• The refusal message for a capture with no named store is shared across the helpers that emit it, rather than copied per helper.

🧪 Tests

• Episode resolution, record composition, and the command surface are covered, including each distinct failure code, the artifact shapes taken from real pull-request and merge artifacts, and the case where two ledes differ only by whitespace.

Closes #1122

[github-actions]

Dependency audit

Production dependency audit passed.