docs: describe the release workflow now that it is merged

The architecture guide, AGENTS.md and the threat model said releases were
built by hand or Windows-first; ADR-0009 still listed the release
workflow as future work. The Windows build guide named the missing
Settings > API Keys tab.
This commit is contained in:
shumeiko.it
2026-11-01 02:21:20 +01:00
parent 608c804482
commit 0e2f3197eb
8 changed files with 20 additions and 16 deletions

View File

@@ -44,6 +44,7 @@ The project owner chose this over publishing the server to npm on 2026-11-01.
tests.
- An archive is about 130 MB (macOS arm64); it is downloaded once per version.
- `install.sh`, `scripts/waggle-server.sh` and their CI job are removed.
- The release workflow must build the archive on each target system (P1.3d).
- The release workflow (`release.yml`) builds the archive on each target system and
smoke-tests the installer against it.
- Windows cannot replace a running program: `update` and `uninstall` there run through `npx`,
and the server must be stopped first.