@sema-agent/settings-schema 3.0.1 → 5.0.0

package/dist/prompts-digest.d.ts

@@ -0,0 +1,16 @@
+/** [1057]① prompts contentDigest:canonical JSON(stableStringify 同姿势:键序稳定+深度护栏)全量 sha256,
+ *  **非盐化**(三方可独立复算)。入参=下发形的 `{sections, scenarioOverrides?}`(packId/contentDigest
+ *  自身不入 hash)。 */
+export declare function promptsContentDigest(payload: {
+    sections: unknown;
+    scenarioOverrides?: unknown;
+}): {
+    contentDigest: string;
+    packId: string;
+    /** [1062]③ 顺带:逐 section 对 `text` 铸的 contentHash(与 core 1.315 校验语义同刻度=
+     *  sha256(text));元素无 string text 位=undefined。center 物化流程=先把这些写回
+     *  declaration.contentHash,再对含 hash 的终形铸整包 digest(本函数对入参原样铸,两步自洽)。 */
+    sectionHashes: Array<string | undefined>;
+};
+/** 逐 section 对账锚(core 1.315 `PromptTextDeclaration.contentHash` 同刻度):sha256(text)。 */
+export declare function sectionContentHash(text: string): string;

package/dist/prompts-digest.js

@@ -0,0 +1,48 @@
+/**
+ * @sema-agent/settings-schema/node — prompts 下发包的**内容摘要**([1057]①/[1062]③)。
+ *
+ * 这两只是跨仓**对账锚**:center 铸、server 透传、core 的 manifest 归因**独立复算**,三方算出同一个值才
+ * 对得上账([1050]② operator 对账位)。所以它们只有一件事要守:**一个刻度**。
+ *
+ * 4.0.0 从 `scheduler-store-node.ts` 搬到这里(不 breaking —— 仍挂在 `./node` 这条 subpath 上,消费方的
+ * import 一个字不用改)。两条理由:①它与调度存储(`scheduled_tasks.json` 的原子读写 + 跨进程变更原语)
+ * 零关系,住在一起只是历史;②搬家顺手把**两个** sha256 铸点合成一只 —— 此前整包 digest 与逐 section
+ * contentHash 各自 `createHash('sha256')` 一次、各自拼一次 `sha256:` 前缀,哪天有人只改一处就成了两个刻度,
+ * 而没有一格会红(门:`test/prompts-digest-4.0.0.test.ts` 逐条看着铸点数与出门前缀数)。
+ *
+ * 摘要用本包**纯实现**的 sha256(`./sha256.ts`),不是 `node:crypto` —— 那份实现与
+ * `createHash("sha256").update(s,"utf8").digest("hex")` 逐字节相同(`test/sha256.test.ts` 逐例压着,
+ * 本模块的门再压一遍摘要值本身),于是整个包的 sha256 只有**一份实现**。
+ */
+import { stableStringify } from './hash.js';
+import { sha256Hex } from './sha256.js';
+/**
+ * 本模块**唯一**的 sha256 铸点:一段 utf8 文本 → `{ hex, anchor }`。`anchor` = 出门形 `sha256:<hex>`
+ * (自描述算法,与 skills 的内容地址同形),`hex` 给需要裸 hex 的那一处(packId 取前 12 位)。
+ * 两个出门形从**同一次**摘要派生 —— 这正是本模块存在的理由。
+ */
+function contentAnchor(text) {
+    const hex = sha256Hex(text);
+    return { hex, anchor: `sha256:${hex}` };
+}
+/** [1057]① prompts contentDigest:canonical JSON(stableStringify 同姿势:键序稳定+深度护栏)全量 sha256,
+ *  **非盐化**(三方可独立复算)。入参=下发形的 `{sections, scenarioOverrides?}`(packId/contentDigest
+ *  自身不入 hash)。 */
+export function promptsContentDigest(payload) {
+    const canonical = stableStringify({
+        sections: payload.sections,
+        ...(payload.scenarioOverrides !== undefined ? { scenarioOverrides: payload.scenarioOverrides } : {}),
+    });
+    const { hex, anchor } = contentAnchor(canonical);
+    const sectionHashes = Array.isArray(payload.sections)
+        ? payload.sections.map((s) => {
+            const t = s?.text;
+            return typeof t === 'string' ? sectionContentHash(t) : undefined;
+        })
+        : [];
+    return { contentDigest: anchor, packId: `center:${hex.slice(0, 12)}`, sectionHashes };
+}
+/** 逐 section 对账锚(core 1.315 `PromptTextDeclaration.contentHash` 同刻度):sha256(text)。 */
+export function sectionContentHash(text) {
+    return contentAnchor(text).anchor;
+}

