@bridge_gpt/mcp-server 0.2.50 → 0.2.52

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