fix: separate run builders from generated workers
This commit is contained in:
+11
@@ -0,0 +1,11 @@
|
||||
## MODIFIED Requirements
|
||||
|
||||
### Requirement: Run distribution generation remains asynchronous and server-scoped
|
||||
|
||||
The platform SHALL create a bounded `distribution.build` job on the instance deployment target and return a `building` distribution with the real job ID. The generated Run package SHALL contain a server-scoped endpoint identity and component key; a legacy shared builder endpoint MUST be promoted to the deployment target before the job is queued.
|
||||
|
||||
#### Scenario: Generate from a legacy endpoint binding
|
||||
|
||||
- **GIVEN** an authorized server owner selects a legacy server whose only endpoint is an online build-capable worker
|
||||
- **WHEN** the owner requests a target-matched Run distribution
|
||||
- **THEN** Platform queues the build on that worker and assigns the generated package its deterministic dedicated endpoint identity
|
||||
Reference in New Issue
Block a user