Post-release manual steps for v0.16.0

`v0.16.0` is published to npm, crates.io, GitHub Releases and the
official MCP Registry. One directory listing still points at the previous
version and cannot be updated from CI.

### Glama build spec

Browser-only:

Replace **Build steps** with the following, leave every other field alone
(in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how
Glama exposes a stdio server), then click **Build & Release**:

```json
[
"curl -fsSL -o /app/sysknife https://github.com/lacs-project/sysknife/releases/download/v0.16.0/sysknife-v0.16.0-linux-x86_64",
"echo \"bd04823c78aefb8cc05604fbe93f019bba9ec7058851da317fc19e43dfea7d1f /app/sysknife\" | sha256sum -c -",
"chmod +x /app/sysknife"
]
```

### Notes

- Checksum above is read from this release's `sha256sums-linux-x86_64.txt`, not hand-copied.
- This does not block users installing `v0.16.0`; it affects discovery only.
- The MCP Registry publish is no longer manual: the `publish-registry` job
authenticates with GitHub Actions OIDC, which is what makes the
`io.github.lacs-project/*` namespace available. A device-code login from a
laptop only ever gets the personal namespace and is rejected with 403.
- Close this issue once both are done.