Inputs and configuration
Keep Pine source defaults separate from app data, execution, and runtime settings.
Native source belongs in the app's pinescript field.
Source-level inputs
The example declares input.int(3, "Fast length", minval=1) and a separate slow length. In the current app integration, edit those source defaults when changing the example's lengths, then save a revision and run it again.
The lower-level Pine runner has an input-options API, but the STX native adapter does not expose a complete app input-override settings workflow. Do not assume that an arbitrary app property or chart dialog overrides an input.* declaration.
Session settings
Instrument, data interval, historical bounds, session timezone, and warmup belong to the surrounding app/session configuration. Changing a source input does not change which instrument the engine subscribes to.
Order sizing and execution also depend on who owns the request. An indicator with SJS execution uses the SJS request quantity; the native strategy bridge has its own quantity fallback behavior.
Update the runtime deliberately
The native runner keeps incremental state. Save source changes and use a fresh historical run when comparing different source or initialization settings. Do not assume that editing the visible source reconstructs an already running instance immediately.
Keep the original source and its settings with the baseline run. A chart whose title stayed the same can still represent changed input defaults.
Editor support
The editor provides Pine syntax highlighting. That is not a full Pine language server or a guarantee that the runtime accepts the script. Use the execution diagnostics and supported-feature guide to validate actual behavior.
Continue with plots and outputs.