Merge branch 'build-stamped-version'

This commit is contained in:
ari committed 2026-10-20 23:38:12 -04:00
commit b3b9103f2f
18 files changed
+322 -18

No files matched your search

+4 -1
View File
@@ -2,7 +2,7 @@
The single place for work tracking. **Tick boxes here only.** Design lives in [`ARCHITECTURE.md`](ARCHITECTURE.md). Archived workstream design notes and logs are in [`docs/workstreams/`](docs/workstreams/). Plans for the next big thing go in [`plan/`](plan/README.md).
_Last updated: 2026-10-20_
_Last updated: 2026-10-21_
## Status
@@ -25,6 +25,7 @@ The build is functionally complete and merged to `main`. REST, MCP, OTel, TLS an
| — | | Nothing in flight |
- [x] **WS-H Gate:** `nix build` and `nix flake check` pass. `ldd` shows no openssl. A fresh NixOS host serves `:1984` and a token can be minted from a login shell.
- [x] **V-1** Build-stamped version `YYYY.MM.DD-<branch>-<sha>` in `--version`, `/healthz`, `/api/v1/ping`, MCP server info and OTel `service.version` (DEC-17). `dev-test lint`, `cargo test`, `nix build` and both VM tests (`vm`, `vm peers`) pass.
## Backlog
@@ -48,6 +49,7 @@ Parked, not scheduled. Each has a reason. Nothing here blocks the current work.
| **P5-5** | Runtime peer management (add/remove without editing config) | Peers are declarative so no write path or DB table exists (DEC-14); would need a write path against the read-only rule |
| **DOC-1** | Show the MCP tools (`x-mcp-tools`) in the Redoc page | Redoc renders REST operations only; needs the tool list generated into a tag description (or a section) in `openapi.rs`, which changes the spec |
| **DOC-2** | Config switch to turn the `/docs` viewer off | Static, public and data-free (DEC-16), so not needed yet; adds a config key, README and `config.example.toml` entries |
| **V-2** | Real branch name in Nix builds (stamp says `nix`) | A flake does not expose its branch; needs CI to pass it to `callPackage` or a release-tag convention |
- [ ] **C7** _(nice-to-have)_ Smoke test against the Podman socket
- [ ] **I6-5** Verification #5 OTel smoke test against a working collector (see the [verification checklist](ARCHITECTURE.md#verification))
@@ -62,6 +64,7 @@ Parked, not scheduled. Each has a reason. Nothing here blocks the current work.
- [ ] **P5-5** Runtime peer management
- [ ] **DOC-1** MCP tools in the Redoc page
- [ ] **DOC-2** Config switch for the `/docs` viewer
- [ ] **V-2** Real branch name in Nix builds instead of the `nix` placeholder
- [ ] **F-1** Cap concurrent follow streams. Each journal follow, `tail_journal` call or docker follow pins a `spawn_blocking` thread for up to `limits.max_follow_secs`. Add a global semaphore shared by REST and MCP (suggested 16) returning 429/503 when full. A client that stops reading may hold the thread past the deadline (untested); add a write timeout or a hard `tokio::time::timeout` around the producer.
- [ ] **F-2** Bound line and message length. Docker `LineSplitter` and journal `MESSAGE` are buffered without limit before the 256 KiB result cap applies. Truncate per line (suggested 64 KiB, with a visible marker) and cap total bytes collected.
- [ ] **F-3** Unit hardening: `ProtectKernelLogs`, `ProtectHostname`, `RemoveIPC`, `LimitNOFILE`, `TasksMax`, `MemoryMax`, narrower `RestrictAddressFamilies`, `PrivateUsers` (check journal group access). Test under the hardened unit on a clean host before enabling. Document how the service user gets read access to the TLS key.