Count occupied restarts as failed missions; sync published Workshop version

docs/discord-changelog-ci.md

@@ -44,23 +44,33 @@ headings inside code examples within an entry. Keep the formatted newest entry
 within Discord's 2000-character limit; oversized entries fail without truncation.
 The dated files in `publishing/` remain separate Workshop release notes.
 
-After compiling/bundling and successfully publishing in Workbench, run:
+Before preparing every push, synchronize the last published version automatically:
 
 ```sh
-python3 tools/workshop_changelog.py --published
+python3 tools/workshop_changelog.py --sync --native-compat .local/rhs-19-work/compat
 ```
 
-The helper reads `asset.version` from Workbench's local publishing manifest and
-updates `Latest published Workshop version: **0.0.109**` above the changelog
-entries. It verifies the addon ID against `addons/core/addon.gproj`. Use
-`--manifest /path/to/manifest.json` on another installation. Without `--published`
-it only displays the bundle version. The flag confirms that you observed a
-successful upload; the helper does not upload or query the Workshop.
+This workstation uses the game's live public Workshop catalogue because the web
+listing can lag behind publication. The helper uses the existing disposable
+Proton prefix under `.local`, takes its test-run lock, opens a temporary muted
+headless game profile, queries only this addon, and closes its own processes.
+It neither downloads addons nor uploads or changes Workshop content. The query
+is bounded to 60 seconds and refuses a busy prefix.
 
-Commit that record together with the new player-facing entry and source changes,
-then push. Drone reads the version from Git, without needing Workbench files.
-Updating only the version does not resend the previous entry. The message labels
-it as the last published version, since a Git push can contain newer changes.
+On a machine without that native setup, `--sync` alone reads the official
+Workshop page. It checks the addon ID and the current version's published and
+approved flags. Neither route overwrites a newer recorded publication with an
+older response. Lookup/validation failure leaves the changelog unchanged and
+returns failure; obtain fresh publication evidence before pushing.
+
+`--published` remains available immediately after an observed successful
+Workbench upload. It records the matching local publishing manifest's version;
+without either flag the helper only displays the bundled version. Bundling alone
+is never publication confirmation.
+
+Commit the synchronized preamble with the requested changes. Updating only that
+version does not resend the previous entry. Drone labels it as the last published
+version because a Git push can contain changes newer than the Workshop upload.
 
 The notifier compares `DRONE_COMMIT_BEFORE` with `DRONE_COMMIT_SHA`, covering the
 whole push, even when a documentation commit follows the changelog commit.