@sema-agent/settings-schema 1.2.0 → 1.3.0

package/CHANGELOG.md

@@ -6,6 +6,93 @@
 > `@sema-agent/registry-core`(更早还曾是 `@sema-ai/registry-core`)。本档 `0.19.0` 以下各节里的
 > 包名是**历史记录**,如实保留不追改。
 
+## 1.3.0 — hooks 域加员 `DirectoryAdded`(CC 2.1.219 新事件;`HooksConfig` 拒键病形修复)
+
+**`HOOK_EVENTS` 30 → 31:`POST_198_HOOK_EVENTS` **尾插** `DirectoryAdded`(1.2.0 三员声明序逐字节不动;重排 = BREAKING,
+免裁)。additive:既有 30 员的 matcher 字段 / owner / 输入形 / `hookSpecificOutput` 臂一字不动(FROZEN 1.2.0 全表字面量夹具钉,
+`test/hooks-directory-added-1.3.0.test.ts`,字面量独立誊自 bfbd140、非从现表派生——1.1.0/1.2.0 safety-merge-spec 夹具同律)。
+版号 minor = 加词(1.2.0 口径)。**
+
+### 病形(修前)
+
+`HooksConfig = z.record(HookEventName, …)` 键集**闭合**(设计如此:wire 上抓 typo)——用户 settings 里 `hooks.DirectoryAdded`
+(壳自 CC 2.1.219 起真会点亮的事件)在 1.2.0 下**整条** hooks 配置被拒(zod `Invalid enum value` at key);同时 `HookInput`
+union 无该臂、`HookEventName` 不收该词。壳认得、schema 不收——与 cli `hooksSchema218.test.ts` 建门帖所述「壳自己认得的
+输入形,壳自己的注册面不收」同形。
+
+### CC 真形(亲读镜像坐标,非按名推断)
+
+来源 = cli 树 `node_modules/@sema-agent/agent-types`(`@anthropic-ai/claude-agent-sdk@0.3.220` `sdk.d.ts` 的镜像,CC 2.1.220,
+与 0.3.219 逐字节同):
+
+- `hooks.d.ts:582-586` `DirectoryAddedHookInput = BaseHookInput & { hook_event_name:'DirectoryAdded'; directory:string;
+  source:'slash_command'|'register_repo_root' }`,`@since CC 2.1.219`(:574-575:目录经 `/add-dir` 或 repo-root 注册加入会话
+  工作集;cli `hooksConfigManager.ts:283-287` 文案:`directory` 为绝对路径)。
+- `hooks.d.ts:638` / `runtime.d.ts:111`:CC 序位于 `FileChanged` 与 `MessageDisplay` 之间;本包**尾插**——声明序非规范,
+  枚举当集合用(与 `MinTrust` 1.2.0 同律);夹具钉「1.2.0 三十员 = `HOOK_EVENTS` 逐字节前缀」。
+- `hooks.d.ts:14-17`:上游**无** `hookSpecificOutput` 臂——本版不加臂,测试钉「缺席」(非遗漏)。
+- **matcher 语义**:cli `src/utils/hooks.ts:1706-1760` `getMatchingHooks` 开关**无** `DirectoryAdded` 臂 → 落 `default` →
+  `matchQuery` 空 → 所有 matcher 组皆触发;`hooksConfigManager.ts` 该员亦无 `matcherMetadata` ⇒
+  `HOOK_EVENT_MATCHER_FIELD.DirectoryAdded = null`(与 CwdChanged / MessageDisplay 同族;entry 上写 `matcher` 仍是合法配置,
+  只是不被查阅)。
+- **owner = `shell`**(工作集在壳;`ENGINE_OWNED_HOOK_EVENTS` 9 员不动,`HOOK_EVENT_OWNER` 为派生表、自动含新员)。
+
+### API 形(全文)
+
+```ts
+export const POST_198_HOOK_EVENTS = ["CwdChanged", "FileChanged", "MessageDisplay", "DirectoryAdded"] as const; // 尾插
+export const DIRECTORY_ADDED_SOURCES = ["slash_command", "register_repo_root"] as const;
+export const DirectoryAddedHookInput = BaseHookInput.extend({
+  hook_event_name: z.literal("DirectoryAdded"),
+  directory: z.string(),
+  source: z.enum(DIRECTORY_ADDED_SOURCES),
+});
+export type DirectoryAddedHookInput = z.infer<typeof DirectoryAddedHookInput>;
+// HookInput union + 1 臂(尾);HOOK_EVENT_MATCHER_FIELD + 1 行(null);HookSpecificOutput 不动;HooksSlotSemantics 不动(非逐员表)
+```
+
+### 消费方可见(与 1.2.0 同一课:「表不动」≠「消费方零感知」)
+
+- **cli**(`package.json` 范围 `^1.2.0`,但 `package-lock.json:1261-1264` **钉 1.2.0**——`npm ci` 不会静默提到 1.3.0;
+  只有 `npm update` / 无锁重解析才命中):**运行时零影响**——cli `src/` 非测试文件对本包只 import `isAtLeast`
+  (`src/sema/settings/resolver.ts:28`),hook 符号零运行时消费(亲 grep)。提货影响全在常驻门
+  `src/types/hooksSchema218.test.ts`(以本包 `HOOK_EVENTS` 为 canonical 钉三面集合等式):亲读该门代码推断(**未实测**,
+  不动 cli 树)提货 1.3.0 后 **五条**红——**H2**(T1 缺 `DirectoryAdded`)/ **H6**(计数 30≠31)/ **H7**(字面量
+  `CANON.length === 30` 与差集 `=== 3`)/ **H8**(按 CANON 31 键铺满喂 initialize,`DirectoryAdded` 对 T1 的 partialRecord
+  是未知键 ⇒ 拒)/ **H10a**(`OLD_27 = CANON − 3` 亦含新员 ⇒ 同因拒);修法 = 该门自注「三面同动」:`coreSchemas.HOOK_EVENTS`
+  加员 + `HookInputSchema` 加臂 + H7 字面量改 31 / 4。其 :177-178 把「`DirectoryAdded` 该不该进 settings 域」记为候裁,
+  本版加员即回应该候裁项(cli 提货时表态);`coreTypes.HOOK_EVENTS`(31 员)与本版集合恰好相等。发布帖须 @cli 点名
+  (能力显式表态制)。
+- 持 `Record<HookEventName, …>` 字面量 / 对 `HookEventName` 穷举 `switch` 的消费方:升级即**编译错**(响亮,正是要的)。
+- 用 `HookEventName` / `HookInput` / `HooksConfig` 校验**外部**值的 1.2.0 消费方:收不下 `DirectoryAdded`(名词拒、整条
+  config 拒)——这正是本版修的病形;夹具钉住 1.2.0 行为供对照(frozen `z.record(z.enum(HOOK_EVENTS_1_2_0), …)` 拒、1.3.0 收)。
+- **server**(`package.json:58` **精确钉** `"1.2.0"`,无 caret——永不自动提货):亲读 `src/hooks/hook-runner.ts`——
+  `parseHooksConfig` 走 `HooksConfig.safeParse`(:200),`createTaskHooks` 按 `HOOK_EVENT_OWNER` 分流(:1179/:1185);提货后
+  wire 上 `settings.hooks.DirectoryAdded` 不再被拒,落 shell-owned 分支 = `debug("hook_events_shell_owned")` 记账不点亮不告警
+  (:1185-1188)——「配置合法但 owner 是壳」本就是既定语义(非本版新义)。server 无 `Record<HookEventName,…>` 穷举表、
+  无 30 计数钉(亲 grep src + test),提货零编译红零测试红(推断自 grep,提货批自证)。
+
+### 门
+
+- **红先**:修前 solo 跑 `test/hooks.test.ts` + `test/hooks-directory-added-1.3.0.test.ts` = **11 红**(新文件 8:集合/
+  `HooksConfig` 收键/`HookInput` 判别/导出符号/owner/matcher/前缀冻结/1.2.0 对照;`hooks.test.ts` 计数钉 3)+ `tsc --noEmit`
+  **10 错**(全在测试文件——`Record<HookEventName,…>` 无该键、union 收窄为 `never`);修后 34/34 绿、tsc 0 错。
+- **变异刀 4/4 红**(每刀后源文件复原逐字节一致):K1 `POST_198_HOOK_EVENTS` 去员 → vitest 8 红 + tsc 5 错(矩阵多余键 =
+  编译红,穷举表如约响);K2 输入字段 `directory`→`dir` → 判别钉 2 红 + tsc 1 错;K3 matcher `null`→`"directory"` → 1 红;
+  K4 重排到 CC 序(DirectoryAdded 前置 MessageDisplay)→ 前缀冻结钉 2 红。
+- **全门**:`npm run build` exit 0;`npm test` 40 文件 / 631 用例全过;`tsc --noEmit` exit 0;dist 亲验(`node -e` 加载
+  `dist/index.js`):`HOOK_EVENTS.length===31`、末员 `DirectoryAdded`、owner `shell`、matcher `null`、`HooksConfig` 收
+  `{DirectoryAdded:[…]}`;`dist/hooks.d.ts` 含 `DIRECTORY_ADDED_SOURCES` / `DirectoryAddedHookInput`(值+类型)。
+- README 无 hooks 员数句(模块清单未列 hooks 域),无需同步。
+- **codex 对抗复审 R1**(`adversarial-review`,工作树 diff):verdict needs-attention,**1 条 [high]** =「minor 发版必破
+  cli 消费方(`^1.2.0` 自动命中,契约门红),建议先落 cli 再发或改用 `^1.2.0` 选不中的版号」。处置:**不是代码缺陷,是发版
+  协同事实**(且是从本段 CHANGELOG 自述推出的)——实证如上:cli 锁文件钉 1.2.0、cli 运行时零 hook 消费、server 精确钉;
+  「破」的实体 = cli 常驻门(该门建门即自注「三面同动」),提货批修门是 cli 侧既定动作;发布走能力显式表态制 @cli。
+  「改版号避开 `^1.2.0`」= 升 major,与 1.2.0 段 codex R2 严格 semver 异议同类,当时记为**候裁项**——本版沿用 minor 口径,
+  异议原样留档供裁。另:codex 沙箱内 `npm run typecheck && npm test` exit 1——**同命令标准环境复跑 exit 0**(typecheck 0
+  错 + 40 文件 631 用例),归因 codex `--sandbox read-only` 下 vitest 写 `node_modules/.vite/vitest` 缓存失败(目录亲验存在;
+  归因为假设,复跑绿为实测)。
+
 ## 1.2.0 — `MinTrust` 排序原语 + `task` 员([5796] 序题 → [5805] schema 认领 / [5807] cli 表态三点)
 
 **新导出 `trustRank(layer)` / `isAtLeast(layer, minTrust)`——规范信任阶梯的**单源**(v2-design §1:29 逐字);

