publish the api documentation from ci
zig build docs generates the reference but nothing served it, so reading it meant cloning the repository and running a local web server, which is required rather than optional: the generated page is a wasm viewer that fetches sources.tar, and opening index.html from the filesystem gives an empty page. The job publishes the output to Codeberg Pages, at https://jcollie.codeberg.page/zig-hidapi/ . It runs in this workflow rather than one of its own because `needs` only refers to jobs within a single workflow, and a separate file could not wait on the tests. Waiting on them is the point: a tree that no longer compiles should not replace the published reference. It is also confined to the default branch, since without that any pushed branch would publish its own documentation over the live site. The git-pages action is pinned to the v2.2.0 commit like the others here, because its `v2` names a branch head that moves. Checked locally that zig build docs writes index.html, main.js, main.wasm and sources.tar into zig-out/docs, which is what the publish step is pointed at. Note that sources.tar is around 17 MB, and the action commits it to the pages branch on every push to main. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011JRTRSt3F4KkHY7ip2MgEk