feat(ui): add Use Cache and Save To Gallery to the form builder, make them connectable

[Pfannkuchensack]

Summary

Feature (frontend + backend). Adds the two node footer toggles — Use Cache and Save To Gallery — to the workflow form builder, and makes their underlying fields connectable.

Why

Every other node control can be placed in a workflow's form. These two could not, because they are node attributes: their value lives on node.data.useCache / node.data.isIntermediate, not in node.data.inputs, so the existing node-field form element cannot address them.

How

1. A node-setting form element (features/nodes/types/workflow.ts)

Parallel to node-field, holding { nodeId, setting, label }. Added to the form the same way node fields are: a +/− button revealed on hover in the node footer, or by dragging the setting's label into the form. The label is editable on double-click — two nodes' "Use Cache" entries would otherwise be indistinguishable in a form.

Rendered as a Switch to match how BooleanField inputs render. Settings that no longer apply to their node are hidden in view mode and flagged in edit mode; use_cache stays admin-only, mirroring the node footer.

2. The fields become connection targets

BaseInvocation already declares both as ordinary pydantic fields, so the backend change is small: both now declare Input.Any, and is_intermediate drops its ui_type=_IsIntermediate, which had made it parse as its own field type that no BooleanField output could connect to.

The interesting part is that this needs no workflow migration:

	before	after
In invocation template	filtered out	parsed in (needed for handle + connection validation)
In node's input list	—	still filtered out (rendered in the footer instead)
Field instance in node.data.inputs	none	still none — buildInvocationNode skips them, and updateNode derives its allowed keys from there
Value storage	node.data.useCache	unchanged
buildNodesGraph	writes the literal	unchanged — the edge is emitted from state.edges and the backend overwrites the literal on resolution

Edge values are applied in GraphExecutionState.next() before the invocation is handed to the invoker, so a connected use_cache is resolved by the time the cache is consulted, and a connected is_intermediate by the time the image is saved.

3. Guards against edges that would do nothing

The footer hosts the handles, and useWithFooter only renders it for executable nodes with a gallery output. Connections to node attribute fields on any other node are rejected — there would be no handle to attach to, and buildNodesGraph drops batch and generator nodes entirely.

When an edge drives a setting, the node's checkbox is removed (matching how a connected input field renders) and the form's toggle is disabled, since the local value is no longer what the node runs with.

4. Layout

The footer became one row per setting so each connection handle lines up with its own label, following InputFieldWrapper. This makes affected nodes ~16px taller. UseCacheCheckbox / SaveToGalleryCheckbox are consolidated into one NodeSettingFooterControl; useIsBatchNode and useNodeHasGalleryOutput were absorbed into shared predicates in types/invocation.ts.

Notes for reviewers

• use_cache is only reachable on nodes with a gallery output. That is pre-existing (useWithFooter = isExecutableNode && hasGalleryOutput) and this PR deliberately does not widen it — the connection guard just matches reality. Happy to change it if that gate is considered a bug.
• The is_intermediate inversion remains. An edge carries is_intermediate, the UI says "Save To Gallery". Connecting a boolean node means thinking inverted. Fixing that properly means either a dedicated renderer or renaming the backend field to save_to_gallery; both felt out of scope here.
• The Canvas workflow integration preview skips node settings — it renders a saved workflow, not the editor state the toggle would write to.

Related Issues / Discussions

QA Instructions

Form builder

1. Workflow editor → a node with a gallery output (e.g. Latents to Image). Hover the footer → + buttons appear next to both settings.
2. Click + on Use Cache → it appears in the form; the button becomes −.
3. Toggle it in the form → the node's checkbox follows, and vice versa.
4. Double-click the label in the form builder → rename it; the custom label persists after reload.
5. Drag the setting by its label into the form → same result as +.
6. Delete the node → its settings disappear from the form.

Connections
7. Add a Boolean Primitive, drag from its Value output onto the Use Cache handle on the footer's left edge → the edge connects, and the checkbox disappears (the edge now supplies the value).
8. If the setting is also in the form, its toggle is now disabled.
9. Try connecting to a node with no gallery output (e.g. Add Integers) → no handle is offered.
10. Invoke → the connected value is what the node runs with.

Regression
11. Confirm use_cache / is_intermediate do not appear in any node's input list.
12. Load a workflow saved before this PR → unchanged; no migration warnings.

Merge Plan

Nothing special.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration — n/a, additive only (see Merge Plan)
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[JPPhoto]

Merge blockers:

• invokeai/app/invocations/baseinvocation.py:267: Changes inherited is_intermediate and use_cache from non-connectable node attributes to Input.Any targets, changing every invocation schema. No invocation versions change. Effect: version-based workflow migration cannot detect the new input contract. Likelihood: all built-in invocations. Recovery: bump affected invocation versions and add compatibility tests. Test: compare changed OpenAPI input metadata against invocation decorator versions; current diff has no decorator version changes.

Other findings/issues:

• invokeai/frontend/web/src/features/nodes/components/sidePanel/builder/NodeSettingElementEditMode.tsx:59: Edit mode renders an enabled use_cache switch without the admin guard retained in NodeSettingFooterControl. Effect: non-admin multiuser users can change and save the admin-only, process-global cache policy. Likelihood: any shared workflow containing an existing use_cache element. Recovery: admin must reset/remove the setting or clear cache. Test: render as non-admin, click the switch, assert no nodeUseCacheChanged dispatch.

• invokeai/frontend/web/src/features/controlLayers/components/CanvasWorkflowIntegration/WorkflowFormPreview.tsx:245: Every node-setting is silently returned as null, while Canvas integration still accepts forms containing these elements. Effect: saved forms show no Use Cache or Save To Gallery control; execution silently uses saved node values. Likelihood: any Canvas-integrated workflow with an ImageField plus node setting. Recovery: edit the workflow node directly or remove the form element. Test: select such a workflow and assert the preview renders the setting control; current branch renders nothing.

Suggestions:

• Bump every affected invocation version and cover old/new workflow loading.

• Instead of checking admin status only in the footer, enforce it in shared node-setting edit, view, and add paths.

• Instead of silently dropping settings in Canvas preview, wire their values into Canvas execution or reject incompatible forms during selection.