← Commit history

dev skill: proven dashboard release ritual; package.json slug -> fusion-bridge

John Lauer ·77f4d1893b ·1mo ago ·parent b2d603a
1 file changed +20−8
dev-skills/fusion-dashboard/SKILL.md+20−8
@@ -77,14 +77,26 @@ fusion-dashboard status                                 # one-shot JSON (the LED - Dock Bar: registers the dashboard URL as this bridge's dock entry (see the wiki Dock   Bar docs; the dock click = open the URL on the user's preferred surface). -## Build + release ritual (added to the publish loop)--1. `cd dashboard && cargo build --release` (musl static if possible - the container is-   the target; pin the binary in `pkg/bin/`).-2. The pkg tarball = skills/ + bin/fusion-dashboard + pkg.json postinstall that links it-   onto PATH. `adom-wiki pkg publish` as before.-3. The BRIDGE zip is unchanged by dashboard work - do not bloat it.-4. Version the dashboard with the bridge (one BRIDGE_VERSION everywhere).+## Build + release ritual (PROVEN live, v1.9.42, 2026-08-16 - follow exactly)++1. `cd dashboard && cargo build --release` (tiny_http + serde_json only; opt-level="z",+   lto, strip -> ~640KB). The UI is `include_str!`d, so the binary is the whole app.+2. **The binary is a RELEASE ASSET, never tarball content** (the wiki linter enforces+   PKG_VS_RELEASE): `adom-wiki release upload adom/fusion-bridge <ver> bin/fusion-dashboard+   --platform linux --arch x64`. Download URL:+   `https://wiki.adom.inc/download/adom/fusion-bridge/<ver>/fusion-dashboard`.+3. `install.sh` downloads that URL to /usr/local/bin (fallback ~/.local/bin) + chmod +x.+   Bump `DASH_VERSION` in install.sh each release (it pins the asset version).+4. Publish the pkg with **`adompkg publish --org adom --yes`** from the repo root.+   ⚠ package.json `slug` must be `fusion-bridge` (the PAGE slug) - it was+   `adom-desktop-fusion-bridge` for ages and adompkg treated the publish as a NEW page+   (and demanded a Hero Studio hero). `adom-wiki pkg publish` keys off the same file.+5. The BRIDGE zip is unchanged by dashboard work - do not bloat it (release-files.txt+   does not list dashboard/).+6. Version the dashboard with the bridge (one BRIDGE_VERSION everywhere: Cargo.toml+   `version`, install.sh DASH_VERSION, page.json/package.json version).+7. Verify the circle end-to-end: `adom-wiki pkg install adom/fusion-bridge` in a container+   -> `fusion-dashboard health` -> `serve` -> `curl /api/status` returns live LEDs.  ## SDK evangelism