Apply the run configuration on run, and add Run with Parameters…

[ChrisonSimtian]

6/6 of the #2 split. Closes #14. Based on #19 — the last of the stack.

Wires the stored configuration into the two ways a target gets run.

• Inline ▶ stays silent. Saved parameters are appended as arguments, secrets applied as environment variables. One click, configuration simply in effect.
• "Run Target with Parameters…" opens an InputBox prefilled with the target and those arguments, for a one-off tweak — an extra --configuration Debug, a different verbosity — without editing the saved configuration. Secrets still apply but are not editable here: the point of keychain storage is that they never appear in a text field.

The subtle one

runInTerminal disposes and recreates the Fallout terminal when an environment is supplied:

if (hasEnv) {
    terminal?.dispose();
    terminal = vscode.window.createTerminal({ name: 'Fallout', cwd: root, env });
}

A terminal's environment is fixed at creation. Reusing the existing one would silently run with a stale secret after a rotation, and the failure would present as a bad credential rather than a stale terminal — an expensive thing to debug. The no-env path still reuses the terminal, so ordinary runs don't churn it.

Both commands are hidden from the command palette: they act on a tree item, and invoking them without one does nothing.

After this merges

#2 can close, and #1 (populate parameters and secrets from the build's declarations, blocked on Fallout-build/Fallout#499) is the remaining follow-up.

🤖 Generated with Claude Code