@bridge_gpt/mcp-server 0.2.51 → 0.2.53

package/build/executor/service-unit.js

@@ -255,6 +255,17 @@ export function buildExecutorServiceArguments(input) {
     for (const repo of input.repos)
         args.push("--repo", repo);
     args.push("--executor-id", input.executorId);
+    // BAPI-1026 (R54): forward the claim scope. Repeated `--epic-run-id <id>`
+    // pairs mirror how the operator supplied them, or the single `--repo-wide`
+    // opt-out. Appended last so the pre-existing prefix/repo/executor-id ordering
+    // — which several artifact tests pin positionally — is unchanged.
+    if (input.epicRunIds !== undefined) {
+        for (const runId of input.epicRunIds)
+            args.push("--epic-run-id", runId);
+    }
+    else if (input.repoWide === true) {
+        args.push("--repo-wide");
+    }
     return args;
 }
 // ---------------------------------------------------------------------------
@@ -845,6 +856,10 @@ export async function runExecutorInstallServiceCli(argv, overrides) {
         baseUrl,
         homeDir: deps.homeDir,
         envPath,
+        // Forwarded from the already-validated parse, so the generated unit starts
+        // with the same claim scope the operator typed (BAPI-1026).
+        ...(options.epicRunIds !== undefined ? { epicRunIds: options.epicRunIds } : {}),
+        ...(options.repoWide === true ? { repoWide: true } : {}),
     };
     // Windows has no generated user-service format here: print the fully resolved,
     // secret-free command line plus manual Task Scheduler guidance and stop. No

package/build/executor/terminal-mutation.js

@@ -1,3 +1,17 @@
+/**
+ * Terminal mutation (complete/fail) retry semantics (BAPI-534, TDD §10).
+ *
+ *  - `updated`            → terminal success.
+ *  - `stale_claim`        → definitive loss of ownership; stop touching worktree.
+ *  - `retry_later` / net  → retryable at the heartbeat interval WHILE the dead-man
+ *                           window has not elapsed; then abandon.
+ *  - `invalid_job_result` → (complete only) terminal non-success; the server has
+ *                           already failed the job, so DO NOT then call `/fail`.
+ *
+ * Retry diagnostics are bounded and never include raw result envelopes, secrets,
+ * or unbounded stdout/stderr.
+ */
+import { normalizeMutationResult } from "./types.js";
 /**
  * Send a terminal mutation with the fencing-aware retry policy. Skips entirely
  * when ownership was already abandoned.
@@ -7,9 +21,16 @@ export async function sendTerminalMutationWithRetry(params) {
     if (ownership.abandoned)
         return { outcome: "skipped" };
     while (true) {
-        const outcome = await params.send();
+        const mapped = normalizeMutationResult(await params.send());
+        const outcome = mapped.outcome;
         if (outcome === "updated")
             return { outcome: "success" };
+        if (outcome === "auth_fatal") {
+            // Return immediately after exactly one send attempt — no dead-man sleep
+            // or retry. Deliberately does NOT set `ownership.abandoned` (this is not
+            // a lost/stale claim) and never invokes `send()` a second time.
+            return { outcome: "auth_fatal", httpStatus: mapped.authHttpStatus ?? 401 };
+        }
         if (outcome === "stale_claim") {
             ownership.abandoned = true;
             ownership.abandonReason = "stale_claim";

package/build/executor/types.js

@@ -1,3 +1,89 @@
+/**
+ * Server-authoritative executor job types (T2 `ExecutorJobType` literal,
+ * mirrors `EXECUTOR_JOB_TYPE_VALUES` in `api/models/executor_job.py`).
+ *
+ * BAPI-997 (T4): the runtime array is the single source, and `ExecutorJobType`
+ * is DERIVED from it via `(typeof VALUES)[number]` rather than declared
+ * independently — adding or removing a value here changes the emitted
+ * JavaScript array (visible to a Node contract driver) and the compile-time
+ * union in one edit, so the two can never drift apart.
+ */
+export const EXECUTOR_JOB_TYPE_VALUES = [
+    "implement",
+    "resume",
+    "spec_review",
+    "remediate",
+    "rebase",
+    "ci_fix",
+    "merge",
+    "smoke",
+];
+/**
+ * Server-authoritative completion classification (T2 `ExecutorClassification`,
+ * mirrors `EXECUTOR_CLASSIFICATION_VALUES` in `api/models/executor_job.py`).
+ * The local process owner produces the first four; `no_progress`/`lease_expired`
+ * are reserved for server/other paths.
+ *
+ * BAPI-997 (T4): derived from the runtime array, same rationale as
+ * {@link EXECUTOR_JOB_TYPE_VALUES} above.
+ */
+export const EXECUTOR_CLASSIFICATION_VALUES = [
+    "clean_exit",
+    "timeout",
+    "killed",
+    "crashed",
+    "no_progress",
+    "lease_expired",
+];
+/**
+ * Outcome of a heartbeat/complete/fail mutation (T2 status mapping):
+ *  - `updated`            2xx `{ ok: true }`
+ *  - `stale_claim`        409 STALE_CLAIM — definitive dead claim (dead-man's switch)
+ *  - `retry_later`        503 RETRY_LATER — transient; keep worker alive, retry
+ *  - `invalid_job_result` 422 INVALID_JOB_RESULT on /complete — job failed server-side
+ *  - `auth_fatal`         401/403 — BAPI-1021 (AC-5): a Bridge auth/access failure.
+ *    Distinct from `fatal_http_error` because it must bypass the dead-man retry
+ *    loop and halt the executor immediately rather than waiting out the deadman
+ *    window on a credential that will never become valid again.
+ *  - `fatal_http_error`   parse/other non-retryable, NON-AUTH failure. Reserved
+ *    for exactly that now that `auth_fatal` exists — 401/403 map to `auth_fatal`
+ *    before this fallback is ever reached.
+ *
+ * BAPI-997 (T4): derived from the runtime array, same rationale as
+ * {@link EXECUTOR_JOB_TYPE_VALUES} above.
+ */
+export const EXECUTOR_MUTATION_OUTCOME_VALUES = [
+    "updated",
+    "stale_claim",
+    "retry_later",
+    "invalid_job_result",
+    "fatal_http_error",
+    "auth_fatal",
+];
+/** Normalize either mutation response form into the structured shape. */
+export function normalizeMutationResult(response) {
+    return typeof response === "string" ? { outcome: response } : response;
+}
+/**
+ * Server-minted reconciler/dispatcher liveness, carried on a claim response
+ * header (BAPI-871).
+ *
+ * SERVER-AUTHORED, and that is the whole contract. The backend derives this from
+ * the durable `process_heartbeats` row; the executor only reads it. Nothing here
+ * may be inferred from HTTP 204, an empty queue, elapsed polling time, a response
+ * body, or a local scheduler setting — those are exactly the proxies that made
+ * "nothing to do" ambiguous in the first place.
+ *
+ * `unknown` means the verdict is UNEVALUABLE — the header was absent (an older
+ * backend), unrecognized, or the server could not read its own durable source.
+ * It is not a claim that the dispatcher is absent.
+ *
+ * BAPI-997 (T4): derived from the runtime array, same rationale as
+ * {@link EXECUTOR_JOB_TYPE_VALUES} above. `http-client.ts`'s
+ * `parseReconcilerLivenessHeader` admits values from this projection rather
+ * than maintaining an independent literal set.
+ */
+export const RECONCILER_LIVENESS_VALUES = ["fresh", "stale", "never_seen", "unknown"];
 /** Normalize either heartbeat response form into the structured shape. */
 export function normalizeHeartbeatResult(response) {
     return typeof response === "string" ? { outcome: response } : response;

package/build/executor/worker-command.js

@@ -89,17 +89,33 @@ export function resolveExecutorPrompt(job) {
         error: `no usable prompt for job_type '${job.job_type}' (no payload.prompt and no ticket_key)`,
     };
 }
