## Why

Creating a guided server already captures the user's installation intent, directory, and game configuration. Requiring a second Deploy click after the dedicated Run registers exposes an internal bootstrap stage and leaves a healthy Run idle.

## What Changes

- Treat `guided-install` as authorization to deploy automatically once the server-scoped Run successfully registers.
- Keep existing-server and custom-command definitions non-destructive: registration never silently reinstalls them.
- Remove Deploy/Retry deploy from the normal server-detail flow; registration and durable job state become the source of deployment progress.

## Impact

- `platform/` schedules the initial fenced install from successful dedicated Run registration.
- `platform_web/` presents registration as an automatic deployment wait state rather than an operator action.
- The independent Run contract remains channelized; its SCUM executor work is validated separately and is not exposed to the browser.