ci: the complete gate runs on your machine for src.rest

forge attest runs .forge/ci in a clean worktree of each commit and signs the
result into refs/notes/ci; forge push sends it with the branch. It runs what
ci.yml's legs run: scripts/verify-demo-build.sh with every stage, the
website gate, and the Decky plugin gate with the pinned pnpm 9.4.0.

Cargo's target directory lives in ~/.cache/goq/target, outside the worktree,
so runs don't rebuild every dependency from source. target/ in the worktree
links to it, because the shell tests read target/debug/sigil directly.

forge resets its CI worktree with git clean, which removes the portal-dist/
that src-tauri/build.rs generates while tracked files keep their mtimes, so
with a warm target directory cargo would skip that build script and
tauri::generate_context! would find no frontendDist. .forge/ci touches
portal/runtime-files.txt so the script always runs.

commit

36df5982091d9c182144d24dd590207dc16711ee

parent

69f58398b0d7f3657d82e4c5d7e6e16cce452142

author

cat <admin@dev.site>