← Commit history

publish skill: pkg-vs-release doctrine (lean files allowlist, binary via release, fresh-home install proof)

John Lauer ·700c410c7d ·3mo ago ·parent 5e8805c
1 file changed +14−2
publish-skills/adom-tts-publish/SKILL.md+14−2
@@ -41,11 +41,23 @@ description: >-    ./build.sh && install -m 0755 target/release/adom-tts ~/.local/bin/adom-tts    ``` -3. **Publish the package** (bundles `skills/` + install scripts; auto-excludes-   `dev-skills/` and `publish-skills/` from the tarball):+3. **Publish the LEAN package + upload the binary as a RELEASE asset.**+   What goes where (per pup-bridge-publish, verified here at v1.9.23):+   - **pkg tarball** = manifest + install/uninstall scripts + `skills/**` ++     `completions/**` ONLY (~17 KB). Enforced by the `files` allowlist in+     package.json — never remove it. NO src/, NO pngs/heroes (those are page+     assets via repo push), NO binaries. `dev-skills/` + `publish-skills/`+     are auto-excluded by the CLI.+   - **release asset** = the compiled binary, per platform. install.sh+     downloads it (`adom-wiki release download adom/adom-tts <ver>+     --platform linux`) — that's why the page has a Download card.    ```bash+   adom-wiki pkg pack --json   # VERIFY lean (<25 KB, ~9 files) BEFORE publishing    adom-wiki pkg publish --org adom+   adom-wiki release upload adom/adom-tts X.Y.Z target/release/adom-tts --platform linux    ```+   Then prove the loop: `HOME=$(mktemp -d) adom-wiki pkg install adom/adom-tts`+   and run `$HOME/.local/bin/adom-tts --version` from that fresh home.  4. **Push the source** — README, src/, screenshots, page.json, and the dev +    publish skills (they reach the page ONLY via repo push; the Skills tab shows