fix: v2 - support value and default in input nodes

[maxy-shpfy]

Description

Introduces a distinct value field for pipeline inputs that sits above defaultValue in the resolution hierarchy. When a user sets a value in the Input Details panel, it now calls setInputValue, which sets both value and defaultValue on the input simultaneously. The displayed label has been renamed from "Default Value" to "Value", and the resolved display uses value ?? defaultValue so that an explicitly set value takes precedence. A "Use as default" indicator has also been added to the input label area.

Screenshots (if applicable)

Screen Recording 2026-07-29 at 12.40.03 PM.mov (uploaded via Graphite)

Test Instructions

1. Open a pipeline in the editor and select an input node.
2. In the Input Details panel, confirm the field is now labelled "Value" with a "Use as default" indicator.
3. Enter a value and confirm it is reflected on the node card, taking precedence over any existing default value.
4. Confirm undo/redo correctly reverts the value change.
5. Confirm that pipelines with existing default values continue to display correctly when no explicit value is set.

Additional Comments

[maxy-shpfy]

• refactor: remove setinputdefaultvalue as obsolete from actions #2591
• chore: v2 - sync behavior to validation fix resolution #2590
• fix: v2 - support value and default in input nodes #2589 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

🎩 Preview

A preview build has been created at: 07-29-fix_v2_-_support_value_and_default_in_input_nodes/4625235

[maxy-shpfy]

Merge activity

• Jul 30, 5:10 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 30, 5:16 PM UTC: @maxy-shpfy merged this pull request with Graphite.