package/dist/hooks.d.ts

@@ -2,10 +2,10 @@
  * `hooks` — the CC-parity hooks contract (incl. stop attribution).
  *
  * ONE definition of the FULL hook-event set — 27 CC 2.1.198 events (REF: the `jP` array in
- * claude-cli-2.1.198.pretty.js) + 3 post-198 events the shell already ships (CwdChanged / FileChanged /
- * MessageDisplay). Per the product ruling: the CONTRACT is the full set from day one; the engine
- * hook-runner (service) and the shell light events up in PHASES — adding an event later is pure
- * implementation, never a schema change.
+ * claude-cli-2.1.198.pretty.js) + 4 post-198 events the shell already ships (CwdChanged / FileChanged /
+ * MessageDisplay, and DirectoryAdded from CC 2.1.219). Per the product ruling: the CONTRACT is the full set
+ * from day one; the engine hook-runner (service) and the shell light events up in PHASES — adding an event
+ * later is pure implementation, never a schema change.
  *
  * CONSUMERS
  * - service (sema-server): `TaskRequest.settings.hooks` wire face = `HooksConfig` below; the worker-side
@@ -26,11 +26,15 @@
 import { z } from "zod";
 /** CC 2.1.198 full hook-event set (jP array) — 27 events. Order matches the shell's HOOK_EVENTS. */
 export declare const CC_198_HOOK_EVENTS: readonly ["PreToolUse", "PostToolUse", "PostToolUseFailure", "PostToolBatch", "Notification", "UserPromptSubmit", "UserPromptExpansion", "SessionStart", "SessionEnd", "Stop", "StopFailure", "SubagentStart", "SubagentStop", "PreCompact", "PostCompact", "PermissionRequest", "PermissionDenied", "Setup", "TeammateIdle", "TaskCreated", "TaskCompleted", "Elicitation", "ElicitationResult", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "InstructionsLoaded"];
