chore(site): retire GitHub Pages — ultralog.co builds from releases

.github/workflows/release.yml

@@ -442,3 +442,13 @@ jobs:
             Users must explicitly opt-in to view pre-releases.
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      # Rebuild ultralog.co (ClassicMiniDIY/ultralog-site) now that the release and its assets
+      # exist. A `release: published` workflow cannot do this: GitHub does not start workflows
+      # from events caused by GITHUB_TOKEN, which created this release. The site's daily scheduled
+      # build is the backstop, so a failed dispatch (an expired token) does not fail the release.
+      - name: Rebuild ultralog.co
+        continue-on-error: true
+        env:
+          GH_TOKEN: ${{ secrets.SITE_DISPATCH_TOKEN }}
+        run: gh api repos/ClassicMiniDIY/ultralog-site/dispatches -f event_type=app-release

.github/workflows/site-dispatch.yml

@@ -0,0 +1,22 @@
+name: Rebuild ultralog.co
+
+# release.yml dispatches the site rebuild for the releases it creates. This covers what happens
+# afterwards with a personal token, which does start workflows: notes written with
+# `gh release edit`, a release published or deleted by hand.
+on:
+  release:
+    types: [published, edited, deleted]
+
+permissions: {}
+
+jobs:
+  dispatch:
+    # Forks have no SITE_DISPATCH_TOKEN; skip instead of failing red.
+    if: github.repository == 'ClassicMiniDIY/UltraLog'
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - name: Dispatch app-release to ClassicMiniDIY/ultralog-site
+        env:
+          GH_TOKEN: ${{ secrets.SITE_DISPATCH_TOKEN }}
+        run: gh api repos/ClassicMiniDIY/ultralog-site/dispatches -f event_type=app-release

CLAUDE.md

@@ -15,6 +15,16 @@ The wiki is managed as a separate Git repository (standard GitHub wiki setup). W
 - User-facing wiki pages (User-Guide.md, Supported-ECU-Formats.md, etc.) go in the wiki repo
 - The wiki repo is typically located adjacent to the main repo (e.g., `../UltraLog.wiki/`)
 
+**Website (ultralog.co):** a separate repo, `ClassicMiniDIY/ultralog-site` (Nuxt 4, a static
+Cloudflare Worker), usually at `../ultralog-site/`. GitHub Pages and `docs/index.html` are retired.
+The site builds from this repo's GitHub releases and from the wiki, so a release needs no site
+edit: the last step of `release.yml` sends a `repository_dispatch` (`app-release`) to the site
+repo, and `.github/workflows/site-dispatch.yml` does the same when a release is edited, published
+or deleted by hand. Both use the `SITE_DISPATCH_TOKEN` secret (a fine-grained PAT with Contents
+write on `ultralog-site` only). That is needed because a release created with `GITHUB_TOKEN`
+starts no other workflow, so `release: published` never fires for releases from `release.yml`.
+Wiki edits go live with the site's next build (daily, or on any dispatch).
+
 ## Project Overview
 
 UltraLog is a high-performance ECU (Engine Control Unit) log viewer written in pure Rust. It parses log files from automotive ECUs (Haltech, ECUMaster, RomRaider, Speeduino, rusEFI, AiM, Link, etc.) and displays channel data as interactive time-series graphs with support for computed/virtual channels derived from mathematical formulas.

scripts/bump-version.sh

@@ -4,7 +4,9 @@
 # Updates the version in all locations:
 #   - Cargo.toml
 #   - README.md (version badge)
-#   - docs/index.html (version badge)
+#
+# ultralog.co (ClassicMiniDIY/ultralog-site) takes its version from the GitHub release and
+# rebuilds when release.yml publishes one, so there is no site file to bump here.
 #
 # Usage: ./scripts/bump-version.sh <new-version>
 # Example: ./scripts/bump-version.sh 1.7.0
@@ -41,7 +43,6 @@ SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
 CARGO_TOML="$PROJECT_ROOT/Cargo.toml"
 README="$PROJECT_ROOT/README.md"
-DOCS_INDEX="$PROJECT_ROOT/docs/index.html"
 
 # Check if Cargo.toml exists
 if [ ! -f "$CARGO_TOML" ]; then
@@ -90,16 +91,6 @@ else
     echo -e "  ${YELLOW}Skipped (file not found)${NC}"
 fi
 
-# Update docs/index.html version badge
-if [ -f "$DOCS_INDEX" ]; then
-    echo "Updating docs/index.html..."
-    sed -i.bak "s/>v$CURRENT_VERSION</>v$NEW_VERSION</g" "$DOCS_INDEX"
-    rm -f "$DOCS_INDEX.bak"
-    echo -e "  ${GREEN}Done${NC}"
-else
-    echo -e "  ${YELLOW}Skipped (file not found)${NC}"
-fi
-
 # Update Cargo.lock by running cargo check
 echo "Updating Cargo.lock..."
 cd "$PROJECT_ROOT"
@@ -112,7 +103,6 @@ echo ""
 echo "Files updated:"
 echo "  - Cargo.toml"
 echo "  - README.md"
-echo "  - docs/index.html"
 echo "  - Cargo.lock"
 echo ""
 echo "Next steps:"