-/** The ratified default — the pre-BAPI-725 behavior for every job. */
-export const DEFAULT_WORKER_PERMISSION_POSTURE = "skip_permissions";
+/**
+ * The ratified default (BAPI-1020).
+ *
+ * `auto` runs the worker under Claude's own permission classifier: a flagged call
+ * is DENIED WITH A REASON and the worker continues. It replaces `skip_permissions`,
+ * which bypassed that classifier entirely — the posture Architecture Miss 28 ran
+ * under. `skip_permissions` is still accepted, but only as an explicit revert an
+ * operator asks for by name; an unset key no longer hands out full bypass.
+ *
+ * `auto` shares its spelling with the Claude CLI's own mode name. That coincidence
+ * does NOT make this vocabulary a passthrough for argv: the mapping still lives in
+ * the adapter, and `resolveWorkerPermissionPosture` still rejects every CLI-shaped
+ * spelling it rejected before (`acceptEdits`, `dangerously-skip-permissions`).
+ */
+export const DEFAULT_WORKER_PERMISSION_POSTURE = "auto";
 const WORKER_PERMISSION_POSTURES = [
+    "auto",
     "skip_permissions",
     "accept_edits",
 ];
 /**
  * Resolve the permission posture at the payload boundary.
  *
- * - ABSENT (`undefined`/`null`) → the ratified `skip_permissions` default, so
- *   legacy jobs enqueued before BAPI-725 keep working unchanged.
+ * - ABSENT (`undefined`/`null`) → the ratified `auto` default (BAPI-1020). A job
+ *   enqueued by an older server, or by one whose policy omits the key, therefore
+ *   spawns under the GUARDED posture rather than under bypass — the direction a
+ *   missing value should fail in.
  * - a supported value → returned as-is.
  * - present but unsupported → THROWS a named contract error before argv
  *   construction, so the job fails loudly instead of spawning under a posture
@@ -121,7 +137,7 @@ export function resolveWorkerPermissionPosture(payload) {
         return raw;
     }
     throw new ExecutorNamedError("ContractError.PermissionPosture", "job payload worker_permission_posture is present but is not a supported posture " +
-        "(expected 'skip_permissions' or 'accept_edits').");
+        "(expected 'auto', 'skip_permissions', or 'accept_edits').");
 }
 // Argv construction, model-alias resolution, and the worker executable name all
 // live in the resolved executor adapter now (BAPI-781). `job-runner.ts` requests