@sema-agent/server 3.4.1 → 3.4.2

package/dist/capabilities/select-environment-tool.js

@@ -1,5 +1,5 @@
 /**
- * RFC A2 (docs/design/ENV-SELECT-AND-REGION-SOURCE.md) — the model-facing `SelectEnvironment` tool.
+ * RFC A2 (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md) — the model-facing `SelectEnvironment` tool.
  * A 切片先行;挂载路线 = RFC 判定②(a):deployment 经 `spec.tools` 注入(同 lsp/
  * 自定义工具),core 收编等真用起来再谈。
  *

package/dist/capabilities/skills.js

@@ -20,7 +20,7 @@ export function loadSkills(dir) {
     };
     // sort 保证加载顺序稳定(冲突报错的"先到者"也因此确定)。dotfile/dot 目录跳过(.DS_Store/.git 类
     // 环境杂物,不是 skill 内容);isFileLike 兼容 symlink(Dirent.isFile() 对 symlink 恒 false,而旧扁平
-    // 实现 readFileSync 是跟链接的——不兼容会让 `skills/foo.md -> 共享文件` 无声消失)。
+    // 实现 readFileSync 是跟链接的——不兼容会让 skills 目录下 `foo.md -> 共享文件` 这种软链无声消失)。
     const isFileLike = (entry, p) => entry.isFile() || (entry.isSymbolicLink() && statSync(p).isFile());
     const isDirLike = (entry, p) => entry.isDirectory() || (entry.isSymbolicLink() && statSync(p).isDirectory());
     for (const entry of entries.slice().sort((a, b) => (a.name < b.name ? -1 : a.name > b.name ? 1 : 0))) {

package/dist/config-center/skills-mcp.d.ts

@@ -4,7 +4,7 @@ import type { Logger } from "../observability/logger.js";
 import type { LoadedSkill } from "../capabilities/skills.js";
 import type { CenterMcpServer, CenterSkillManifest } from "./types.js";
 /**
- * Merge center skills OVER the image baseline (design/41-sibling B1; `docs/MCP-SKILLS.md`). Load order =
+ * Merge center skills OVER the image baseline (design/41-sibling B1; `sema-registry docs/MCP-SKILLS.md`). Load order =
  * `loadSkills(SKILLS_DIR)` baseline → center skills lazily fetched by hash and overlaid BY NAME (center
  * wins on a clash → can override a built-in; guarded center-side by publisher RBAC + the publish gate).
  * `enabled:false` is skipped. Content is verified + cached by hash (same hash fetched once). A skill whose

package/dist/config-center/skills-mcp.js

@@ -8,7 +8,7 @@
 import { skillContentHash } from "@sema-agent/registry-core";
 import { fetchSkillContent } from "./http-client.js";
 /**
- * Merge center skills OVER the image baseline (design/41-sibling B1; `docs/MCP-SKILLS.md`). Load order =
+ * Merge center skills OVER the image baseline (design/41-sibling B1; `sema-registry docs/MCP-SKILLS.md`). Load order =
  * `loadSkills(SKILLS_DIR)` baseline → center skills lazily fetched by hash and overlaid BY NAME (center
  * wins on a clash → can override a built-in; guarded center-side by publisher RBAC + the publish gate).
  * `enabled:false` is skipped. Content is verified + cached by hash (same hash fetched once). A skill whose

package/dist/env-facts.js

@@ -1,5 +1,5 @@
 /**
- * RFC A1 (docs/design/ENV-SELECT-AND-REGION-SOURCE.md) — the sandbox envFacts composer (service 半场).
+ * RFC A1 (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md) — the sandbox envFacts composer (service 半场).
  * Shape ratified REV-1: `TaskSpec.envFacts?: { profile?, capabilities?[], pkgSource?, egress? }`.
  * Core injects it into model context (escape+bound core-side); this module only COMPOSES the facts
  * from deployment-trusted sources (image catalog entry + operator region config + exec-lane posture).

package/dist/http/routes/approvals-assistant.js

@@ -214,6 +214,19 @@ async function handleApprovalsAssistantBody(req, res, url, ctx, miss) {
                 .map((r) => {
                 const s = byGate.get(r.sessionId);
                 const gate = s ? { kind: s.gateKind, severity: s.severity ?? null, spentMicroUsd: s.spentMicroUsd ?? null, deadline: s.deadline ?? null } : null;
+                // 🔴 `needsAttention` = 「此刻有一个**可解的活门**」= `!!gate`,**不是**「run 行停着」([2034]/[2035]
+                // 附带登记的 handler↔§3 文档出入,2026-07-30 裁定 (b):改文档对齐本行,常驻钉
+                // `test/assistant-tasks-needs-attention.test.ts`)。gate 来自 `listByScope`,三个实现都只回
+                // `status='pending'` 的行 ⇒ 分歧态 = run 停在 suspended/needs_review 而 pending checkpoint 已不在。
+                // 该态**可达且周期性发生**:TTL 收割的两半(checkpointStore.reapExpired 只动 checkpoint /
+                // runStore.failSuspendedWithExpiredCheckpoint 才动 run 行)在 boot/reapers.ts 同一 tick 里互不 await。
+                // 三问:① 需要方=triage 视图,它拿这一位只做「哪张卡现在能动 + 排前面」(比较器第一级);
+                // ② 若改按 status 算,分歧态会产出**不可解之卡**——标成待处理、排进前段,而 /decide 必 404、
+                //    /plan_review 与 /resume 同族拒,且与同一行的 `gate:null` 自相矛盾;现写法的代价是这段窗口里
+                //    「只渲染 needsAttention 段」的客户端看不到它;
+                // ③ 补偿=(a) 行**不消失**——它仍在本列表里带真实 `status`,「所有还停着的任务」由 status 回答;
+                //    (b) failSuspendedWithExpiredCheckpoint 三个 run store 全实装、每 tick 无条件跑(不受
+                //    APPROVAL_TIMEOUT_SEC 开关),窗口由 REAP_INTERVAL_SEC 封顶后收敛成 failed。
                 return { taskId: r.taskId, sessionId: r.sessionId, status: r.status, needsAttention: !!gate, gate, createdAt: r.createdAt, updatedAt: r.updatedAt };
             })
                 .sort((a, b) => Number(b.needsAttention) - Number(a.needsAttention) || (b.gate?.severity ?? 0) - (a.gate?.severity ?? 0) || (b.gate?.spentMicroUsd ?? 0) - (a.gate?.spentMicroUsd ?? 0));

package/dist/http/routes/session-sync.d.ts

@@ -1,5 +1,5 @@
 /**
- * design/158 A9 域模块 —— 2c session-sync 面(docs/DESIGN-session-sync.md §15 + §5–§10)。
+ * design/158 A9 域模块 —— 2c session-sync 面(sema-internal server/docs/DESIGN-session-sync.md §15 + §5–§10)。
  *
  * 路由:`/v1/sessions/:id/sync/{manifest,entries,import,plan,blobs,snapshots/:k/blobs/:b,import/:staging/entries}`。
  * 每条都像 fork/delete 一样 owner-gated;无持久 session store 时 501(能力面与路由解析同真值)。

package/dist/http/routes/session-sync.js

@@ -49,7 +49,7 @@ async function handleSessionSyncBody(req, res, url, ctx, miss) {
     const { deps } = ctx;
     const { readJson, readRawBody, safeDecode, sessionOwnerScopeForWrite } = ctx.helpers;
     const { pendingStagings, importLeases, touchImportLease, cleanupStaging } = ctx.local.sessionSync;
-    // ── 2c session-sync (P1d) — the cloud as a SYNC PEER (docs/DESIGN-session-sync.md §15 + §5–§10) ──────────────
+    // ── 2c session-sync (P1d) — the cloud as a SYNC PEER (sema-internal server/docs/DESIGN-session-sync.md §15 + §5–§10) ──────────────
     // The real 2c topology is TWO PROCESSES (the local shell's local backend + this cloud service); these routes let
     // the local peer PULL a session's whole state out of the cloud or PUSH its own in. Both halves are STREAMING
     // implementations that fan out across ALL four session subsystems (entries + fileSnapshot + sessionPolicy +

package/dist/leader/grader-env-factory.d.ts

@@ -1,6 +1,6 @@
 /**
  * The OUT-OF-PROCESS grader plumbing for the leader × `runRepairLoop` integration
- * (`docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.2 + the authoritative §10 layer). Two distinct consumers:
+ * (`sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.2 + the authoritative §10 layer). Two distinct consumers:
  *
  *  - **R1 (single-agent oracle, §10.1)** — the `RepairOracle` closure (`repair-oracle.ts`) reuses the EXISTING
  *    integration sandbox as its grader at ZERO extra sandbox cost. It needs only a `GraderHandle` (a writeFile +

package/dist/leader/grader-env-factory.js

@@ -1,6 +1,6 @@
 /**
  * The OUT-OF-PROCESS grader plumbing for the leader × `runRepairLoop` integration
- * (`docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.2 + the authoritative §10 layer). Two distinct consumers:
+ * (`sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.2 + the authoritative §10 layer). Two distinct consumers:
  *
  *  - **R1 (single-agent oracle, §10.1)** — the `RepairOracle` closure (`repair-oracle.ts`) reuses the EXISTING
  *    integration sandbox as its grader at ZERO extra sandbox cost. It needs only a `GraderHandle` (a writeFile +
@@ -126,7 +126,7 @@ export function createGraderEnvFactory(_cfg) {
     return async () => {
         throw new Error("createGraderEnvFactory: the standalone control-plane grader is the auto-accept slice (LEADER_GRADER_FACTORY) — " +
             "NOT wired in v1 (which reuses the integration sandbox for R1 and re-seeds it for R2). " +
-            "See docs/LEADER-REPAIRLOOP-INTEGRATION.md §3.2/§7.");
+            "See sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md §3.2/§7.");
     };
 }
 //# sourceMappingURL=grader-env-factory.js.map

package/dist/leader/repair-oracle.d.ts

@@ -1,6 +1,6 @@
 /**
  * The PROFILE-injected `RepairOracle` closure for the leader's single-agent self-repair loop
- * (`runRepairLoop`, core design/78 / D1). See `docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
+ * (`runRepairLoop`, core design/78 / D1). See `sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
  * §10 corrected layer). The closure GRADES a worker's candidate in an ISOLATED grader env (the reused
  * integration sandbox, distinct from the worker env) and maps the result to a core `OracleResult`. core only
  * fixes the `OracleResult` shape + the read-only/identity contract; the composition lives HERE so the core type

package/dist/leader/repair-oracle.js

@@ -1,6 +1,6 @@
 /**
  * The PROFILE-injected `RepairOracle` closure for the leader's single-agent self-repair loop
- * (`runRepairLoop`, core design/78 / D1). See `docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
+ * (`runRepairLoop`, core design/78 / D1). See `sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` (§3.1 + the authoritative
  * §10 corrected layer). The closure GRADES a worker's candidate in an ISOLATED grader env (the reused
  * integration sandbox, distinct from the worker env) and maps the result to a core `OracleResult`. core only
  * fixes the `OracleResult` shape + the read-only/identity contract; the composition lives HERE so the core type

package/dist/leader/repair-wire.d.ts

@@ -1,6 +1,6 @@
 /**
  * The WIRE that wraps core `runRepairLoop` onto the leader's single-agent path
- * (`docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.3 + the authoritative §10 layer). It owns the three things the
+ * (`sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.3 + the authoritative §10 layer). It owns the three things the
  * `RepairOracle` closure (`repair-oracle.ts`) and the core engine CANNOT resolve themselves:
  *
  *  1. **The grader handle (R1, §10.1)** — the reused integration sandbox's writeFile/exec + `integBase`, bound by

package/dist/leader/repair-wire.js

@@ -1,6 +1,6 @@
 /**
  * The WIRE that wraps core `runRepairLoop` onto the leader's single-agent path
- * (`docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.3 + the authoritative §10 layer). It owns the three things the
+ * (`sema-internal server/docs/LEADER-REPAIRLOOP-INTEGRATION.md` §3.3 + the authoritative §10 layer). It owns the three things the
  * `RepairOracle` closure (`repair-oracle.ts`) and the core engine CANNOT resolve themselves:
  *
  *  1. **The grader handle (R1, §10.1)** — the reused integration sandbox's writeFile/exec + `integBase`, bound by

package/dist/main.js

@@ -784,7 +784,7 @@ async function main() {
         // 🔴 复审 2026-07-28(E-HIGH-1)修:此键是 **ServiceDeps** 字段,原先被 spread 进 `runnerDeps`
         // (core 的 RunnerDeps 无此字段,条件 spread 绕过 TS 多余属性检查 ⇒ 编译期无声)⇒ HTTP 面恒
         // undefined、413 前置是死枝、超帽仍走 502。落错家的死键病族(verify-cost 先例)——接线钉见
-        // test/review-2026-07-28-batch1.test.ts。
+        // test/deps-literal-shape-gate.test.ts(2026-07-28 那批复审文件已按仓规折进主题文件,钉本体在 E-HIGH-1 那个 describe)。
         snapshotBlobSqlCapBytes: backend && backend.kind !== "local" && !config.snapshotBlobStore
             ? (config.snapshotBlobSqlMaxBytes ?? (backend.kind === "mysql" ? SQL_BLOB_DEFAULT_MAX_BYTES : undefined))
             : undefined,

package/dist/memory-sync.js

@@ -1,4 +1,4 @@
-// 142-S2.5 中心侧同步 API 的执行内核(设计 docs/design/142-S4-DATAPLANE.md §2.5;裁定:
+// 142-S2.5 中心侧同步 API 的执行内核(设计 sema-internal server/docs/design/142-S4-DATAPLANE.md §2.5;裁定:
 // **plan 随数据走,core 零运行时半场**——core 的 `reconcileMemoryEntries`/`nextSyncBaseline`/
 // `screenInboundEntries` 是纯函数导出,持数据的一侧(本 server=DB 权威+per-(scope,peer) 游标)直接
 // import 调用算 plan 并执行 CAS;API 面全在 server,core 的承诺=纯函数语义稳定。

package/dist/observability/metrics.js

@@ -254,7 +254,7 @@ export function createMetrics() {
     // E18 resume-at: a per-turn anchor capture (getLeafId→put) failed (e.g. an un-migrated DB missing resume_anchor) —
     // best-effort, never fails the run; this surfaces a SYSTEMATIC capture outage instead of a silent feature stoppage.
     m.counter("resume_anchor_capture_failed", "E18 resume-at per-turn anchor captures that failed (best-effort, run unaffected)");
-    // Silent-fallback telemetry P0 batch (docs/design/SILENT-FALLBACK-TELEMETRY.md, service half):
+    // Silent-fallback telemetry P0 batch (sema-internal server/docs/design/SILENT-FALLBACK-TELEMETRY.md, service half):
     // S4 — brain-layer liveness phases (rate_limited/retrying/reconnecting/circuit_open) were previously visible
     // only on the live SSE stream; count them so upstream throttling/outage is graphable per phase.
     m.counter("brain_retry_total", "Brain-layer status events (S4), by phase (rate_limited/retrying/reconnecting/circuit_open)");

package/dist/plan-cache-probe.js

@@ -1,4 +1,6 @@
-// Verbatim from core strategy-store.ts (keep in sync if core changes its stopword set).
+// Verbatim from core strategy-store.ts. 🔴 「keep in sync」不是靠这句话 —— lockstep 活钉在
+// test/plan-cache-probe.test.ts(真读 core 的 dist strategy-store.js 做 set diff + 切词正则/阈值同源),
+// 任一侧改词表当场红。2026-07-30 之前这里只有声明没有钉:删掉一个词全量零红(实测)。
 const STOP = new Set([
     "the", "and", "for", "with", "from", "this", "that", "into", "your", "you", "are", "was", "were", "has",
     "have", "had", "not", "but", "all", "any", "can", "use", "using", "via", "then", "than", "out", "get",

package/dist/plugins/approval-exemption-store.js

@@ -1,6 +1,6 @@
 /**
  * Per-session per-toolName approval exemption ("本会话不再询问",
- * design: docs/design/APPROVAL-SESSION-EXEMPTION.md).
+ * design: sema-internal server/docs/design/APPROVAL-SESSION-EXEMPTION.md).
  *
  * SEMANTICS (the boundary that keeps this an APPROVAL MEMORY, not a policy loosen): a granted row makes the
  * F4 ask-gate SKIP the human ask for that (sessionId, canonicalToolName) — it is consulted ONLY after

package/dist/plugins/pg-pool.js

@@ -117,7 +117,7 @@ export const PG_SCHEMA_STATEMENTS = [
    )`,
     `CREATE INDEX IF NOT EXISTS idx_resume_anchor_session ON resume_anchor (session_id)`,
     // Per-session per-toolName approval exemption (the PG twin — see tidb-pool.ts /
-    // docs/design/APPROVAL-SESSION-EXEMPTION.md).
+    // sema-internal server/docs/design/APPROVAL-SESSION-EXEMPTION.md).
     `CREATE TABLE IF NOT EXISTS approval_exemption (
      session_id VARCHAR(64)    NOT NULL,
      tool_name  VARCHAR(190)   NOT NULL,

package/dist/plugins/remote-env-k8s.d.ts

@@ -69,7 +69,7 @@ export interface K8sEnvConfig {
      * image/command), which are set OUTSIDE the patched fields.
      */
     podSpecPatch?: PodSpecPatch;
