runs: reconcile uncertain browser launches with a persistent intent key
This commit is contained in:
@@ -42,6 +42,17 @@ can use the host user's permissions, credentials, and network. Use a dedicated
|
||||
unprivileged account, VM, or container with an explicit workspace mount for
|
||||
untrusted definitions. Do not advertise prompt instructions as sandboxing.
|
||||
|
||||
## Lost run-start replies
|
||||
|
||||
The web Run dialog saves one immutable launch payload and request key in tab
|
||||
storage before sending it. An uncertain launch is not automatically replayed.
|
||||
`Check / retry` first uses the read-only `get_run` command with `request_key`;
|
||||
if admitted, it opens that exact run, even if it already finished. Otherwise it
|
||||
resends the original intent with the same key. Changing the task requires first
|
||||
resolving admission; an explicit refusal is editable only after that lookup
|
||||
confirms no run exists. A page reload and reopening the same pipeline/version
|
||||
recovers the pending intent on the same endpoint.
|
||||
|
||||
## Delivery discipline
|
||||
|
||||
Checks and browser probes use scratch databases and loopback ports. Installing
|
||||
|
||||
Reference in New Issue
Block a user