feat(claude): update skills to know about closed tickets

.claude/skills/monthly-review/SKILL.md

@@ -138,7 +138,12 @@ the month was about and where the big threads landed, not the day-to-day.
   few plain sentences: what it was, how it progressed across the month's weeks,
   and where it ended the month (landed / merged / still in flight / handed off).
   Merge a theme that appears in several weekly summaries into one month-level
-  thread rather than repeating it per week.
+  thread rather than repeating it per week. To state where a thread ended with
+  confidence, check the backing story note's location in Joplin: a note in the
+  top-level `Work / Story Logs` is still active, one in
+  `Work / Story Logs / Archive / <year>` is finished (the user archives a story
+  log once its work is done). This confirms landed/closed vs still in flight
+  rather than guessing from the weekly prose alone.
 - **Recurring / continuous work** in a tighter list: bug-fixing load, the areas
   that came up repeatedly (specific subsystems), customer/incoming work, MCP/AI,
   security/ISMS, etc. Mirror the "Recurring areas" / "Continuous work" split in
@@ -172,7 +177,10 @@ month. Cover these three lenses (and only these unless the user asks for more):
      or recurring-story lists and never closed within the month.
    - Repeated rework: rebases of the same big branch, repeated rounds of fixing
      the same failing tests or de-flaking the same suite (e.g. Cypress).
-   - Threads that opened early in the month and were still open at month end.
+   - Threads that opened early in the month and were still open at month end. A
+     thread is genuinely still open if its backing story note is still in the
+     top-level `Work / Story Logs`; if the note has moved to an archive
+     subnotebook it closed within the month, so do not list it as stuck.
    - These are candidates the user may want to push to close or escalate.
 
 3. **Long weeks (only).**