agents-relay 1.0.121 → 1.0.123
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -6,17 +6,6 @@ Before `job create`, the orchestrator converts the relevant discussion into a st
|
|
|
6
6
|
|
|
7
7
|
This contract defines orchestrator-owned exception workflows that sit above normal Agents Relay task/job execution.
|
|
8
8
|
|
|
9
|
-
## Hotfix workflow
|
|
10
|
-
|
|
11
|
-
A hotfix is a fast path for a live blocking problem:
|
|
12
|
-
|
|
13
|
-
1. The current active orchestrator thread patches the live/runtime target directly.
|
|
14
|
-
2. It immediately reproduces the failure and verifies the fix against the live runtime.
|
|
15
|
-
3. Once verified, the same logical fix is applied to canonical `main`, tested, committed, and pushed.
|
|
16
|
-
4. The orchestrator completes the normal post-merge/publish reconciliation and cleanup.
|
|
17
|
-
|
|
18
|
-
Do not create a blocking job/PR before fixing the live runtime. Keep the hotfix minimal and do not leave the live patch as the only durable implementation.
|
|
19
|
-
|
|
20
9
|
## P0 / self job workflow
|
|
21
10
|
|
|
22
11
|
A **P0 job** (alias: **self job**) is executed directly by the current active orchestrator thread:
|
|
@@ -73,7 +73,7 @@ Every worker task has one of three story sizes:
|
|
|
73
73
|
|
|
74
74
|
Relay derives the overall execution timeout from `storySize`. If `routing.reasoning` is `high`, Relay doubles the overall execution timeout. Other reasoning levels do not change it.
|
|
75
75
|
|
|
76
|
-
Raw `timeoutMs` is a compatibility/debug
|
|
76
|
+
Raw `timeoutMs` is a compatibility/debug override, not the normal task-production interface.
|
|
77
77
|
|
|
78
78
|
## Task readiness states
|
|
79
79
|
|