Make generated run lifecycle autonomous
This commit is contained in:
@@ -4,10 +4,10 @@ Manual generated Run execution exposed a stale lifecycle design: platform persis
|
||||
|
||||
## What Changes
|
||||
|
||||
- Add runtime-state reconciliation for generated Run registration so a Run endpoint can report the actual managed process state for its server after reconnect/startup.
|
||||
- Remove registration-time runtime-state reconciliation jobs for generated Run; Run reports the actual managed process state from its own lifecycle authority instead of waiting for Platform probes.
|
||||
- Project `process.status` results into server lifecycle state using Run-reported `processState` values such as `running`, `stopped`, `not-started`, and `exited`.
|
||||
- Prevent stale platform `running` from surviving when the active Run reports no managed process for that server.
|
||||
- Keep lifecycle command authorization and job dispatch platform-owned; only observed runtime/process state becomes Run-authoritative.
|
||||
- Keep Platform authorization/audit for explicit operator requests while making observed runtime/process state and generated Run bootstrap Run-authoritative.
|
||||
|
||||
## Capabilities
|
||||
|
||||
|
||||
Reference in New Issue
Block a user