-/** Post-CC-2.1.198 additions the shell already ships (sema superset; CC added them after 198). */
-export declare const POST_198_HOOK_EVENTS: readonly ["CwdChanged", "FileChanged", "MessageDisplay"];
-/** The full 30-event contract set = CC 198's 27 + the 3 post-198 shell events. */
-export declare const HOOK_EVENTS: readonly ["PreToolUse", "PostToolUse", "PostToolUseFailure", "PostToolBatch", "Notification", "UserPromptSubmit", "UserPromptExpansion", "SessionStart", "SessionEnd", "Stop", "StopFailure", "SubagentStart", "SubagentStop", "PreCompact", "PostCompact", "PermissionRequest", "PermissionDenied", "Setup", "TeammateIdle", "TaskCreated", "TaskCompleted", "Elicitation", "ElicitationResult", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "InstructionsLoaded", "CwdChanged", "FileChanged", "MessageDisplay"];
-export declare const HookEventName: z.ZodEnum<["PreToolUse", "PostToolUse", "PostToolUseFailure", "PostToolBatch", "Notification", "UserPromptSubmit", "UserPromptExpansion", "SessionStart", "SessionEnd", "Stop", "StopFailure", "SubagentStart", "SubagentStop", "PreCompact", "PostCompact", "PermissionRequest", "PermissionDenied", "Setup", "TeammateIdle", "TaskCreated", "TaskCompleted", "Elicitation", "ElicitationResult", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "InstructionsLoaded", "CwdChanged", "FileChanged", "MessageDisplay"]>;
+/**
+ * Post-CC-2.1.198 additions the shell already ships (sema superset; CC added them after 198).
+ * APPEND-ONLY: new members go at the tail (1.3.0 `DirectoryAdded`, CC 2.1.219 — CC's own tuple places it
+ * between FileChanged and MessageDisplay; the declaration order here is not normative, the enum is a set).
+ */
+export declare const POST_198_HOOK_EVENTS: readonly ["CwdChanged", "FileChanged", "MessageDisplay", "DirectoryAdded"];
+/** The full 31-event contract set = CC 198's 27 + the 4 post-198 shell events. */
+export declare const HOOK_EVENTS: readonly ["PreToolUse", "PostToolUse", "PostToolUseFailure", "PostToolBatch", "Notification", "UserPromptSubmit", "UserPromptExpansion", "SessionStart", "SessionEnd", "Stop", "StopFailure", "SubagentStart", "SubagentStop", "PreCompact", "PostCompact", "PermissionRequest", "PermissionDenied", "Setup", "TeammateIdle", "TaskCreated", "TaskCompleted", "Elicitation", "ElicitationResult", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "InstructionsLoaded", "CwdChanged", "FileChanged", "MessageDisplay", "DirectoryAdded"];
+export declare const HookEventName: z.ZodEnum<["PreToolUse", "PostToolUse", "PostToolUseFailure", "PostToolBatch", "Notification", "UserPromptSubmit", "UserPromptExpansion", "SessionStart", "SessionEnd", "Stop", "StopFailure", "SubagentStart", "SubagentStop", "PreCompact", "PostCompact", "PermissionRequest", "PermissionDenied", "Setup", "TeammateIdle", "TaskCreated", "TaskCompleted", "Elicitation", "ElicitationResult", "ConfigChange", "WorktreeCreate", "WorktreeRemove", "InstructionsLoaded", "CwdChanged", "FileChanged", "MessageDisplay", "DirectoryAdded"]>;
 export type HookEventName = z.infer<typeof HookEventName>;
 export declare const HookOwner: z.ZodEnum<["engine", "shell"]>;
 export type HookOwner = z.infer<typeof HookOwner>;
