digital-garbageandClaude Sonnet 5
97e1029ca0
Round 6's sweep of raw API.* calls that bypass Store entirely (a layer none of the prior five rounds checked) found the most easily-triggered gap yet: models.js's "Export settings..." button calls API.settingsCard directly, a real unmocked POST /api/settings-card -- and it's on the FIRST screen the tour's own "models-modal" step shows, no sidebar navigation needed (unlike round 5's Combo Sweep panel, which needed a click into Settings first). Fixed by mocking API.settingsCard with a real Blob (the function resolves a Blob and feeds it straight to URL.createObjectURL, so a JSON mock like every other entry uses would break the button instead of blocking it) -- a 1x1 transparent PNG is enough for the card to render. Also closed the secondary finding: applyGlobalPromptQuiet has TWO internal closure-scoped callers (setEditorSetting's anchorEnabled toggle, applyPromptTemplate) besides its exported Store property -- the same "block the export, miss the internal call" shape as commit()'s original vulnerability, so a patchStore() block-list entry alone couldn't have closed it. It reaches a real, unmocked API.parsePrompt call. Fixed with the same root-cause pattern as commit()'s guard: a window.__FUNPACK_TOUR__ check directly inside the function, which also covers scheduleGlobalPromptApply transitively since that just debounces into a call to this same function. Verified live: API.settingsCard resolves a real 68-byte PNG Blob (not an error); toggling anchorEnabled and calling scheduleGlobalPromptApply directly, waited past both debounce windows, zero prompt/expand or settings-card requests in the network log; full tour sequence still completes with zero thrown errors. Co-Authored-By: Claude Sonnet 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.