Development desktop builds currently cannot use verified remote releases even when direct package updates are explicitly enabled, because eligibility also requires release-build metadata.
Acceptance criteria:
- A versioned development desktop build with direct package updates explicitly enabled can check its selected available release channel.
- A strictly newer matching remote package can use the existing verified installer flow.
- Development and release packages with direct package updates disabled remain under their distribution workflow.
- Unversioned development runs and unsupported targets remain excluded.
- Existing channel, URL, platform, format, architecture, size, and checksum validation remains enforced.
Development desktop builds currently cannot use verified remote releases even when direct package updates are explicitly enabled, because eligibility also requires release-build metadata.
Acceptance criteria: