promoting-work-log-lessonslisted

# promoting-work-log-lessons The `/writing-work-logs` skill writes a durable narrative after each task, and its Step 4 asks the author to fold generalizable lessons into the rules **in the same change set**. That step is discretionary and single-log: the same agent that just wrote one log decides, in the moment, whether a lesson is worth promoting. Nothing ever looks _across_ logs. So a lesson that shows up once and is skipped as "too specific" can recur three logs later and still never reach `.claude/rules/` — the loop leaks. This skill closes that leak. It reads the whole `docs/logs/` corpus at once, finds the lessons that recur (recurrence is the strongest signal that a lesson generalizes), and promotes each to the durable home where it will actually change future behavior. A promoted lesson is stamped back in its source logs so the next run skips it — that provenance marker is how the loop stays closed instead of re-proposing the same thing forever. **Three evidence sources, not one** (ADR-0084). Work logs are the narrative record, but they are not the only place this project's lived experience accumulates: | Source | What it is good for | | ------------------------- | ------------------------------------------------------------------------ | | `docs/logs/*.md` | Narrative cause-and-effect: what was tried, what broke, what fixed it. | | The auto-memory store | Facts a past session j