-    /** RFC B5 (docs/design/ENV-SELECT-AND-REGION-SOURCE.md 抽象点②): operator-trusted env injected into the
+    /** RFC B5 (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md 抽象点②): operator-trusted env injected into the
      *  sandbox container (e.g. `SEMA_PKG_SOURCE=cn|global` — the runtime package-source selector the image's
      *  pkg-source.sh hook materializes at start). Deployment-region config, NEVER task-controlled. Absent = the
      *  pod is byte-identical to today. */

package/dist/plugins/tidb-pool.js

@@ -305,7 +305,7 @@ export const SCHEMA_STATEMENTS = [
    )`,
     // Per-session per-toolName approval exemption ("本会话不再询问") — an APPROVAL MEMORY the
     // F4 ask-gate consults AFTER deny/neverAuto (both always win). tool_name is CANONICAL space. GC'd with
-    // the session (E21 delete). See docs/design/APPROVAL-SESSION-EXEMPTION.md.
+    // the session (E21 delete). See sema-internal server/docs/design/APPROVAL-SESSION-EXEMPTION.md.
     `CREATE TABLE IF NOT EXISTS approval_exemption (
      session_id VARCHAR(64)  NOT NULL,
      tool_name  VARCHAR(190) NOT NULL,

package/dist/router/route-orchestration.d.ts

@@ -1,5 +1,5 @@
 /**
- * The A value router — cash out the S1 supervisor value verdict (docs/S1-VALUE-VERDICT.md §6.3) into a per-task
+ * The A value router — cash out the S1 supervisor value verdict (sema-internal server/docs/S1-VALUE-VERDICT.md §6.3) into a per-task
  * orchestration decision: run a task as `single` / `supervisor` / `team`.
  *
  * The verdict, in one line: **competent tasks have SUP/TEAM dominated (pure overhead) ⇒ default single; the real

package/dist/router/route-orchestration.js

@@ -1,5 +1,5 @@
 /**
- * The A value router — cash out the S1 supervisor value verdict (docs/S1-VALUE-VERDICT.md §6.3) into a per-task
+ * The A value router — cash out the S1 supervisor value verdict (sema-internal server/docs/S1-VALUE-VERDICT.md §6.3) into a per-task
  * orchestration decision: run a task as `single` / `supervisor` / `team`.
  *
  * The verdict, in one line: **competent tasks have SUP/TEAM dominated (pure overhead) ⇒ default single; the real

package/dist/sandbox-pkg-source.d.ts

@@ -1,5 +1,5 @@
 /**
- * RFC B5/B4 抽象点② (docs/design/ENV-SELECT-AND-REGION-SOURCE.md): the deployment-region package-source →
+ * RFC B5/B4 抽象点② (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md): the deployment-region package-source →
  * sandbox env derivation. ENV-FIRST: pod/sandbox env OVERRIDES the image's baked `ENV` (k8s container env wins
  * over image config and is visible to every exec'd process; e2b sandboxEnv likewise) — so the env-overridable
  * ecosystem pieces (pip/uv/npm/corepack/go/rustup/flutter/playwright/nuget) switch region on EXISTING images,

package/dist/sandbox-pkg-source.js

@@ -1,5 +1,5 @@
 /**
- * RFC B5/B4 抽象点② (docs/design/ENV-SELECT-AND-REGION-SOURCE.md): the deployment-region package-source →
+ * RFC B5/B4 抽象点② (sema-internal server/docs/design/ENV-SELECT-AND-REGION-SOURCE.md): the deployment-region package-source →
  * sandbox env derivation. ENV-FIRST: pod/sandbox env OVERRIDES the image's baked `ENV` (k8s container env wins
  * over image config and is visible to every exec'd process; e2b sandboxEnv likewise) — so the env-overridable
  * ecosystem pieces (pip/uv/npm/corepack/go/rustup/flutter/playwright/nuget) switch region on EXISTING images,

package/dist/session-sync-kernel.d.ts

@@ -11,7 +11,7 @@
  */
 import type { SessionTreeEntry } from "@sema-agent/core";
 /**
- * P1d-β (PUSH streaming, docs/DESIGN-session-sync.md §15 + the persistence synthesis) — a TWO-PHASE STAGED import
+ * P1d-β (PUSH streaming, sema-internal server/docs/DESIGN-session-sync.md §15 + the persistence synthesis) — a TWO-PHASE STAGED import
  * handle. The whole-bundle `importSession` (session-sync.ts) buffers every entry in one JSON body (server memory ∝ session size);
  * β instead STREAMS the entry log (NDJSON) into a SHADOW session id, validating it ONLINE per line through core's
  * StreamingImportValidator (the single invariant gate — core 1.143.0), then ATOMICALLY swaps

package/dist/session-sync.d.ts

@@ -1,6 +1,6 @@
 /**
  * 2c session-sync — P1b ORCHESTRATION: export a session's WHOLE portable state from one StoreBackend and import it
- * verbatim into another (the seamless local↔cloud "save state" move; docs/DESIGN-session-sync.md §5–§10). All the
+ * verbatim into another (the seamless local↔cloud "save state" move; sema-internal server/docs/DESIGN-session-sync.md §5–§10). All the
  * per-store PRIMITIVES already exist (P1a entries + P1b snapshots/policy/anchor); this module is the COORDINATOR that
  * (a) reads them into a {@link SessionBundle} and (b) replays them across backends in the §8 fail-closed atomic order.
  *

package/dist/task-settings.d.ts

@@ -20,7 +20,7 @@
  *    ——但深层不变量未变:bypass=「不加 ask 门」,恒不越部署基线(tightenTaskSpec deny-wins,基线 deny/
  *    ask 照压);精化语义见 :2xx 行内注释。旧头注的「NEVER honored/三模式白名单」是 pre-[816] 拍照。
  *
- * 🔴 SYNC WITH shell `src/sema/settings/seam.ts`: the permissions→toolPolicy + §6.4 permissionMode derive MIRRORS
+ * 🔴 SYNC WITH sema-cli(壳仓)的 `src/sema/settings/seam.ts`: the permissions→toolPolicy + §6.4 permissionMode derive MIRRORS
  * the shell's LOCAL-Runner resolver — both compose the SAME core primitives (`createAllowDenyPolicy` /
  * `combinePolicies` / `tightenTaskSpec`), so the deny-wins ENFORCEMENT is core-single-source. Only the COMPOSITION
  * is duplicated for the remote path; a proposed follow-up extracts it to `@sema-agent/sdk` for true

package/dist/task-settings.js

@@ -20,7 +20,7 @@
  *    ——但深层不变量未变:bypass=「不加 ask 门」,恒不越部署基线(tightenTaskSpec deny-wins,基线 deny/
  *    ask 照压);精化语义见 :2xx 行内注释。旧头注的「NEVER honored/三模式白名单」是 pre-[816] 拍照。
  *
- * 🔴 SYNC WITH shell `src/sema/settings/seam.ts`: the permissions→toolPolicy + §6.4 permissionMode derive MIRRORS
+ * 🔴 SYNC WITH sema-cli(壳仓)的 `src/sema/settings/seam.ts`: the permissions→toolPolicy + §6.4 permissionMode derive MIRRORS
  * the shell's LOCAL-Runner resolver — both compose the SAME core primitives (`createAllowDenyPolicy` /
  * `combinePolicies` / `tightenTaskSpec`), so the deny-wins ENFORCEMENT is core-single-source. Only the COMPOSITION
  * is duplicated for the remote path; a proposed follow-up extracts it to `@sema-agent/sdk` for true

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "3.4.1",
+  "version": "3.4.2",
   "description": "Sema Server — the server/API implementation layer for Sema, wiring core, registry, model providers, and cloud agent execution. Built on @sema-agent/core.",
   "type": "module",
   "license": "BUSL-1.1",