agents-relay 2.0.96 → 2.0.97

package/dist/cli-help.js

@@ -58,7 +58,7 @@ Required: --repo OWNER/REPO --pr NUMBER --id JOB_ID.
 Optional: --thread-id THREAD_ID persists a reviewer override; omitted uses Job reviewer/creator thread or legacy route. Rejects pending reviews and wakes managed reconciliation.`,
     'job create': `Create a SQLite-authoritative Job (objective-only).
 
-Required: --repo OWNER/REPO and a standalone Job objective. Job ID defaults to an auto-incrementing repository-scoped number; --id is optional for compatibility. Existing PR adoption is an explicit separate command: job adopt.
+Required: --repo OWNER/REPO and a standalone Job objective. Job ID defaults to an auto-incrementing store-global number; --id is optional for compatibility. Existing PR adoption is an explicit separate command: job adopt.
 Common: --id JOB_ID (optional), --title TEXT, --objective-file PATH|- (preferred), --objective MARKDOWN (short/simple only), --project-path RELATIVE_PATH, --priority P0|P1|P2|P3, --mode fixed|autonomous, --initial-plan, --no-review, --tag JSON, --reviewer-thread-id ID, --creator-thread-id ID, --implementation-thread-id ID. --objective and --objective-file are mutually exclusive.
 Job creation always enables auto-merge. By default it is create-only; --initial-plan validates the first real Planner round before atomically creating the durable Job and Plan, then publishes the normal wake so Relay can continue without a second orchestrator command. Re-running create against an already healthy Job is idempotent and does not mutate its metadata.
 

package/dist/job-task-id-sequence.js

@@ -14,14 +14,17 @@ export function isGeneratedEntityId(id, repository, kind) {
         const legacyPrefix = generatedEntityPrefix(repository, kind);
         return id.startsWith(legacyPrefix) && /^[0-9]+$/.test(id.slice(legacyPrefix.length));
     }
+    if (/^[1-9][0-9]*$/.test(id))
+        return true;
     const prefix = generatedEntityPrefix(repository, kind);
     return id.startsWith(prefix) && /^[0-9]+$/.test(id.slice(prefix.length));
 }
-/** Jobs remain repository-scoped. Task IDs are one Relay-global monotonically increasing integer sequence. Allocation is serialized by SQLite. */
+/** Job and Task IDs each use their own store-global sequence. SQLite serializes allocation; legacy identifiers remain readable. */
 export function allocateEntityId(directory, repository, kind, requestKey, occupied = new Set()) {
-    const prefix = kind === 'job' ? generatedEntityPrefix(repository, kind) : '';
-    const scope = kind === 'task' ? '*' : repository;
-    const scopedRequestKey = requestKey && kind === 'task' ? `${repository}:${requestKey}` : requestKey;
+    generatedEntityPrefix(repository, kind); // validate repository even though its name no longer appears in the ID
+    const prefix = '';
+    const scope = '*';
+    const scopedRequestKey = requestKey ? `${repository}:${requestKey}` : undefined;
     if (requestKey !== undefined && (!requestKey || requestKey.length > 512))
         throw new Error('Invalid idempotency key');
     mkdirSync(directory, { recursive: true });
@@ -39,6 +42,7 @@ export function allocateEntityId(directory, repository, kind, requestKey, occupi
                 }
             }
             const old = db.prepare('SELECT value FROM sequences WHERE repository=? AND kind=?').get(scope, kind);
+            // Existing generated numeric IDs across all repositories are reserved by the caller.
             let next = (old?.value ?? 0) + 1;
             while (occupied.has(prefix + next))
                 next++;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-relay",
-  "version": "2.0.96",
+  "version": "2.0.97",
   "description": "Durable async agent jobs coordinated through GitHub pull requests",
   "type": "module",
   "bin": {

package/skills/agents-relay/contracts/orchestrator-workflows.md

@@ -24,6 +24,14 @@ The initial decomposition belongs to that durable Planner round. The orchestrato
 
 ## P0 / self job workflow
 
+For a self Job owned by the current XChat thread, resolve the current thread ID
+before creating the Job. If it cannot be retrieved reliably, ask the user for
+the thread ID before proceeding. Set `creatorThreadId`,
+`implementationThreadId`, and `reviewerThreadId` to that same thread ID at
+creation, using the corresponding `--creator-thread-id`,
+`--implementation-thread-id`, and `--reviewer-thread-id` options. Do not infer
+the thread ID from an unrelated worker, execution, or previous conversation.
+
 P0/self work is ordinary durable Relay work. The orchestrator may choose normal
 Task requirements, but every newly created work Task is executable by a
 worker/model route selected by Execution Router. Relay has no privileged