Improve skills and document updates

.agents/skills/beatsaber-plugin-update-auditor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: beatsaber-plugin-update-auditor
-description: Audit Beat Saber plugin-helper locks for available plugin updates and follow-up work. Use when the user asks to check all Beat Saber plugins for updates, compare locked mods against GitHub or BeatMods, review plugin/version compatibility tracking notes, identify PR/local/manual builds that need follow-up, or skip paid/private Patreon and Discord plugin sources during update checks.
+description: Audit Beat Saber plugin-helper locks for available plugin updates and follow-up work. Use when the user asks to check all Beat Saber plugins for updates, compare locked mods against GitHub or BeatMods, review plugin/version compatibility tracking notes, identify PR/local/manual builds that need follow-up, or skip paid/private Patreon and Discord plugin sources during update checks. Read docs/notes/update-checks/<version>/ before the audit and add a new markdown file there when the audit finishes.
 ---
 
 # Beat Saber Plugin Update Auditor
@@ -32,7 +32,14 @@ Before auditing, read the shared policy references:
    PYTHONPATH=src .venv/bin/python -m plugin_helper instances
    ```
 
-3. Run the update audit with repo-local state unless the user explicitly targets
+3. Read the update journal for that Beat Saber version before drawing
+   conclusions. Journals live under `docs/notes/update-checks/<version>/`, one
+   directory per game version, with as many markdown files as needed (usually
+   one dated file per check). List the directory and read the recent files.
+   Treat them as prior findings, not as a substitute for a fresh audit. If the
+   directory does not exist yet, create it when recording this check.
+
+4. Run the update audit with repo-local state unless the user explicitly targets
    another configured profile:
 
    ```bash
@@ -44,7 +51,7 @@ Before auditing, read the shared policy references:
    verified metadata, skips `patreon/` and `discord/` sources, and marks local,
    PR, manual, failed-trial, or pending-smoke entries as review items.
 
-4. Read the active compatibility tracker before proposing updates for review
+5. Read the active compatibility tracker before proposing updates for review
    items. For the current migration notes, inspect:
 
    ```bash
@@ -53,15 +60,22 @@ Before auditing, read the shared policy references:
    ```
 
    Follow up on rows marked failed, omitted, currently failed, smoke blocked,
-   manual resmoke pending, local build, PR build, or local/private. Do not
-   reinstall failed or omitted plugins unless the notes identify a newer
-   compatible source.
+   manual resmoke pending, local build, PR build, or local/private. The lock
+   `reason` and `docs/notes/update-checks/<version>/` are the current record.
+   When an older note says a plugin was removed and the lock still has a local
+   or pull-request build, the lock wins. Correct that note in the same change.
+   Do not reinstall failed or omitted plugins unless the lock or journal
+   identifies a newer compatible source.
 
-5. For each public update candidate, inspect source notes before changing the
+   To see what BeatMods has for one mod, query `status=all` for that game
+   version and filter by mod name in the client. BeatMods ignores `search` and
+   `name`. An empty verified list is not the whole catalog.
+
+6. For each public update candidate, inspect source notes before changing the
    lock. Follow the shared artifact policy for GitHub-first sourcing and
    BeatMods fallback cases.
 
-6. Do not attempt automated public update checks for:
+7. Do not attempt automated public update checks for:
 
    - `patreon/NalulunaModAssistant` or Naluluna bundles
    - `discord/BeatSaberPlus` or BeatSaberPlus/ChatPlexSDK bundles
@@ -69,7 +83,7 @@ Before auditing, read the shared policy references:
 
    Report them as skipped/manual follow-up only.
 
-7. If the user asks to apply an update, switch to the `beatsaber-plugin-manager`
+8. If the user asks to apply an update, switch to the `beatsaber-plugin-manager`
    workflow for download, lock update, planning, apply, and smoketest.
 
 ## Output
@@ -84,3 +98,15 @@ Summarize in four groups:
 
 Mention BeatMods/GitHub API errors separately from "no update found"; those are
 unknowns, not proof that the plugin is current.
+
+## Journal
+
+After the audit, add a new markdown file. Do not rewrite earlier journal files.
+
+```text
+docs/notes/update-checks/<beat-saber-version>/<YYYY-MM-DD>.md
+```
+
+Use `<YYYY-MM-DD>-<short-slug>.md` when that date already has an entry. Keep
+the note short: date, instance, the four summary groups, and any comparison
+that changed a recommendation. A version directory may hold many files.