@sema-agent/server 7.55.0 → 7.57.0

package/dist/trace/sema-provenance.d.ts

@@ -0,0 +1,26 @@
+/**
+ * [ref](a)(core 7.2.0 / [ref] 片6 d1):`task_notification` 帧上 `_sema_provenance` typed 归因侧记的
+ * **单点**投影判据——live 三腿(`trace/project.ts` 的 `taskNotificationEventData`)与 park 半场
+ * (`orchestration/workflow-completion-inbox.ts` 的 `taskNotificationInboxEntry`)共用,两腿字节同判。
+ *
+ * `kind` 是**闭集**——wire 上只许出现 core 词表里的 lane 词。两向锚([ref]/[ref] 同纪律,与
+ * routes/notify-wake.ts 的 `NOTIFY_STATUSES` 同形):`satisfies` 保「表内无词表外的词」(core 删/改词 ⇒ 编译红),
+ * 穷举断言保「词表无表外的词」(core 加 lane ⇒ 编译红,新词必须由人处置——它是 cli 渲染判别键,静默透传一个
+ * 未知 lane 等于替 core 声明一种渲染形)。运行期闭集外的值(上游漂了 / 载荷被改过)⇒ **丢整键**,与 `priority`
+ * 的闭集守卫(`trace/injection-tier.ts`)同判:消费端退回老形卡,不按未知 lane 猜;`agentMessage` 不受牵连
+ * (它是渲染判别,不是 lane 词)。
+ */
+import type { SemaProvenance } from "@sema-agent/core";
+export declare const SEMA_PROVENANCE_KINDS: readonly ["agent_message"];
+/** 本仓两条腿入参的**形**(不是 core 类型:入参是运行期载荷,`kind` 先当 string 收、经闭集才成 typed)。 */
+export interface SemaProvenanceInput {
+    kind: string;
+    from: string;
+    taskId: string;
+    seq: number;
+    agentType?: string;
+}
+/** 逐成员挑取(绝不 spread —— core 给侧记加成员时必须经 keyset 门处置,见 `trace/core-keyset-guard.ts` ①);
+ *  返回 undefined = 闭集外 / 形不合 ⇒ 调用方丢整键。`agentType` 缺席不编(本 mount 恒缺席,在场即透传)。 */
+export declare function semaProvenanceOrAbsent(p: SemaProvenanceInput): SemaProvenance | undefined;
+//# sourceMappingURL=sema-provenance.d.ts.map

package/dist/trace/sema-provenance.js

@@ -0,0 +1,11 @@
+export const SEMA_PROVENANCE_KINDS = ["agent_message"];
+const _semaProvenanceExhaustive = true;
+void _semaProvenanceExhaustive;
+export function semaProvenanceOrAbsent(p) {
+    if (!SEMA_PROVENANCE_KINDS.includes(p.kind))
+        return undefined;
+    if (typeof p.from !== "string" || typeof p.taskId !== "string" || typeof p.seq !== "number")
+        return undefined;
+    return { kind: p.kind, from: p.from, taskId: p.taskId, seq: p.seq, ...(typeof p.agentType === "string" ? { agentType: p.agentType } : {}) };
+}
+//# sourceMappingURL=sema-provenance.js.map

package/dist/turn-activity.d.ts

@@ -21,10 +21,40 @@
  * 提交——不清的话新 run 首次打点前会读到旧 run 的时刻 = 假「刚有活性」证据。清点 = 三个 createRun
  * 成功分支(routes/runs.ts + routes/tasks.ts×2,接线锚在 session-active-conflict-materials 测试)。
  */
-/** ledger sink 每次 durable append 时打点(装配点:runs.ts / routes/tasks.ts 的 createLedgerSink)。 */
-export declare function recordTurnActivity(taskId: string): void;
+import type { RunBrainStatusSnapshot } from "./plugins/store-contracts.js";
+/** 一次打点的读数。`kind` = 触发这次打点的 durable 事件类型;打点方拿不到类型(core 的 onActivity
+ *  第五席、resume 腿的手动打点)⇒ 缺席,**绝不铸占位词** —— [ref] 的 `cancelContext.lastEventKind`
+ *  会原样上 wire,一个编出来的 `"unknown"` 会被消费端读成「引擎真发过一条叫 unknown 的事件」。
+ *
+ *  `brainStatus` = 本 run 账本尾**最后一条** `status` 帧的判别五键([ref]/[ref]:重试相位早已在
+ *  wire 上,server 侧不需要 core 新钩就能回答「已重试几次 / 在等什么」)。它是 **sticky** 的 ——
+ *  后续别的事件(text/tool)打点**不清**它:问题是「上次大脑说了什么」,不是「上一条事件是不是大脑说的」。 */
+export interface TurnActivity {
+    at: number;
+    kind?: string;
+    brainStatus?: RunBrainStatusSnapshot;
+}
+/**
+ * ledger sink 每次 durable append 时打点(装配点:runs.ts / routes/tasks.ts 的 createLedgerSink)。
+ *
+ * @param kind 账本写口传得出事件类型就传([ref] 件3 的判别材料),传不出就省。
+ * @param statusData `status` 帧的**已投影**载荷(`trace/project.ts` 的 `brainStatusEventData` 产物)。
+ *   只有 `status` 那一路传;本函数从中挑出五键存起来,并 **sticky 保留**到下一条 status 帧到来。
+ *   之所以在这里挑而不是在 sink 里挑:挑法与存法同一个属主,sink 不必认识这个类型。
+ */
+export declare function recordTurnActivity(taskId: string, kind?: string, statusData?: Record<string, unknown>): void;
+/**
+ * `brainStatusEventData` 的投影产物 → {@link RunBrainStatusSnapshot} 的五键子集。
+ *
+ * 逐键**按型收**(不是整只透传):投影产物是给账本行用的宽面(还带 `detail` / `retryInMs` /
+ * `eventId` / 身份键),而 `cancelContext` 是分诊便签 —— `detail` 是**模型/provider 的自由文本**
+ * (已过 redactSecrets,但仍是宽面),不进这只小快照。非期望型的值一律丢(不铸)。
+ */
+export declare function pickRunBrainStatus(data: Record<string, unknown> | undefined): RunBrainStatusSnapshot | undefined;
 /** 最后活性时刻(epoch ms);无记录 ⇒ undefined(缺席语义见顶注)。 */
 export declare function readTurnActivityMs(taskId: string): number | undefined;
