Drop the retired draw node from the agent-facing docs

[mikkel]

Two separate untruths on the same agent-facing pages, plus the guard that stops them coming back.

1. The retired draw node

The 🎨 Draw node retired on 2026-07-22. Its Gemini omni model left the NanoGPT catalog.

The runtime is already correct. The editor does not register the type. Both headless executors treat it as an unknown type: they warn on load and throw UnsupportedNodeError at run(), before any network call. The documentation was not correct. Four live surfaces still presented draw as a current, usable node type. An agent that reads those surfaces writes a graph that cannot run.

• llms-full.txt:158 listed draw in the node catalog.
• llms-full.txt:259 and llms-full.txt:378 listed draw in both NanoGPT node tables.
• guide/graph-format.html:132 said "(LLM/Draw vision references)".
• guide/graph-format.html:158 was a full table row for the draw type and its fields.
• guide/run-headless.html:135 listed draw among the nodes that run headlessly.
• growth/i18n-drafts/zenn-comfyui-ja.md:81 advertised Draw. That draft is unposted, so the claim never shipped. It also described Draw wrongly, as a hand-drawing input.

(Line numbers are as of 552b41f^, the tip before this branch.)

llms-full.txt is generated by scripts/gen-llms-full.mjs, and the header says "do not edit by hand". The file was stale. All 3 draw mentions came from sources that dropped draw already: index.html for the node catalog, and the nanoodle-js and nanoodle-py READMEs for the 2 tables. I regenerated the file instead of editing it. The regeneration also picks up unrelated README drift that built up since the last run, so the diff is larger than the draw fix alone.

guide/graph-format.html loses the draw row and the "LLM/Draw" port note. It gains a "Retired type" bullet under Loader rules. That was a deliberate call. The page documents the file format, not the menu. An author who holds a graph saved before 2026-07-22 opens the JSON, finds a draw node, and comes to this page for an answer. Deletion alone gives no answer. The new bullet states the retirement date, states that old graphs still load, and names the repair: image to generate, edit to edit a wired image.

growth/i18n-drafts/zenn-comfyui-ja.md names Join instead of Draw.

Historical records stay untouched. changelog.html, updates.json, feed.xml, docs/ and proof/ still record that the node existed and then retired. The changelog entry that announces the retirement is correct and stays.

Legacy compatibility is untouched. No runtime code changed.

2. "Not supported headlessly" was false

Review of the first commit caught a second untruth in the same paragraphs, and llms-full.txt in that same commit contradicted it.

guide/run-headless.html: Browser-only media-processing nodes (resize, vframes, combine, soundtrack, trim, extractaudio) are not supported headlessly: workflows containing them load with a warning and fail fast at run(), before any network call.

guide/graph-format.html: the headless executors reject them up front, before any paid call.

Both are false. The truth, read off the executors:

• nanoodle-js/src/local-media.mjs implements all 6 ops headlessly. It runs a pure-JS path first (PNG resize through its own PNG codec, PCM-WAV trim, MP4CAT lossless mp4 concat) and shells out to ffmpeg/ffprobe on PATH for everything else.
• nanoodle-py/src/nanoodle/local_media.py has no pure path. All 6 shell out to ffmpeg.
• Neither library marks any node type unsupported. nanoodle-py's graph.UNSUPPORTED_TYPES evaluates to the empty tuple; nanoodle-js's graph.mjs lists all 6 as local: true. UnsupportedNodeError is raised only for an unknown node type (workflow.mjs:183-188, workflow.py:208-215) — which is what a legacy draw node is, and the only case the up-front refusal covers.
• nanoodle-mcp/src/ffmpeg-check.mjs warns at startup when ffmpeg is missing, for exactly these 6 types. It would have nothing to warn about if they could not run.

A false "not supported" costs an agent a capability it has. A false "supported" costs a failed paid run. So the fix states it per node and per language:

node	JavaScript	Python
resize	pure JS for a PNG source; ffmpeg for any other format	ffmpeg
trim	pure JS for a PCM WAV source; ffmpeg for any other format	ffmpeg
combine	pure JS lossless mp4 remux when every clip is mp4 with matching stream parameters; ffmpeg otherwise	ffmpeg
vframes	ffmpeg	ffmpeg
soundtrack	ffmpeg	ffmpeg
extractaudio	ffmpeg	ffmpeg

guide/run-headless.html carries that table plus one thing the old text got backwards in the reader's favour: a missing-ffmpeg error does not arrive before any paid call. It arrives when that node's turn comes, so paid nodes upstream have already spent. The page says so and tells you to prove your setup with a media-only graph first. guide/graph-format.html's "runs" column now reads local media instead of browser-only and links to that table.

