agents-relay 2.0.170 → 2.0.171
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
|
@@ -2,6 +2,16 @@
|
|
|
2
2
|
|
|
3
3
|
**Scope:** Relay-specific event meaning and validation. This does **not** define Events Bus transport. The bus only handles generic event identity, type, timestamp, routing as needed, and opaque `data`. No Events Bus change is required when Relay adds agent roles or payload fields.
|
|
4
4
|
|
|
5
|
+
## Execution event source
|
|
6
|
+
|
|
7
|
+
Every Task lifecycle event must identify the exact current Relay execution with:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
source.id = job/<job-id>/task/<task-id>/execution/<execution-id>
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
Relay supplies this complete identity in the managed Task context. Agents must copy it unchanged; they must not infer a Job/Task ID, generate an execution ID, or reuse an identity from a previous attempt. The Neo `events.publish` tool accepts this value as its string `source` argument; the Events Bus event envelope represents it as `source.id`. Transport acceptance alone does not establish that Relay accepted the event for the current execution.
|
|
14
|
+
|
|
5
15
|
## Producer contract
|
|
6
16
|
|
|
7
17
|
Every Implementation, Reviewer, and Troubleshooter execution publishes `task.started`, optional `task.progress`, then **exactly one** agent terminal event:
|