Note what the docs site left open

This commit is contained in:
2026-08-22 05:57:29 +02:00
parent 6efb40f1fe
commit 7db3e304ff
+9
View File
@@ -274,3 +274,12 @@ Open on purpose. Each names what should bring it back.
"Fail extracting tarball" for several packages at once, and succeeds on a plain rebuild. "Fail extracting tarball" for several packages at once, and succeeds on a plain rebuild.
It looks like concurrent extraction under memory pressure. Pin down or retry in the It looks like concurrent extraction under memory pressure. Pin down or retry in the
Dockerfile if it starts costing CI time. NOTE: memory lifted; retry and close if stale Dockerfile if it starts costing CI time. NOTE: memory lifted; retry and close if stale
- CHORE/DOCS: `docs/` (the published site) documents `device` and `device_policy` as
API-only, because the node panel has no field for either. That is the one place the
public docs have to say "use the API instead of the UI". Adding a Device section to
`NodePanel.tsx` — a label field plus a require/prefer toggle — would close it.
- CHORE/DOCS: the site's node-type reference is hand-written from `NODE_TYPES` and each
node's `Params`. It will drift. `GET /flows/node-types` already returns the whole thing
with its schemas, so a generator (the way n3xd generates its command catalog) is the
obvious fix once the type list stops moving.