## ADDED Requirements

### Requirement: Authorized deployment input reveal
The Platform SHALL provide an explicit authenticated read operation that lets an authorized server manager retrieve the saved server root, working directory, install command, start command, stop command, and status command for one server deployment. The operation MUST NOT return runtime bindings.

#### Scenario: Owner reveals a custom deployment
- **WHEN** an authorized server manager explicitly requests deployment input reveal for a stopped server with saved custom commands
- **THEN** the Platform returns the saved deployment paths and commands for that server only

#### Scenario: Unauthorized user requests reveal
- **WHEN** a user without access to the server requests deployment input reveal
- **THEN** the Platform rejects the request and returns no deployment input

### Requirement: Default deployment views remain redacted
The existing server deployment read endpoint and all list, detail, job, audit, log, and plugin-facing projections SHALL remain redacted after reveal support is added.

#### Scenario: Normal deployment read after reveal support
- **WHEN** an authorized user reads a configured deployment through the existing deployment endpoint
- **THEN** the response indicates configured state without returning paths or commands

### Requirement: Editor reveal is deliberate and bounded
The deployment editor SHALL start with protected inputs redacted and SHALL fetch saved path and command values only after the operator selects its explicit reveal control. Closing the editor MUST discard revealed values from its local form state.

#### Scenario: Operator opens editor without revealing
- **WHEN** an operator opens an existing deployment editor
- **THEN** protected input fields remain blank and show their configured state

#### Scenario: Operator explicitly reveals inputs
- **WHEN** an operator selects the reveal control in the open deployment editor
- **THEN** the editor displays the returned saved paths and commands for inspection and editing

### Requirement: Dispatch diagnostics distinguish Platform dispatch from Run execution
The deployment view SHALL expose safe diagnostic metadata for the most recent lifecycle job: job identifier, job state, deployed revision, and whether the leased input included a deployment definition. It MUST NOT expose the leased values.

#### Scenario: Platform queued a deployment definition
- **WHEN** Platform creates a lifecycle job from a saved deployment definition
- **THEN** the deployment diagnostic identifies the job revision and that the job included a deployment definition without returning its paths or commands