Remove lesson status from proof system
The lesson status occupies a semantic niche already filled by close-with-reason. Post-availability adoption data shows 128 findings closed with "accept/intentional" reasons vs. 6 using the lesson command — the workflow voted with its feet. The Learn agent's triage phases produce close, keep, or promote — lesson isn't part of the loop. No agent reads lessons, no command surfaces them, and Ana's own instruction to "surface relevant lessons" via `proof context` is broken because `getProofContext` filters lessons out. Meanwhile, 116 upstream auto-lessons (pipeline forensics about contract quality and tag collisions) dilute the concept so thoroughly that a lesson query would return 95% noise. The status adds a fourth value every consumer must handle while contributing no retrievable information.
Pipeline timeline
Intent to proven code in 14h 31m across Think, Plan, Build, and Verify.
Assertion ledger
28 claims, each independently verified. Showing 8 — show all →
| ID | Says | Matcher | |
|---|---|---|---|
| A001 | The finding status type only allows active, promoted, or closed | verified | ok |
| A002 | Chain health stats no longer track lessons as a separate count | verified | ok |
| A003 | New upstream findings are automatically closed instead of lessoned | verified | ok |
| A004 | New upstream findings record why they were closed | verified | ok |
| A005 | New upstream findings record they were closed mechanically | verified | ok |
| A006 | New upstream findings record when they were closed | verified | ok |
| A007 | Old lesson findings in the proof chain are migrated to closed during work complete | verified | ok |
| A008 | Migrated lessons without existing metadata get default close fields | verified | ok |