package/dist/scheduler-store-node.d.ts

@@ -13,8 +13,13 @@ export declare function loadSchedulerStore(path: string): SchedulerRecord[];
  * concurrent reader never sees a partial file). Throws on IO failure (caller maps to a domain error).
  */
 export declare function saveSchedulerStore(path: string, records: SchedulerRecord[]): void;
-/** A filesystem-backed {@link SchedulerStore} bound to a path (convenience for the daemon/backend constructors). */
-export declare function fileSchedulerStore(path: string): SchedulerStore;
+/** A filesystem-backed {@link SchedulerStore} bound to a path (convenience for the daemon/backend constructors).
+ *
+ * 4.0.0 BREAKING 改名(S-571 B5,**零别名**):旧名 `fileSchedulerStore` 已删。它返回一只带 `load`/`save`
+ * 的**活对象** ⇒ 按本组工厂命名法(`build*` 出纯数据、`create*` 出活对象)该叫 `create*`;2.0.0 那次照人眼
+ * 改只改到了 `createSiblingResolver`,漏了这处 —— 现在由 `test/factory-naming-4.0.0.test.ts` 的门④ 机器看着。
+ * 消费方改调 `createFileSchedulerStore`(改名是硬 breaking:消费方的 tsc 红 / 运行期 undefined 就是通知本身)。 */
+export declare function createFileSchedulerStore(path: string): SchedulerStore;
 /** Outcome of {@link mutateSchedulerStore}. `conflict_exhausted` = a concurrent writer kept changing the file
  *  faster than the bounded replays; nothing was written on that final attempt (earlier attempts never wrote). */
 export type SchedulerStoreMutation = {
@@ -53,20 +58,3 @@ export type SchedulerStoreMutation = {
 export declare function mutateSchedulerStore(path: string, fn: (records: SchedulerRecord[]) => SchedulerRecord[] | null, opts?: {
     retries?: number;
 }): SchedulerStoreMutation;
-/** [1057]① prompts contentDigest(node 绑定;browser-safe 纯层不带 crypto):
- *  canonical JSON(stableStringify 同姿势:键序稳定+深度护栏)全量 sha256,**非盐化**
- *  ([1050]② operator 对账位——center 产、server 透传、core manifest 归因三方可独立复算)。
- *  入参=下发形的 {sections, scenarioOverrides?}(packId/contentDigest 自身不入 hash)。 */
-export declare function promptsContentDigest(payload: {
-    sections: unknown;
-    scenarioOverrides?: unknown;
-}): {
-    contentDigest: string;
-    packId: string;
-    /** [1062]③ 顺带:逐 section 对 `text` 铸的 contentHash(与 core 1.315 校验语义同刻度=
-     *  sha256(text));元素无 string text 位=undefined。center 物化流程=先把这些写回
-     *  declaration.contentHash,再对含 hash 的终形铸整包 digest(本函数对入参原样铸,两步自洽)。 */
-    sectionHashes: Array<string | undefined>;
-};
-/** 逐 section 对账锚(core 1.315 `PromptTextDeclaration.contentHash` 同刻度):sha256(text)。 */
-export declare function sectionContentHash(text: string): string;

package/dist/scheduler-store-node.js

@@ -8,9 +8,8 @@
  */
 import { mkdirSync, readFileSync, writeFileSync, renameSync } from 'node:fs';
 import { dirname } from 'node:path';
-import { randomBytes, createHash } from 'node:crypto';
+import { randomBytes } from 'node:crypto';
 import { parseSchedulerStore, serializeSchedulerStore } from './scheduler-store.js';
-import { stableStringify } from './hash.js';
 /**
  * Load the durable store. A MISSING file (ENOENT) ⇒ `[]` (fail-soft, first-run/never-written case); any OTHER
  * read failure (EACCES/EIO/EISDIR/…) RETHROWS — only absence means "empty", not "unreadable for any reason"
@@ -39,8 +38,13 @@ export function saveSchedulerStore(path, records) {
     writeFileSync(tmp, serializeSchedulerStore(records), { mode: 0o600 });
     renameSync(tmp, path); // atomic over the target
 }
-/** A filesystem-backed {@link SchedulerStore} bound to a path (convenience for the daemon/backend constructors). */
-export function fileSchedulerStore(path) {
+/** A filesystem-backed {@link SchedulerStore} bound to a path (convenience for the daemon/backend constructors).
+ *
+ * 4.0.0 BREAKING 改名(S-571 B5,**零别名**):旧名 `fileSchedulerStore` 已删。它返回一只带 `load`/`save`
+ * 的**活对象** ⇒ 按本组工厂命名法(`build*` 出纯数据、`create*` 出活对象)该叫 `create*`;2.0.0 那次照人眼
+ * 改只改到了 `createSiblingResolver`,漏了这处 —— 现在由 `test/factory-naming-4.0.0.test.ts` 的门④ 机器看着。
+ * 消费方改调 `createFileSchedulerStore`(改名是硬 breaking:消费方的 tsc 红 / 运行期 undefined 就是通知本身)。 */
+export function createFileSchedulerStore(path) {
     return {
         load: () => loadSchedulerStore(path),
         save: (records) => saveSchedulerStore(path, records),
@@ -95,25 +99,3 @@ export function mutateSchedulerStore(path, fn, opts) {
         return { ok: true, records: next, retries: attempt };
     }
 }
-/** [1057]① prompts contentDigest(node 绑定;browser-safe 纯层不带 crypto):
- *  canonical JSON(stableStringify 同姿势:键序稳定+深度护栏)全量 sha256,**非盐化**
- *  ([1050]② operator 对账位——center 产、server 透传、core manifest 归因三方可独立复算)。
- *  入参=下发形的 {sections, scenarioOverrides?}(packId/contentDigest 自身不入 hash)。 */
-export function promptsContentDigest(payload) {
-    const canonical = stableStringify({
-        sections: payload.sections,
-        ...(payload.scenarioOverrides !== undefined ? { scenarioOverrides: payload.scenarioOverrides } : {}),
-    });
-    const hex = createHash('sha256').update(canonical, 'utf8').digest('hex');
-    const sectionHashes = Array.isArray(payload.sections)
-        ? payload.sections.map((s) => {
-            const t = s?.text;
-            return typeof t === 'string' ? sectionContentHash(t) : undefined;
-        })
-        : [];
-    return { contentDigest: `sha256:${hex}`, packId: `center:${hex.slice(0, 12)}`, sectionHashes };
-}
-/** 逐 section 对账锚(core 1.315 `PromptTextDeclaration.contentHash` 同刻度):sha256(text)。 */
-export function sectionContentHash(text) {
-    return `sha256:${createHash('sha256').update(text, 'utf8').digest('hex')}`;
-}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/settings-schema",
-  "version": "3.0.1",
+  "version": "5.0.0",
   "description": "Sema settings schema — pure config contract (zod domains + effective-config + roster resolution + ref-integrity + remoteExec) shared by sema-registry, sema-server, and the TOC desktop/CLI. One source of truth. (Renamed at 1.0.0 from @sema-agent/registry-core — name and docs only, no behavior change; note the range moves 0.19.0 -> 1.0.0, so a dependency must become ^1.0.0. The old names @sema-agent/registry-core <=0.19.0 and @sema-ai/registry-core remain published, frozen, for migration.)",
   "type": "module",
   "license": "BUSL-1.1",
@@ -121,6 +121,8 @@
     "test:watch": "vitest",
     "e2e": "node examples/toc-e2e.mjs",
     "drift:cc": "node scripts/extract-cc-hook-events.mjs",
+    "conformance:bless": "node scripts/gen-conformance.mjs",
+    "conformance:historical": "node scripts/conformance-historical.mjs",
     "prepare": "npm run build",
     "prepublishOnly": "npm run build && npm run test",
     "publish:npm": "npm publish --access public --@sema-agent:registry=https://registry.npmjs.org/ --\"//registry.npmjs.org/:_authToken=${NPM_TOKEN}\""