From f3b9eb1bd3f822042b59ffc4ba18362c6e9577b1 Mon Sep 17 00:00:00 2001 From: stroblme Date: Sat, 22 Aug 2026 05:57:29 +0200 Subject: [PATCH] Note what the docs site left open Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01M7Xv3cJEW5c8AXxn2hoojV --- NOTEPAD.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/NOTEPAD.md b/NOTEPAD.md index 7b14f28..f100f2f 100644 --- a/NOTEPAD.md +++ b/NOTEPAD.md @@ -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. 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 + +- 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.