+/** 最后一次打点的完整读数(时刻 + 事件类型);无记录 ⇒ undefined。[ref] 件3 的数据源。 */
+export declare function readTurnActivity(taskId: string): TurnActivity | undefined;
 /** 测试隔离用(生产路径不调:终局不清的理由见顶注)。 */
 export declare function clearTurnActivity(taskId: string): void;
 //# sourceMappingURL=turn-activity.d.ts.map

package/dist/turn-activity.js

@@ -1,7 +1,8 @@
 const CAP = 8192;
 const lastActivityByTask = new Map();
-export function recordTurnActivity(taskId) {
-    if (lastActivityByTask.has(taskId)) {
+export function recordTurnActivity(taskId, kind, statusData) {
+    const prev = lastActivityByTask.get(taskId);
+    if (prev !== undefined) {
         lastActivityByTask.delete(taskId);
     }
     else if (lastActivityByTask.size >= CAP) {
@@ -9,10 +10,34 @@ export function recordTurnActivity(taskId) {
         if (oldest !== undefined)
             lastActivityByTask.delete(oldest);
     }
-    lastActivityByTask.set(taskId, Date.now());
+    const brainStatus = pickRunBrainStatus(statusData) ?? prev?.brainStatus;
+    lastActivityByTask.set(taskId, {
+        at: Date.now(),
+        ...(kind !== undefined ? { kind } : {}),
+        ...(brainStatus !== undefined ? { brainStatus } : {}),
+    });
+}
+export function pickRunBrainStatus(data) {
+    if (data === undefined)
+        return undefined;
+    const phase = data.phase;
+    if (typeof phase !== "string" || phase.length === 0)
+        return undefined;
+    const num = (v) => typeof v === "number" && Number.isFinite(v);
+    return {
+        phase,
+        ...(num(data.attempt) ? { attempt: data.attempt } : {}),
+        ...(num(data.maxRetries) ? { maxRetries: data.maxRetries } : {}),
+        ...(num(data.retryAtMs) ? { retryAtMs: data.retryAtMs } : {}),
+        ...(typeof data.errClass === "string" && data.errClass.length > 0 ? { errClass: data.errClass } : {}),
+    };
 }
 export function readTurnActivityMs(taskId) {
-    return lastActivityByTask.get(taskId);
+    return lastActivityByTask.get(taskId)?.at;
+}
+export function readTurnActivity(taskId) {
+    const a = lastActivityByTask.get(taskId);
+    return a === undefined ? undefined : { ...a };
 }
 export function clearTurnActivity(taskId) {
     lastActivityByTask.delete(taskId);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/server",
-  "version": "7.55.0",
+  "version": "7.57.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",
@@ -54,8 +54,8 @@
     "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.1.0",
-    "@sema-agent/settings-schema": "1.3.0",
+    "@sema-agent/core": "7.2.0",
+    "@sema-agent/settings-schema": "1.4.0",
     "e2b": "^2.28.0",
     "libsodium-wrappers": "^0.8.4",
     "mysql2": "^3.22.4",

package/skills/find-skills.md

@@ -141,7 +141,7 @@ npx skills init my-xyz-skill
 ```
 
 <!--
-TODO (blackboard [832], clay): add our own first-party skill sources here -
+TODO (clay): add our own first-party skill sources here -
 sema-registry / config-center - as a discovery+install lane alongside the open
 skills.sh ecosystem. Not every deployment ships a config-center, so the section
 must probe availability first and fall back to the public ecosystem cleanly.

package/skills/loop.md

@@ -35,7 +35,7 @@ Then briefly confirm what's scheduled (id, human cadence, how to cancel with `Cr
 With no interval, run one iteration of the task now, then call `ScheduleWakeup` to schedule when you resume:
 
 - `delaySeconds`: how long to sleep (runtime clamps to [60, 3600]).
-- `reason`: one short, specific sentence ("watching CI run #123" beats "waiting") — shown to the user and telemetry.
+- `reason`: one short, specific sentence ("watching CI run #4521" beats "waiting") — shown to the user and telemetry.
 - `prompt`: the same /loop input verbatim, so the next firing re-enters this skill and continues the loop. For an autonomous loop with no user prompt, pass the literal sentinel `<<autonomous-loop-dynamic>>` (never the CronCreate-mode `<<autonomous-loop>>` sentinel — ScheduleWakeup always uses the `-dynamic` variant).
 - To END the loop: call `ScheduleWakeup` with `stop: true` and omit every other field — the loop ends immediately and no further wakeups fire.