agents-relay 2.0.119 → 2.0.121

package/dist/adapters.js

@@ -322,7 +322,7 @@ export class ChatGptAdapter {
                 throw new Error('browser-worker execution aborted');
             const policy = chatGptTabClosePolicy(task.chatgptTabClosePolicy, this.tabClosePolicy);
             const submit = () => (this.runner ?? browserWorkerRunner())(definition, {
-                prompt: task.chatgptThreadDelivery?.threadSource === 'implementation' && task.chatgptThreadDelivery.repository && task.chatgptThreadDelivery.executionId
+                prompt: task.chatgptThreadDelivery?.repository && task.chatgptThreadDelivery.executionId
                     ? taskReferencePrompt(task.chatgptThreadDelivery.repository, task.chatgptThreadDelivery.jobId, task.id, task.chatgptThreadDelivery.executionId, task.input) : task.input,
                 ...(task.attachments?.length ? { files: task.attachments } : {}),
                 ...(task.chatgptThreadDelivery ? { thread: task.chatgptThreadDelivery } : {}),

package/dist/managed-worker-input.js

@@ -63,6 +63,7 @@ publish through the federated MCP tool events__publish; do not open NATS directl
 For a direct non-sandbox local worker, use NEO_EVENTS_EMIT when the caller provides it.
 As your FIRST execution action, before reading files, editing code, running commands, or doing other work,
 you MUST publish exactly one canonical task.started event for this exact Job/Task.
+Immediately after task.started, BEFORE reading task context or doing any implementation/review/recovery work, read the full authoritative Relay event contract at absolute path /Users/chengli/Workspace/agents-relay/skills/agents-relay/contracts/event-contract.md. If it cannot be read, publish task.failed with the blocker and stop. Do not rely only on this prompt summary or a relative path.
 
 ${task.adapter === 'chatgpt' ? `Because ChatGPT execution continues asynchronously after the submit process exits, you MUST keep reporting liveness while the task is active. Publish meaningful progress/milestone events when there is real progress to report. If no meaningful milestone has been published for 30 seconds during active work, publish a non-terminal task.heartbeat event with status running, visibility orchestrator, this exact source.id, and a concise description of the current operation. Continue heartbeats after each further 30 seconds of active silence until a terminal task event is published. Do not invent percentage progress.` : `You MAY publish progress events while working. For long silent active work, follow the events-bus heartbeat policy.`}
 Before returning or allowing the worker process to exit, you MUST publish exactly one canonical terminal event:

package/dist/task-context.js

@@ -11,11 +11,22 @@ export function taskExecutionContext(job, taskId, executionId) {
             projectPath: job.projectPath, state: job.state }, task, comments: task.comments ?? [], dependencies: task.dependencies.map(id => job.tasks.find(item => item.id === id) ?? { id, missing: true }),
         plan: job.plans?.find(plan => plan.id === task.planningDecisionId) ?? null };
 }
+/** Browser new-turn envelope: the local Contract and durable Task Context are authoritative. */
 export function taskReferencePrompt(repository, jobId, taskId, executionId, managedInput) {
-    const marker = '[Execution event contract — mandatory]';
-    const index = managedInput?.indexOf(marker) ?? -1;
-    if (managedInput !== undefined && index < 0)
+    if (managedInput !== undefined && !managedInput.includes('[Execution event contract — mandatory]'))
         throw new Error(`Missing managed execution event contract for ${jobId}/${taskId}/${executionId}`);
-    const eventContract = index >= 0 ? `\n\n${managedInput.slice(index)}` : '';
-    return `[Agents Relay managed task]\nRepository: ${repository}\nJob ID: ${jobId}\nTask ID: ${taskId}\nExecution ID: ${executionId}\n\nRetrieve the authoritative task contract using the connected NeoY shell/Agents Relay CLI:\n  agents-relay task context --repo ${repository} --id ${jobId} --task-id ${taskId} --execution-id ${executionId}\nRead the returned Task input, dependencies, Plan, project context, and output requirements before execution. Check that the execution ID matches. If the CLI or context is unavailable, report blocked; never guess or execute from this envelope. Continue in this thread; Relay owns completion and review. Do not create another Job.${eventContract}`;
+    const source = `job/${jobId}/task/${taskId}/execution/${executionId}`;
+    return `[Agents Relay managed task]
+Repository: ${repository}
+Job ID: ${jobId}
+Task ID: ${taskId}
+Execution ID: ${executionId}
+Exact event source.id: ${source}
+
+FIRST publish exactly one task.started through the canonical Neo events-bus with this exact source.id.
+THEN read the entire authoritative event contract from /Users/chengli/Workspace/agents-relay/skills/agents-relay/contracts/event-contract.md before any task work. If unavailable publish task.failed and stop.
+THEN retrieve the authoritative Task Context:
+  agents-relay task context --repo ${repository} --id ${jobId} --task-id ${taskId} --execution-id ${executionId}
+Verify the execution ID. Read Task input, dependencies, Plan, project context, and output requirements from that response. Never guess or create a new Job. Continue in this thread; Relay owns completion and review.
+Follow the file's lifecycle contract, including progress/heartbeat and exactly one task.completed or task.failed before exiting. If context is unavailable publish task.failed with the blocker.`;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-relay",
-  "version": "2.0.119",
+  "version": "2.0.121",
   "description": "Durable async agent jobs coordinated through GitHub pull requests",
   "repository": {
     "type": "git",