digital-garbageandClaude Opus 5
89e4b24b59
The sandbox was a claim the code could not make. `panels.js` said "no DOM node, no document... a module cannot style anything because it is never handed anything that could" -- while handing over `composer`, whose factories return handles wrapping a real element. A module could take one, style it, and reach the whole document through node.ownerDocument. No lint to evade, just the intended API. No module ever used it. Panels are rendered from the DECLARATION, and a module that wants to draw something should be declaring it. So it is gone, and the guarantee is now true as stated: the kit hands a module nothing that touches the DOM. What is NOT claimed any more: that a module CANNOT reach the DOM. A ui.js is an ES module in the page realm and `document` is a global. kit_lint is a discipline check, not a boundary -- globalThis["docu"+"ment"] defeats every regex and always will. It now catches the bracket-access spellings, which were the first thing tried and went straight through, and says plainly what it is and is not. The test that was supposed to protect this asserted "no value IS a node" while a value that MAKES nodes sat in the same object. It checks what it names now. And the overlay compaction test computed a before-snapshot and discarded it with `void before`, checking only that survivors do not collide -- true even if nothing ever moves. Two attempts to fix it failed against CORRECT code (earlier tests leave live claims, so the rung has a legitimate gap; and some demos close themselves, so closing them again is a no-op). It now opens two overlays of its own so the invariant runs every time, and removing notify() from zlayer fails three tests instead of none. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.