Choose the Windows installer destination contract

[eimexdev]

Part of OpenBeat v0.1.0 public launch map.

Question

For the v0.1.0 launch, should the Windows installer support a user-selected Resolve Fusion destination, or intentionally support only the standard %APPDATA% location?

Resolution should record

• The supported install-path contract.
• The user experience and documentation implied by that contract.
• The minimum tests needed to trust it.
• Whether any nonstandard-path behavior is explicitly deferred.

This is a HITL product decision: use $grilling and $domain-modeling.

Handoff

Implement the selected Windows installer destination contract implements the resolved decision.

[eimexdev]

Resolution

For the v0.1.0 launch, the Windows installer supports both:

• The standard per-user Resolve Fusion support root at %APPDATA%\Blackmagic Design\DaVinci Resolve\Support\Fusion, selected by default.
• A user-selected Resolve Fusion support root through an editable path field and folder chooser.

User experience and documentation

• Call the destination the Resolve Fusion support folder.
• Show that OpenBeat creates Scripts and Modules beneath the selected root.
• Keep the selected path visible on the confirmation screen.
• Reject an empty destination and allow a new destination folder to be created.
• Document the standard default and custom-path workflow without implying that the installer automatically discovers relocated folders.

Minimum tests

• Default resolution from %APPDATA%, including the fallback when the variable is absent.
• Chooser cancellation and empty-path rejection.
• Custom roots containing spaces and Unicode.
• Preservation of the selected root through confirmation and installation.
• Placement of scripts, modules, bundled runtime, and generated Lua configuration beneath the selected root.
• Exact Windows artifact smoke testing in DaVinci Resolve.

Explicit deferral

Automatic discovery of relocated Resolve/Fusion folders is deferred. Resolve documents conventional per-user and all-user locations but exposes no trustworthy installer-facing source of truth for an arbitrary relocated support root. The chooser provides a reliable recovery path without presenting filesystem guesses as authoritative.