Separate component releases and safely reuse unchanged Runner droplets #167

Separate Configurator component releases so an unchanged Runner does not need restaging for UI/API-only fixes.

Deferred follow-up; outside the current pipeline optimization scope. The current work retains one immutable source-bound release and optimizes packaging and independent validation/staging only.

Proposed scope:

• Immutable per-component digests for Web/API, Runner and migration payloads, with explicit compatibility/provenance contracts.
• Reuse an unchanged verified Runner droplet; preserve source-bound approvals, existing order/template bindings and native engine pins.
• Run only applicable migrations while retaining checksum/advisory-lock verification and readiness checks.
• GitHub UI release selection and a clear summary of rebuilt/reused components, safe rollback and failure handling.
• Keep qualified Assistant release gates and Dev-only skip semantics intact.

Acceptance: a UI-only fix reuses the verified compatible Runner without another upload/staging cycle; incompatible combinations fail closed. Test full releases, component reuse, promotion, rollback and stale/tampered artifacts. Measure lifecycle improvement against the current release baseline (12:13 build, 38:33 deploy in run 40334302222).