feat(doos): add container runtime, audit cases, example demo and tests

- New rootless doos container runtime: sandbox, cgroup, network, images, hardening, davmount, CLI plus molo integration
- 18 CVE audit reproductions with READMEs and Makefiles
- Example DoosDemo routes, IndexCatalog, static assets, spec update
- CLI serve on 0.0.0.0:8000, arg parser, dev server improvements
- Runtime HTTP fixes, supervisor isolation backend
- Tests for doos, example doos routes, CLI serve; suite count 261 to 265
This commit is contained in:
2026-11-06 04:36:00 +01:00
parent a2a737e21d
commit 0595284fe3
170 changed files with 12212 additions and 145 deletions
+18
View File
@@ -7,6 +7,15 @@ owning sibling plan and the file that will close it.
## Behaviors
1. `GET /` renders the coverage matrix from a template with inheritance.
Rows are grouped into themed sections by route prefix (`IndexCatalog`,
`example/app/IndexCatalog.cpp`); a route matching no group lands in
"Other" and fails `index_test`. Groups whose demos need credentials carry
a "needs API key" badge. Each row is `<td><a href="ROUTE">Name</a></td>`
(the crawl marker used by `matrix_test` and `tools/verify_deploy.py`),
with the route repeated in a column that hides below 40rem. A filter box
(`/static/index.js`) hides non-matching rows; without JavaScript the full
list shows. Adding a feature stays `add_feature(name, route)`; adding a
route under a new prefix means adding the prefix to a group.
2. Every matrix row resolves to a live route, a test file, and a plan link.
3. Every test drives the real stack: TestClient -> middleware -> router ->
view -> in-memory services, plus one real loopback HTTP round-trip.
@@ -79,6 +88,15 @@ owning sibling plan and the file that will close it.
at `/ai/<v>` (compat, mistral, cohere, perplexity, bedrock, azure,
huggingface, audio, media, retrieval). Same contract as items 17 and 18.
Every `/google` and `/ai` route is excluded from locust.
20. Sandboxed containers (`src/doos`, the real framework part): `GET /doos`
renders the container page, `GET /doos/status` returns containers,
images, davmounts and the libdoos version as JSON, `POST /doos/create`
idempotently creates (name plus optional size/memory/net),
`POST /doos/delete` dry-runs unless `confirm=yes`. Validation failures
answer 422 with every failure listed; a missing container answers 404.
All four run on a demo store (`DOOS_HOME` when the harness sets it,
else `build/doos-demo`), never the user's real store; real container
starts stay out of the demo (see `src/doos/SPEC.md`, Framework seams).
## Caps