chore: promote mechanism notes to LESSONS.md on first occurrence - #106
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a review-memory run files a lint-rule or test issue for a note, the note now also goes into LESSONS.md, even the first time it shows up. It carries a
Mechanism: #<issue>line until that issue lands. Before this change, the first scheduled run (#105) marked the #99 note for a mechanism but left it in the inbox. Agents never read the inbox, so nobody would have seen the lesson, and the two-review rule would have deleted it in two weeks, probably before #104 is done.This PR also does by hand what #105 should have done. It adds the #99 lesson to the
implement-issuesection withMechanism: #104and removes the note from the inbox. The LESSONS.md header now describes the optional third line.Not user-visible, so there's no changelog entry.