3. Nothing stopped the staleness returning

No guard checked llms-full.txt: none of the 51 scripts/check-*.mjs mentioned it, and scripts/gen-llms-full.mjs was not in .githooks/pre-commit. Worse, its clone() returned the cached .tmp-libs/<repo> whenever README.md existed and never re-fetched, so a future regeneration could silently reproduce a months-old library README. The file was correct by luck.

• scripts/gen-llms-full.mjs now hard-resets the cached clone to the remote default branch on every run, and fails loudly (naming the fix) when it cannot. --offline reuses the cache and says so. --check regenerates and diffs instead of writing. NANOODLE_JS / NANOODLE_PY read a local checkout instead of cloning. Its section builders are exported so a guard can rebuild them.
• scripts/check-llms-full.mjs (new) is offline and deterministic. It regenerates every section sourced from this repo (llms.txt, README.md, index.html) and diffs byte for byte, then asserts every node type named in the two libraries' supported-node tables is still registered in index.html — the exact check the three stale draw rows would have failed.
• .githooks/pre-commit runs it when llms-full.txt, llms.txt, README.md, index.html or either script is staged.
• .github/workflows/checks.yml checks out nanoodle-py as well and runs gen-llms-full.mjs --check against both fresh siblings. That covers the library sections the offline guard cannot rebuild, and it needs no network beyond the checkouts.

How I verified it

• grep -rniE "🎨|\bdraw\b" . over the whole repo, minus .git, vendor/ and proof/. The only remaining hits are canvas code (drawImage, drawFinderPattern, "draw rect"), the image node's search keyword string at index.html:6042, and the historical records listed above.
• node scripts/gen-llms-full.mjs, then grep -n draw llms-full.txt returns nothing.
• node scripts/gen-llms-full.mjs --check passes against freshly fetched clones of both libraries, and again through the NANOODLE_JS / NANOODLE_PY local-checkout path that CI uses.
• The new guard was proved to fail, not just to pass. Injecting a draw cell into a supported-node row fails it with the node-key message. Renaming a catalog entry fails it with a byte diff naming the line. Editing a cached library README and regenerating fails both the generator's --check and the guard.
• All 53 guards run clean on the updated branch: for f in scripts/check-*.mjs; do node "$f"; done → 53 pass, 0 fail. (51 at the branch point, 52 after growth: refresh the 4 slipped launches, remove the stale r/mcp gate, add a launch checklist #373 added check-launch-facts.mjs, 53 with check-llms-full.mjs.)
• scripts/check-js-parity.mjs runs, and does not skip, against nanoodle-js at its main tip: 24 scenarios match.
• The pre-commit hook passed on every commit without --no-verify.

I did not touch index.html, play.html, growth/shares.md, growth/launch-checklist.md, README.md, or the built-with-nanoodle links.

Updated to main before merge

main moved to 89f998c (#373) after this branch was written. I merged it in (no rebase, no force-push). Two resolutions:

.githooks/pre-commit — #373 and this branch both edited the same one-line early-exit chain, and both appended a guard numbered 41). I unioned them, so the chain now carries touches_launchfacts and touches_llmsfull, and #373's guard keeps 41) while this branch's becomes 42). #373's 3-line comment above the chain is kept.

A dropped clause is a guard that never runs, so I proved the union instead of reading it. Staging one modified file into a scratch index and running the real hook with a node that only names the script it was handed:

staged file	guards that ran
growth/launch-checklist.md	check-launch-facts.mjs
llms-full.txt	check-llms-full.mjs
README.md (in both patterns)	check-launch-facts.mjs, check-llms-full.mjs

llms-full.txt — nanoodle-py 0.5.0 landed (nanoodle-py#11, nanoodle-py#12) after this branch generated the file, and it rewrote two sections the generator copies verbatim: ## Quickstart (library) and ## CLI. The committed file described 0.4.0, so the new CI step would have gone red on merge. Regenerating adds 88 lines: the breaking input-key rename in 0.5.0 with its per-workflow key table, optional input nodes, run-wide timeout= releasing its workers, prompt length caps, and --json printing the same envelope on a failed run.

That regeneration is also the proof the clone() fix works. The cache held stale checkouts, and the run refreshed both before reading them — nanoodle-py 91741de → deea945, nanoodle-js a900ed1 → bff73bb. The old clone() would have re-emitted 0.4.0 and said nothing.

Related

Same false claim, different repo: nanoodlecom/nanoodle-skill#5 fixes references/graph-format.md, which called the 6 media nodes browser-only while that skill's own SKILL.md said the opposite.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	nanoodle	571cedf	Commit Preview URL Branch Preview URL	Jul 30 2026, 12:15 AM