@@ -1586,7 +1590,48 @@ export declare const MessageDisplayHookInput: z.ZodObject<{
     permission_mode?: string | undefined;
     agent_id?: string | undefined;
 }>;
-/** Any hook input — discriminated on `hook_event_name` (all 30 events). */
+/** How a directory joined the session working set: the `/add-dir` slash command or repo-root registration. */
+export declare const DIRECTORY_ADDED_SOURCES: readonly ["slash_command", "register_repo_root"];
+/**
+ * Fired after a directory joins the session's working set (CC 2.1.219; agent-types hooks.d.ts:582-586 —
+ * `directory` is the absolute path). Shell-owned; matcher ignored; no hookSpecificOutput arm upstream.
+ */
+export declare const DirectoryAddedHookInput: z.ZodObject<{
+    session_id: z.ZodString;
+    transcript_path: z.ZodString;
+    cwd: z.ZodString;
+    permission_mode: z.ZodOptional<z.ZodString>;
+    /** Subagent id — present only when the hook fires from within a subagent. */
+    agent_id: z.ZodOptional<z.ZodString>;
+    /** Agent type name (e.g. "general-purpose") — present alongside agent_id, or on --agent main threads. */
+    agent_type: z.ZodOptional<z.ZodString>;
+} & {
+    hook_event_name: z.ZodLiteral<"DirectoryAdded">;
+    directory: z.ZodString;
+    source: z.ZodEnum<["slash_command", "register_repo_root"]>;
+}, "strip", z.ZodTypeAny, {
+    source: "slash_command" | "register_repo_root";
+    session_id: string;
+    transcript_path: string;
+    cwd: string;
+    hook_event_name: "DirectoryAdded";
+    directory: string;
+    agent_type?: string | undefined;
+    permission_mode?: string | undefined;
+    agent_id?: string | undefined;
+}, {
+    source: "slash_command" | "register_repo_root";
+    session_id: string;
+    transcript_path: string;
+    cwd: string;
+    hook_event_name: "DirectoryAdded";
+    directory: string;
+    agent_type?: string | undefined;
+    permission_mode?: string | undefined;
+    agent_id?: string | undefined;
+}>;
+export type DirectoryAddedHookInput = z.infer<typeof DirectoryAddedHookInput>;
+/** Any hook input — discriminated on `hook_event_name` (all 31 events). */
 export declare const HookInput: z.ZodDiscriminatedUnion<"hook_event_name", [z.ZodObject<{
     session_id: z.ZodString;
     transcript_path: z.ZodString;
@@ -2884,6 +2929,39 @@ export declare const HookInput: z.ZodDiscriminatedUnion<"hook_event_name", [z.Zo
     agent_type?: string | undefined;
     permission_mode?: string | undefined;
     agent_id?: string | undefined;
+}>, z.ZodObject<{
+    session_id: z.ZodString;
+    transcript_path: z.ZodString;
+    cwd: z.ZodString;
+    permission_mode: z.ZodOptional<z.ZodString>;
+    /** Subagent id — present only when the hook fires from within a subagent. */
+    agent_id: z.ZodOptional<z.ZodString>;
+    /** Agent type name (e.g. "general-purpose") — present alongside agent_id, or on --agent main threads. */
+    agent_type: z.ZodOptional<z.ZodString>;
+} & {
+    hook_event_name: z.ZodLiteral<"DirectoryAdded">;
+    directory: z.ZodString;
+    source: z.ZodEnum<["slash_command", "register_repo_root"]>;
+}, "strip", z.ZodTypeAny, {
+    source: "slash_command" | "register_repo_root";
+    session_id: string;
+    transcript_path: string;
+    cwd: string;
+    hook_event_name: "DirectoryAdded";
+    directory: string;
+    agent_type?: string | undefined;
+    permission_mode?: string | undefined;
+    agent_id?: string | undefined;
+}, {
+    source: "slash_command" | "register_repo_root";
+    session_id: string;
+    transcript_path: string;
+    cwd: string;
+    hook_event_name: "DirectoryAdded";
+    directory: string;
+    agent_type?: string | undefined;
+    permission_mode?: string | undefined;
+    agent_id?: string | undefined;
 }>]>;
 export type HookInput = z.infer<typeof HookInput>;
 /** Legacy top-level decision (CC): "approve" ≈ allow, "block" feeds `reason` back to the model. */
@@ -5442,7 +5520,7 @@ export declare const HookMatcherEntry: z.ZodObject<{
 export type HookMatcherEntry = z.infer<typeof HookMatcherEntry>;
 /**
  * The hooks config record — the shape `TaskRequest.settings.hooks` carries on the wire and the shell
- * reads from settings JSON: `{ [eventName]: [{ matcher?, hooks: [...] }] }`. Keys limited to the 30
+ * reads from settings JSON: `{ [eventName]: [{ matcher?, hooks: [...] }] }`. Keys limited to the 31
  * contract events (an unknown event name fails parse — catch typos at the wire); all keys optional.
  */
 export type HooksConfig = Partial<Record<HookEventName, HookMatcherEntry[]>>;

package/dist/hooks.js

@@ -2,10 +2,10 @@
  * `hooks` — the CC-parity hooks contract (incl. stop attribution).
  *
  * ONE definition of the FULL hook-event set — 27 CC 2.1.198 events (REF: the `jP` array in
- * claude-cli-2.1.198.pretty.js) + 3 post-198 events the shell already ships (CwdChanged / FileChanged /
- * MessageDisplay). Per the product ruling: the CONTRACT is the full set from day one; the engine
- * hook-runner (service) and the shell light events up in PHASES — adding an event later is pure
- * implementation, never a schema change.
+ * claude-cli-2.1.198.pretty.js) + 4 post-198 events the shell already ships (CwdChanged / FileChanged /
+ * MessageDisplay, and DirectoryAdded from CC 2.1.219). Per the product ruling: the CONTRACT is the full set
+ * from day one; the engine hook-runner (service) and the shell light events up in PHASES — adding an event
+ * later is pure implementation, never a schema change.
  *
  * CONSUMERS
  * - service (sema-server): `TaskRequest.settings.hooks` wire face = `HooksConfig` below; the worker-side
@@ -55,9 +55,13 @@ export const CC_198_HOOK_EVENTS = [
     "WorktreeRemove",
     "InstructionsLoaded",
 ];
-/** Post-CC-2.1.198 additions the shell already ships (sema superset; CC added them after 198). */
-export const POST_198_HOOK_EVENTS = ["CwdChanged", "FileChanged", "MessageDisplay"];
-/** The full 30-event contract set = CC 198's 27 + the 3 post-198 shell events. */
+/**
+ * Post-CC-2.1.198 additions the shell already ships (sema superset; CC added them after 198).
+ * APPEND-ONLY: new members go at the tail (1.3.0 `DirectoryAdded`, CC 2.1.219 — CC's own tuple places it
+ * between FileChanged and MessageDisplay; the declaration order here is not normative, the enum is a set).
+ */
+export const POST_198_HOOK_EVENTS = ["CwdChanged", "FileChanged", "MessageDisplay", "DirectoryAdded"];
+/** The full 31-event contract set = CC 198's 27 + the 4 post-198 shell events. */
 export const HOOK_EVENTS = [...CC_198_HOOK_EVENTS, ...POST_198_HOOK_EVENTS];
 export const HookEventName = z.enum(HOOK_EVENTS);
 // ── ownership (owner-single) ─────────────────────────────────────────────────────────────────────
@@ -119,6 +123,7 @@ export const HOOK_EVENT_MATCHER_FIELD = {
     CwdChanged: null,
     FileChanged: "file_path", // matched against basename(file_path)
     MessageDisplay: null,
+    DirectoryAdded: null, // the shell's getMatchingHooks switch has no arm for it → every entry matches (CwdChanged family)
 };
 // ── shared enums (CC-verbatim) ─────────────────────────────────────────────────────────────────────────
 export const PermissionBehavior = z.enum(["allow", "deny", "ask"]);
@@ -382,7 +387,18 @@ export const MessageDisplayHookInput = BaseHookInput.extend({
     /** Newly completed lines since the prior flush (final flush may end mid-line / be empty). */
     delta: z.string(),
 });
-/** Any hook input — discriminated on `hook_event_name` (all 30 events). */
+/** How a directory joined the session working set: the `/add-dir` slash command or repo-root registration. */
+export const DIRECTORY_ADDED_SOURCES = ["slash_command", "register_repo_root"];
+/**
+ * Fired after a directory joins the session's working set (CC 2.1.219; agent-types hooks.d.ts:582-586 —
+ * `directory` is the absolute path). Shell-owned; matcher ignored; no hookSpecificOutput arm upstream.
+ */
+export const DirectoryAddedHookInput = BaseHookInput.extend({
+    hook_event_name: z.literal("DirectoryAdded"),
+    directory: z.string(),
+    source: z.enum(DIRECTORY_ADDED_SOURCES),
+});
+/** Any hook input — discriminated on `hook_event_name` (all 31 events). */
 export const HookInput = z.discriminatedUnion("hook_event_name", [
     PreToolUseHookInput,
     PostToolUseHookInput,
@@ -414,6 +430,7 @@ export const HookInput = z.discriminatedUnion("hook_event_name", [
     CwdChangedHookInput,
     FileChangedHookInput,
     MessageDisplayHookInput,
+    DirectoryAddedHookInput,
 ]);
 // ── hook output / decision semantics (CC-verbatim, with the service-receipt design points pinned) ────────
 //

package/dist/index.js

@@ -14,7 +14,7 @@ export * from "./cross-domain.js"; // pure half only (no fleet placement)
 export * from "./remote-exec.js";
 export * from "./safety-merge-spec.js"; // #14 per-category safety merge-spec (settings resolver authority)
 export * from "./scheduler-store.js"; // R7 self-wake scheduler store CONTRACT (pure: type + parse/serialize + SchedulerStore interface; fs binding in ./node)
-export * from "./hooks.js"; // CC-parity hooks contract (30-event set + owner map + per-event input/output shapes + HooksConfig) & stop attribution (stoppedBy) — pure/browser-safe
+export * from "./hooks.js"; // CC-parity hooks contract (31-event set + owner map + per-event input/output shapes + HooksConfig) & stop attribution (stoppedBy) — pure/browser-safe
 export * from "./fleet.js"; // scheduling/fleet contract (drain protocol · instance discovery · dispatch policy · quota lease · usage report · quota reset event) — CONTROL-PLANE-SCHEDULING-DESIGN, pure/browser-safe
 export * from "./migrate.js"; // 0.5→0.6 migration tools (hosts grandfathering + worker.model→catalog migration PLAN — report/draft only, E1; EXPERT-REDESIGN §2-2/§3), pure/browser-safe
 export * from "./api/auth.js"; // /api/v1/auth/* wire contract (RFC 8628 device flow + rotating refresh + logout + approve) — REGISTRY-REBUILD-DESIGN §2, M1 shipped shapes frozen, pure/browser-safe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/settings-schema",
-  "version": "1.2.0",
+  "version": "1.3.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",