@sema-agent/server 7.104.0 → 7.106.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "7.104.0",
+  "version": "7.106.0",
   "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",
@@ -61,7 +61,7 @@
     "build:binary:run-local:darwin-arm64": "bun build --compile --target=bun-darwin-arm64 src/run-local.ts --outfile dist/run-local-darwin-arm64"
   },
   "dependencies": {
-    "@sema-agent/core": "7.33.8",
+    "@sema-agent/core": "7.35.2",
     "@sema-agent/settings-schema": "6.3.0",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",
@@ -77,7 +77,7 @@
     "sharp": "^0.35.3"
   },
   "devDependencies": {
-    "@sema-agent/sdk": "12.0.1",
+    "@sema-agent/sdk": "13.1.0",
     "@types/libsodium-wrappers": "^0.7.14",
     "@types/node": "22.10.2",
     "@types/pg": "^8.20.0",

package/dist/boot/session-shell-gate-registry.d.ts

@@ -1,39 +0,0 @@
-/**
- * [ref] 件⑤(core PM 三仓扫查 [ref] server 条 ③,并入 [ref])—— 「本 run 是否**显式**声明了 bypassPermissions」的
- * per-session 登记簿,供 `boot/runner-deps.ts` 的 `onError(phase:"config")` 汇点给 core 的 `shell-gate-off`
- * 忠告定级。
- *
- * ## 为什么需要它
- * core 在「shell 门 doctrine=off ∧ 挂了真可写 Bash」时经 `onError(phase:"config", classification:"shell-gate-off")`
- * 发一条忠告(`prepare-hands-readface.js`),但它分不清 off 是**调用方显式选的**(server 把 `permissionMode:
- * "bypassPermissions"` 翻成 `shellGate:"off"`,[ref] 表)还是**没表态落到 core 默认**(无壳直连部署,真值得
- * 一条 warn)。这正是真实用户提案里「bypass 下照打 shell gate doctrine is off 告警」的根:正常态被当异常打。
- * 汇点只拿到 `ctx.sessionId`,而生效模式是 server 在 resolve-spec 阶段④ 单点算出的(`effectivePermissionMode`),
- * 所以由 resolve-spec 在算出 effMode 的那一行登记、汇点按 sessionId 回查。
- *
- * ## 键
- * `auth.sessionId`:authorizer 在服务路径上**恒**铸 session id(`security.ts` `uuidv7()`,core 的无 sessionId
- * 分支在服务路径不可达),且 spec.sessionId = 同一值 ⇒ core 回调的 `ctx.sessionId` 与登记键同源。
- * 缺 authorizer 的裸装配(测试桩)拿不到键 ⇒ 不登记 ⇒ 汇点按「未声明」处理 = 仍 warn(退化方向=多一条告警,
- * 不是少一条)。
- *
- * ## 已知界(codex r2 [medium],登记不修:属主在 core 回调契约)
- * 键是 session 而非**执行**:同 session 并发第二次提交在 resolveSpec 后才被 409 拒,其登记已覆盖前一次——若被拒的
- * 那次是 bypass 而在跑的那次不是,且忠告恰在这一窗内发出,则一条本该 warn 的 `shell-gate-off` 被降成 info(仍整行
- * 落日志、字段齐全,执法零变)。窗 = 在跑 run 的 resolveSpec 到其 prepare 期忠告之间(毫秒级,且要同 session 并发
- * 提交 + 模式相反)。执行唯一的归因需要 core 回调 `ctx` 带 taskId / shellGate 出处(已作 core 侧诉求登记),
- * 到货后本簿退役。
- *
- * ## 界
- * 有界 Map(插入序淘汰,默认 10k 条,与 caps 缓存同量级):session id 是开集,长命 worker 不能无界累积。
- * 淘汰掉的旧会话再来忠告时同样回落「未声明」⇒ warn(同一退化方向)。每次 resolve 覆写(同 session 后一轮改
- * 模式时以最近一轮为准;续跑四条 rebuild 腿都经 resolveSpec ⇒ 同律登记)。
- */
-export interface SessionShellGateRegistry {
-    /** resolve-spec 阶段④:登记本 session 这一轮是否显式声明 bypassPermissions(= server 翻成 shellGate:"off")。 */
-    note(sessionId: string | undefined, explicitOff: boolean): void;
-    /** runner-deps 汇点:本 session 最近一轮是否显式声明了 off。未登记/已淘汰 ⇒ false(退化=照 warn)。 */
-    explicitlyOff(sessionId: string): boolean;
-}
-export declare function createSessionShellGateRegistry(cap?: number): SessionShellGateRegistry;
-//# sourceMappingURL=session-shell-gate-registry.d.ts.map

package/dist/boot/session-shell-gate-registry.js

@@ -1,21 +0,0 @@
-export function createSessionShellGateRegistry(cap = 10_000) {
-    const off = new Map();
-    return {
-        note(sessionId, explicitOff) {
-            if (sessionId === undefined)
-                return;
-            if (off.has(sessionId))
-                off.delete(sessionId);
-            else if (off.size >= cap) {
-                const oldest = off.keys().next();
-                if (!oldest.done)
-                    off.delete(oldest.value);
-            }
-            off.set(sessionId, explicitOff);
-        },
-        explicitlyOff(sessionId) {
-            return off.get(sessionId) === true;
-        },
-    };
-}
-//# sourceMappingURL=session-shell-gate-registry.js.map

package/dist/plugins/memory-session-policy-store.d.ts

@@ -1,46 +0,0 @@
-/**
- * In-memory SessionPolicyStore + the service's `deleteBySession` extension (E21 purge / 2c overwrite-dst wipe).
- *
- * WHY THIS EXISTS (and not core's `InMemorySessionPolicyStore`): core's in-memory/file policy stores implement only
- * the core interface (getRules/putRules/listBySession) — they have NO deletion seam, so neither the E21 session purge
- * nor the 2c `overwrite-dst` subsystem wipe can remove policy rows on a backend that uses them (the SQL twins carry
- * `deleteBySession` as a service extension; see session-policy-store-sql.ts). This store is the delete-capable
- * in-memory twin. The seam itself is also requested upstream (core: optional `deleteBySession?` on the interface +
- * the File/InMemory impls) — if core lands it, this class can retire in favor of core's.
- *
- * BYTE-MATCH DISCIPLINE: getRules/putRules/listBySession replicate core's `InMemorySessionPolicyStore` semantics
- * exactly (same key shape, same CAS `conflict` on expectedRev mismatch, same tighten-only `loosen_forbidden` gate via
- * core's exported `normalizeRules`/`loosenReasons`/`stripRev`, same rev start/bump). Any divergence is a bug here.
- * S-529 起同样钉住 `@contract session_policy.rev_survives_delete`:`deleteBySession` 保留每把键的 rev 高水位
- * **并给那把键的世代(`gen`)+1**(见 {@link MemorySessionPolicyStore.deleteBySession});共用试剂盒
- * `test/helpers/session-policy-rev-line-contract.ts` 与 SQL 双生、以及 core 自己的 `InMemorySessionPolicyStore`
- * (7.25.0 起带这条契约,已作为第三只引擎接进同一只试剂盒当 oracle)跑同一段剧本。
- */
-import { type PutRulesOptions, type SessionPermissionRules, type SessionPolicyStore, type SessionRulesRecord, type StoredSessionRules } from "@sema-agent/core";
-export declare class MemorySessionPolicyStore implements SessionPolicyStore {
-    private readonly map;
-    /** S-529 —— 每把键的 rev **高水位 + 世代**(`@contract session_policy.rev_survives_delete`):`deleteBySession`
-     *  抹掉规则行时把它那条 rev 线的终点留在这里,于是删后首写 stamp 的是 `max(当前行 rev, 记号.rev) + 1`,
-     *  而不是从 1 重来;同时把 `gen` +1 —— **抹除终结的是那一行的血统**,下一次写开的是新世代,读侧因此能把
-     *  「重建的行」与「它正在执行的那一行的延续」分开,无论新行的 rev 有多大(core 7.25.0 [ref] 判词:
-     *  没有世代时读侧只能靠「亲眼看见行消失」那条弱守卫,于是两道门之间未被观察到的 erase+重建抓不住,
-     *  而一次瞬时读 null 会把该腿永久闩在旧行上)。
-     *  与 SQL 双生的 `session_policy_rev_mark` 表、core File 店的 `<stem>.hwm.json` 侧车是同一条律的三个实现体
-     *  (SQL 那边的表注写了为什么不留墓碑行)。本表只增不减、条目是两个整数 —— 与 `map` 同为进程内结构,
-     *  随进程亡;跨副本的持久面在 SQL 双生那半。 */
-    private readonly marks;
-    private key;
-    getRules(sessionId: string, principal?: string): Promise<StoredSessionRules | null>;
-    putRules(sessionId: string, principal: string | undefined, rules: SessionPermissionRules, opts?: PutRulesOptions): Promise<StoredSessionRules>;
-    listBySession(sessionId: string): Promise<SessionRulesRecord[]>;
-    /** Purge ALL policy rows for a session, across every principal — KEEPING each key's rev high-water mark.
-     *  Scoped by session_id alone — the caller (E21 route / importSession overwrite-dst) already proved ownership.
-     *  Shape = core 1.423's optional `SessionPolicyStore.deleteBySession?` seam (`Promise<void>` — the count was
-     *  incidental; nothing consumed it).
-     *
-     *  S-529:规则本身死,rev 线不死(`@contract session_policy.rev_survives_delete`)。记号只升不降(`Math.max`),
-     *  所以反复抹除不会把线走回头;从没写过的键不留记号(没有线就不凭空抬)。**抹除同时终结那一行的血统**:
-     *  `gen` +1,于是下一次写开的是新世代 —— 数字继续爬,但读侧按世代判「这不是我在执行的那一行的延续」。 */
-    deleteBySession(sessionId: string): Promise<void>;
-}
-//# sourceMappingURL=memory-session-policy-store.d.ts.map

package/dist/plugins/memory-session-policy-store.js

@@ -1,52 +0,0 @@
-import { normalizeRules, loosenReasons, stripRev, SessionPolicyError, } from "@sema-agent/core";
-export class MemorySessionPolicyStore {
-    map = new Map();
-    marks = new Map();
-    key(sessionId, principal) {
-        return JSON.stringify([sessionId, principal ?? null]);
-    }
-    async getRules(sessionId, principal) {
-        const r = this.map.get(this.key(sessionId, principal));
-        return r ? structuredClone(r) : null;
-    }
-    async putRules(sessionId, principal, rules, opts) {
-        const key = this.key(sessionId, principal);
-        const prior = this.map.get(key);
-        if (opts?.expectedRev !== undefined && (prior?.rev ?? 0) !== opts.expectedRev) {
-            throw new SessionPolicyError("conflict", `session rules rev mismatch (expected ${opts.expectedRev}, have ${prior?.rev ?? 0})`);
-        }
-        const clean = normalizeRules(stripRev(rules));
-        if (prior && opts?.operator !== true) {
-            const loosens = loosenReasons(prior, clean);
-            if (loosens.length > 0) {
-                throw new SessionPolicyError("loosen_forbidden", `a non-operator session-rule write may only tighten; refused: ${loosens.join("; ")}`);
-            }
-        }
-        const mark = this.marks.get(key) ?? { rev: 0, gen: 0 };
-        const gen = prior?.gen ?? mark.gen;
-        const next = { ...structuredClone(clean), rev: Math.max(prior?.rev ?? 0, mark.rev) + 1, gen };
-        this.map.set(key, next);
-        this.marks.set(key, { rev: next.rev, gen });
-        return structuredClone(next);
-    }
-    async listBySession(sessionId) {
-        const out = [];
-        for (const [k, rules] of this.map) {
-            const [sid, principal] = JSON.parse(k);
-            if (sid === sessionId)
-                out.push({ principal: principal ?? undefined, rules: structuredClone(rules) });
-        }
-        return out;
-    }
-    async deleteBySession(sessionId) {
-        for (const [k, rules] of [...this.map]) {
-            const [sid] = JSON.parse(k);
-            if (sid !== sessionId)
-                continue;
-            const mark = this.marks.get(k) ?? { rev: 0, gen: 0 };
-            this.marks.set(k, { rev: Math.max(mark.rev, rules.rev), gen: mark.gen + 1 });
-            this.map.delete(k);
-        }
-    }
-}
-//# sourceMappingURL=memory-session-policy-store.js.map

package/dist/roster-bound-http-status.d.ts

@@ -1,6 +0,0 @@
-export declare const ROSTER_BOUND_HTTP_STATUS: {
-    readonly "config.tool_name_too_long": 503;
-    readonly "config.tool_contract_too_long": 503;
-    readonly "config.tool_roster_bound": 503;
-};
-//# sourceMappingURL=roster-bound-http-status.d.ts.map

package/dist/roster-bound-http-status.js

@@ -1,6 +0,0 @@
-export const ROSTER_BOUND_HTTP_STATUS = {
-    "config.tool_name_too_long": 503,
-    "config.tool_contract_too_long": 503,
-    "config.tool_roster_bound": 503,
-};
-//# sourceMappingURL=roster-bound-http-status.js.map