@aitne/daemon 0.1.7 → 0.1.9

package/dist/core/browser-history/research-events.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Event factories for browser-history research process keys
+ * (BROWSER_HISTORY_INTEGRATION_PLAN §10.6 / §5.F1).
+ *
+ * Three process keys flow through this module:
+ *   - routine.research_cluster_update   — nightly journal append
+ *   - routine.research_dispatch         — !research accept <slug>
+ *   - routine.research_wiki_summary     — !research wiki <slug>
+ *
+ * Each event is shaped after the wiki-dispatcher pattern
+ * (`packages/daemon/src/core/wiki/dispatcher.ts`) so the EventBus's
+ * generic routing path picks them up: `event.type` IS the process key,
+ * `event.data.slug` carries the cluster identifier, and
+ * `event.data.reply_target` carries the originating DM routing tuple
+ * when a bang command minted the event (so the agent's DM lands back
+ * on the platform the user typed `!research accept` on, not a fan-out
+ * to every connected destination).
+ *
+ * The factory is pure — no DB, no side effects. Callers (bang command
+ * handler, API route) construct the event, push it onto the EventBus,
+ * and the dispatcher resolves backend / model / max_turns from
+ * `process_backend_config`.
+ */
+import { EventPriority, type Event } from "@aitne/shared";
+export declare const RESEARCH_PROCESS_KEYS: readonly ["routine.research_cluster_update", "routine.research_offer_dm", "routine.research_dispatch", "routine.research_wiki_summary"];
+export type ResearchProcessKey = (typeof RESEARCH_PROCESS_KEYS)[number];
+export declare function isResearchProcessKey(value: string): value is ResearchProcessKey;
+export interface ResearchCommandEventInput {
+    processKey: ResearchProcessKey;
+    slug: string;
+    /** Originating DM, if any, for reply routing. */
+    sourceEvent?: Event;
+    /** Extra event payload (for cluster_update: optional `displayName`). */
+    data?: Record<string, unknown>;
+    priority?: EventPriority;
+}
+export declare function createResearchCommandEvent(input: ResearchCommandEventInput): Event;

package/dist/core/browser-history/research-events.js

@@ -0,0 +1,70 @@
+/**
+ * Event factories for browser-history research process keys
+ * (BROWSER_HISTORY_INTEGRATION_PLAN §10.6 / §5.F1).
+ *
+ * Three process keys flow through this module:
+ *   - routine.research_cluster_update   — nightly journal append
+ *   - routine.research_dispatch         — !research accept <slug>
+ *   - routine.research_wiki_summary     — !research wiki <slug>
+ *
+ * Each event is shaped after the wiki-dispatcher pattern
+ * (`packages/daemon/src/core/wiki/dispatcher.ts`) so the EventBus's
+ * generic routing path picks them up: `event.type` IS the process key,
+ * `event.data.slug` carries the cluster identifier, and
+ * `event.data.reply_target` carries the originating DM routing tuple
+ * when a bang command minted the event (so the agent's DM lands back
+ * on the platform the user typed `!research accept` on, not a fan-out
+ * to every connected destination).
+ *
+ * The factory is pure — no DB, no side effects. Callers (bang command
+ * handler, API route) construct the event, push it onto the EventBus,
+ * and the dispatcher resolves backend / model / max_turns from
+ * `process_backend_config`.
+ */
+import { createEvent, EventPriority, isMessageEvent, } from "@aitne/shared";
+export const RESEARCH_PROCESS_KEYS = [
+    "routine.research_cluster_update",
+    "routine.research_offer_dm",
+    "routine.research_dispatch",
+    "routine.research_wiki_summary",
+];
+export function isResearchProcessKey(value) {
+    return RESEARCH_PROCESS_KEYS.includes(value);
+}
+export function createResearchCommandEvent(input) {
+    // Mirror the wiki dispatcher's data-merge order: caller data first,
+    // daemon fields last, so a caller cannot hijack routing by passing
+    // `reply_target` / `slug` in `data`. The factory's typed `slug`
+    // wins over any same-key value in `data`.
+    const replyTarget = input.sourceEvent && isMessageEvent(input.sourceEvent)
+        ? {
+            platform: input.sourceEvent.platform,
+            channel: input.sourceEvent.channel,
+            threadId: input.sourceEvent.threadId,
+            sender: input.sourceEvent.sender,
+        }
+        : undefined;
+    // `RoutineEvent.routine` is the documented contract on every
+    // `routine.*` event (see RoutineEvent in @aitne/shared types.ts). The
+    // dispatcher's `isRoutineEvent` branch reads it; omitting the field
+    // and relying on the fall-through `executeDefault` would make the
+    // `event as RoutineEvent` cast in the dispatcher's executeDefault
+    // branch lie about the runtime shape. Strip the `routine.` prefix to
+    // match the canonical morning/evening/weekly entries.
+    const routineKey = input.processKey.slice("routine.".length);
+    const base = createEvent({
+        type: input.processKey,
+        source: input.sourceEvent ? "browser_history.bang" : "browser_history.cron",
+        priority: input.priority ?? EventPriority.NORMAL,
+        data: {
+            ...(input.data ?? {}),
+            slug: input.slug,
+            ...(input.sourceEvent
+                ? { parent_correlation_id: input.sourceEvent.correlationId }
+                : {}),
+            ...(replyTarget ? { reply_target: replyTarget } : {}),
+        },
+    });
+    const event = { ...base, routine: routineKey };
+    return event;
+}

package/dist/core/channel-timeline.d.ts

@@ -1,7 +1,24 @@
 import type Database from "better-sqlite3";
 import type { AgentConfig } from "../config.js";
-export declare const PROACTIVE_FORWARD_TYPES: readonly ["proactive_forward", "proactive_forward_batched"];
+export declare const PROACTIVE_FORWARD_TYPES: readonly ["proactive_forward", "proactive_forward_batched", "scheduled_dm"];
 export type ProactiveForwardType = (typeof PROACTIVE_FORWARD_TYPES)[number];
+/**
+ * Render-side suffix that goes after the role tag in the assembled
+ * `<conversation_history>` line and the cross-session
+ * "## Previous conversation in this thread" line. Centralised so the
+ * two render sites stay in lock-step when a new forward type is added.
+ *
+ * - `proactive_forward` / `proactive_forward_batched` →
+ *   "(forwarded from autonomous run)" — the row was emitted by an
+ *   autonomous run that the user did not directly trigger.
+ * - `scheduled_dm` → "(scheduled DM dispatched)" — the row is the
+ *   pre-composed body of a `/api/schedule/dm` request the user (or an
+ *   earlier agent turn) booked ahead of time. We deliberately do NOT
+ *   embed the dispatch timestamp here: every line already carries the
+ *   `[timestamp]` prefix added by the caller, so a second timestamp
+ *   in the suffix would just duplicate that information.
+ */
+export declare function formatForwardSuffix(metadata: Record<string, unknown>): string;
 export interface DeliveryRow {
     platform: string;
     channel: string;
@@ -25,4 +42,3 @@ export declare function recordProactiveForwardDeliveries(params: {
     originSessionIds?: Array<number | null | undefined>;
     notificationType: ProactiveForwardType;
 }): ProactiveForwardRecordResult;
-//# sourceMappingURL=channel-timeline.d.ts.map

package/dist/core/channel-timeline.js

@@ -4,7 +4,42 @@ import { findOrCreateActiveChannelSession } from "./session-manager.js";
 export const PROACTIVE_FORWARD_TYPES = [
     "proactive_forward",
     "proactive_forward_batched",
+    // DM-HISTORY-CONTINUITY-FIX H-1 — scheduled DMs dispatched by
+    // `scheduler.handleDirectDm` are recorded into `messages` via the
+    // shared channel-timeline path so the DM agent sees its own
+    // pre-composed sends in `<conversation_history>` and the cross-
+    // session bridge. Without this type the message would land in
+    // `notification_log` only and the user's follow-up reply would
+    // have nothing to anchor to.
+    "scheduled_dm",
 ];
+/**
+ * Render-side suffix that goes after the role tag in the assembled
+ * `<conversation_history>` line and the cross-session
+ * "## Previous conversation in this thread" line. Centralised so the
+ * two render sites stay in lock-step when a new forward type is added.
+ *
+ * - `proactive_forward` / `proactive_forward_batched` →
+ *   "(forwarded from autonomous run)" — the row was emitted by an
+ *   autonomous run that the user did not directly trigger.
+ * - `scheduled_dm` → "(scheduled DM dispatched)" — the row is the
+ *   pre-composed body of a `/api/schedule/dm` request the user (or an
+ *   earlier agent turn) booked ahead of time. We deliberately do NOT
+ *   embed the dispatch timestamp here: every line already carries the
+ *   `[timestamp]` prefix added by the caller, so a second timestamp
+ *   in the suffix would just duplicate that information.
+ */
+export function formatForwardSuffix(metadata) {
+    switch (getProactiveForwardType(metadata)) {
+        case "scheduled_dm":
+            return " (scheduled DM dispatched)";
+        case "proactive_forward":
+        case "proactive_forward_batched":
+            return " (forwarded from autonomous run)";
+        default:
+            return "";
+    }
+}
 export function parseMessageMetadata(raw) {
     if (raw && typeof raw === "object" && !Array.isArray(raw)) {
         return raw;
@@ -48,7 +83,16 @@ export function recordProactiveForwardDeliveries(params) {
     const recorder = new MessageRecorder(params.db);
     const dispatchIds = dedupeStrings(params.dispatchIds ?? (params.dispatchId ? [params.dispatchId] : []));
     const originSessionIds = dedupeNumbers(params.originSessionIds ?? []);
+    // Single-dispatch types carry the dispatch_id on the indexed column
+    // (`idx_messages_dispatch ... WHERE notification_dispatch_id IS NOT
+    // NULL`) so the row is reachable via the same fast-lookup path as
+    // notification_log. `proactive_forward_batched` is excluded because
+    // the row aggregates N origin dispatches and no single id is
+    // authoritative — the full set lives in `metadata.dispatchIds`.
+    // `scheduled_dm` IS single-dispatch (one dispatchId per
+    // `handleDirectDm` call) so it joins `proactive_forward` on this rule.
     const notificationDispatchId = params.notificationType === "proactive_forward"
+        || params.notificationType === "scheduled_dm"
         ? params.dispatchId ?? null
         : null;
     const metadata = {
@@ -114,4 +158,3 @@ function dedupeNumbers(values) {
         ...new Set(values.filter((value) => typeof value === "number" && Number.isInteger(value) && value > 0)),
     ];
 }
-//# sourceMappingURL=channel-timeline.js.map

package/dist/core/character-block.d.ts

@@ -34,4 +34,3 @@ export declare function buildCharacterBlock(character: string): string | null;
  * relies on to avoid thrashing active session files.
  */
 export declare function applyCharacterBlockRewrite(content: string, character: string): string;
-//# sourceMappingURL=character-block.d.ts.map

package/dist/core/character-block.js

@@ -159,4 +159,3 @@ function findFirstSectionHeading(content) {
     const idx = content.indexOf("\n## ");
     return idx < 0 ? -1 : idx + 1;
 }
-//# sourceMappingURL=character-block.js.map

package/dist/core/context/activity-sources.d.ts

@@ -3,12 +3,12 @@ import type Database from "better-sqlite3";
  * Activity-source enumeration (docs/design/21-management-registry-and-
  * entities.md §9.6). Lifted out of `activity-view-runner.ts` so the
  * dashboard can consume the same union the runner renders into
- * `_activity/<source>.md` (followups doc Issue 3).
+ * `state/activity/<source>.md` (followups doc Issue 3).
  *
  * The "active source set" is the union of three projections:
  *
  *   1. `managed_tasks.app_normalized` — the registered fetches (Section
- *      B of `rules/management.md`).
+ *      B of `policies/management.md`).
  *   2. `entity_source_keys.source_key` — every L2 entity file that
  *      mentions a source key, joined to the entity's date / sync window.
  *   3. `agent_actions.detail->>app_normalized` — recent management_task
@@ -19,7 +19,7 @@ import type Database from "better-sqlite3";
  *   - `active`  — there is a row in `managed_tasks` for this normalized
  *                 form (Settings → Management can edit it).
  *   - `stopped` — the source appears only in (2) or (3); typically a
- *                 recently stopped task whose `_activity/<source>.md`
+ *                 recently stopped task whose `state/activity/<source>.md`
  *                 file is still on disk for the 90-day window. The
  *                 dashboard's Activity tab keeps showing it; the
  *                 Settings → Management page does not (it only edits
@@ -34,4 +34,3 @@ export interface ActivitySourceRef {
     status: "active" | "stopped";
 }
 export declare function enumerateActivitySources(db: Database.Database, cutoffDate: string): ActivitySourceRef[];
-//# sourceMappingURL=activity-sources.d.ts.map

package/dist/core/context/activity-sources.js

@@ -66,4 +66,3 @@ export function enumerateActivitySources(db, cutoffDate) {
     }))
         .sort((a, b) => a.normalized.localeCompare(b.normalized));
 }
-//# sourceMappingURL=activity-sources.js.map

package/dist/core/context/activity-view-reconciler.d.ts

@@ -80,7 +80,7 @@ export interface ActivitySnapshot {
 export declare function activityFileSlugFor(source: string): string | null;
 /**
  * Relative path under `<contextDir>` for the activity file. Matches
- * the §9.6 layout `_activity/<source>.md`. The leading underscore is
+ * the §9.6 layout `state/activity/<source>.md`. The leading underscore is
  * the convention for auto-generated views (same as `_index.md`).
  */
 export declare function relativeActivityPath(slug: string): string;
@@ -107,4 +107,3 @@ export declare function sortRecentlyChangedRows(rows: readonly RecentlyChangedIn
  * deterministically.
  */
 export declare function windowCutoffDate(now: Date, windowDays: number): string;
-//# sourceMappingURL=activity-view-reconciler.d.ts.map

package/dist/core/context/activity-view-reconciler.js

@@ -1,7 +1,7 @@
 import { normalizeAppLabel } from "@aitne/shared";
 /**
  * Activity-view reconciler — pure render + snapshot helpers for
- * `<contextDir>/_activity/<source>.md`
+ * `<contextDir>/state/activity/<source>.md`
  * (docs/design/21-management-registry-and-entities.md §7.2 / §9.6).
  *
  * Inputs:
@@ -11,7 +11,7 @@ import { normalizeAppLabel } from "@aitne/shared";
  *     "Recently changed" section.
  *
  * Output is a chronological per-source view; the LLM's query path
- * (§7.5) reads `_activity/<source>.md` for the date, then follows the
+ * (§7.5) reads `state/activity/<source>.md` for the date, then follows the
  * link into the entity file. The activity file is short on details
  * (entity title + per-entity source metadata + a managed-task tag) so
  * the prompt-injection budget stays modest even with hundreds of
@@ -50,11 +50,11 @@ export function activityFileSlugFor(source) {
 }
 /**
  * Relative path under `<contextDir>` for the activity file. Matches
- * the §9.6 layout `_activity/<source>.md`. The leading underscore is
+ * the §9.6 layout `state/activity/<source>.md`. The leading underscore is
  * the convention for auto-generated views (same as `_index.md`).
  */
 export function relativeActivityPath(slug) {
-    return `_activity/${slug}.md`;
+    return `state/activity/${slug}.md`;
 }
 // ── Render ────────────────────────────────────────────────────────────────
 /**
@@ -160,11 +160,12 @@ function formatRecentlyChanged(row) {
 }
 function formatEntity(entity) {
     const head = entity.timeRange ? `${entity.timeRange} ` : "";
-    // The activity file lives at `_activity/<slug>.md`; entity files
-    // live at `<domain>/<type-plural>/<slug>.md`. From the activity
-    // file's perspective an entity at `work/meetings/foo.md` is at
-    // `../work/meetings/foo.md`.
-    const link = `../${entity.entityRelativePath}`;
+    // After CONTEXT_VAULT_REDESIGN the activity file lives at
+    // `state/activity/<slug>.md` and entity files live at
+    // `knowledge/entities/<domain>/<type-plural>/<slug>.md`. From the
+    // activity file's perspective both trees are siblings under the vault
+    // root; the relative link climbs two levels first.
+    const link = `../../${entity.entityRelativePath}`;
     const title = `[${escapeMd(entity.title)}](${link})`;
     const tail = formatEntityTail(entity);
     return `${head}${title}${tail}`;
@@ -249,4 +250,3 @@ export function windowCutoffDate(now, windowDays) {
     const cutoff = new Date(now.getTime() - windowDays * 86400_000);
     return cutoff.toISOString().slice(0, 10);
 }
-//# sourceMappingURL=activity-view-reconciler.js.map

package/dist/core/context/activity-view-runner.d.ts

@@ -35,4 +35,3 @@ export interface RunActivityViewReconcilerOptions {
  *   - `refreshedMtime`  → number of files that already matched on disk
  */
 export declare function runActivityViewReconciler(opts: RunActivityViewReconcilerOptions): Promise<ReconcilerRunRecord>;
-//# sourceMappingURL=activity-view-runner.d.ts.map

package/dist/core/context/activity-view-runner.js

@@ -9,7 +9,8 @@ import { ACTIVITY_VIEW_WINDOW_DAYS, activityFileSlugFor, relativeActivityPath, r
 const logger = createLogger("activity-view-reconciler");
 /** Runtime-state key for the activity-view reconciler's last run record. */
 export const ACTIVITY_VIEW_RECONCILER_LAST_RUN_KEY = "reconciler.activity_view.last_run";
-const ACTIVITY_DIR = "_activity";
+// CONTEXT_VAULT_REDESIGN: activity views live under state/activity/.
+const ACTIVITY_DIR = "state/activity";
 let runnerMutex = Promise.resolve();
 /**
  * Drive one pass of the activity-view reconciler:
@@ -388,8 +389,16 @@ function writeWithSnapshot(opts, absolutePath, relativePath, content, previousCo
             logger.warn({ err, file: relativePath }, "Failed to snapshot prior content before activity-view write");
         }
     }
-    writeFileAtomically(absolutePath, content);
+    // Mark before the rename so FS-watch consumers attribute the resulting
+    // event to the agent. Roll back on failure (C2).
     opts.writeTracker?.markWriting(absolutePath, content);
+    try {
+        writeFileAtomically(absolutePath, content);
+    }
+    catch (writeErr) {
+        opts.writeTracker?.unmark(absolutePath);
+        throw writeErr;
+    }
 }
 function persistRunRecord(db, record) {
     try {
@@ -399,4 +408,3 @@ function persistRunRecord(db, record) {
         logger.warn({ err, record }, "Activity-view reconciler run record persistence failed");
     }
 }
-//# sourceMappingURL=activity-view-runner.js.map

package/dist/core/context/default-schedules-reconciler.d.ts

@@ -1,6 +1,6 @@
 /**
  * SCHEDULED-DM-IMPLEMENTATION-PLAN §6.5 — pure logic for the
- * `## Default Schedules` section of `rules/management.md`. Mirrors
+ * `## Default Schedules` section of `policies/management.md`. Mirrors
  * `policy-index-reconciler.ts` exactly — snapshot → rendered output,
  * with no DB or fs I/O. The runner (`default-schedules-runner.ts`)
  * drives it.
@@ -82,4 +82,3 @@ export declare function extractDefaultSchedulesSection(content: string): string
  * description when no sub_flow is present.
  */
 export declare function deriveDefaultScheduleLabel(subFlow: string | null, description: string): string;
-//# sourceMappingURL=default-schedules-reconciler.d.ts.map

package/dist/core/context/default-schedules-reconciler.js

@@ -1,6 +1,6 @@
 /**
  * SCHEDULED-DM-IMPLEMENTATION-PLAN §6.5 — pure logic for the
- * `## Default Schedules` section of `rules/management.md`. Mirrors
+ * `## Default Schedules` section of `policies/management.md`. Mirrors
  * `policy-index-reconciler.ts` exactly — snapshot → rendered output,
  * with no DB or fs I/O. The runner (`default-schedules-runner.ts`)
  * drives it.
@@ -150,4 +150,3 @@ export function deriveDefaultScheduleLabel(subFlow, description) {
         return description.trim() || EM_DASH;
     return words.charAt(0).toUpperCase() + words.slice(1);
 }
-//# sourceMappingURL=default-schedules-reconciler.js.map

package/dist/core/context/default-schedules-runner.d.ts

@@ -37,4 +37,3 @@ export declare function runDefaultSchedulesReconciler(opts: RunDefaultSchedulesR
  * directly (in-place splice without going through the runner).
  */
 export declare function buildDefaultSchedulesSnapshot(db: Database.Database): DefaultScheduleSnapshotEntry[];
-//# sourceMappingURL=default-schedules-runner.d.ts.map

package/dist/core/context/default-schedules-runner.js

@@ -155,14 +155,41 @@ export function buildDefaultSchedulesSnapshot(db) {
  */
 function parseRecurrenceRule(raw) {
     const obj = safeJsonObject(raw);
-    const frequency = obj.frequency === "weekly" || obj.frequency === "monthly"
+    // SCHEDULE_API_REDESIGN_PLAN §6.1 — whitelist must include `hourly`
+    // alongside weekly/monthly. Without it, a stored hourly rule renders
+    // as `daily —` in rules/management.md §B and breaks the round-trip
+    // property the runner relies on.
+    const frequency = obj.frequency === "hourly"
+        || obj.frequency === "weekly"
+        || obj.frequency === "monthly"
         ? obj.frequency
         : "daily";
-    const time = typeof obj.time === "string" ? obj.time : "—";
-    const out = { frequency, time };
+    // hourly has no `time`; daily/weekly/monthly do. Fall back to "—" to
+    // keep formatRecurrenceLabel safe on malformed rows.
+    const out = { frequency };
+    if (typeof obj.time === "string") {
+        out.time = obj.time;
+    }
+    else if (frequency !== "hourly") {
+        out.time = "—";
+    }
     if (typeof obj.timezone === "string" && obj.timezone.length > 0) {
         out.timezone = obj.timezone;
     }
+    if (frequency === "hourly") {
+        if (typeof obj.intervalHours === "number"
+            && Number.isInteger(obj.intervalHours)
+            && obj.intervalHours >= 1
+            && obj.intervalHours <= 23) {
+            out.intervalHours = obj.intervalHours;
+        }
+        if (typeof obj.minuteOfHour === "number"
+            && Number.isInteger(obj.minuteOfHour)
+            && obj.minuteOfHour >= 0
+            && obj.minuteOfHour <= 59) {
+            out.minuteOfHour = obj.minuteOfHour;
+        }
+    }
     if (Array.isArray(obj.daysOfWeek)) {
         const days = obj.daysOfWeek.filter((d) => typeof d === "number" && d >= 0 && d <= 6);
         if (days.length > 0)
@@ -173,6 +200,10 @@ function parseRecurrenceRule(raw) {
         if (days.length > 0)
             out.daysOfMonth = days;
     }
+    if (frequency === "monthly"
+        && (obj.onMissingDay === "skip" || obj.onMissingDay === "lastDayOfMonth")) {
+        out.onMissingDay = obj.onMissingDay;
+    }
     return out;
 }
 function safeJsonObject(value) {
@@ -213,8 +244,17 @@ function writeWithSnapshot(opts, absolutePath, content, previousContent) {
             logger.warn({ err, file: absolutePath }, "Failed to snapshot prior content before default-schedules write");
         }
     }
-    writeFileSync(absolutePath, content, "utf-8");
+    // Mark before the visible-write boundary (writeFileSync) so FS-watch
+    // consumers attribute the resulting event to the agent. Roll back on
+    // failure (C2).
     opts.writeTracker?.markWriting(absolutePath, content);
+    try {
+        writeFileSync(absolutePath, content, "utf-8");
+    }
+    catch (writeErr) {
+        opts.writeTracker?.unmark(absolutePath);
+        throw writeErr;
+    }
 }
 function relativizeToContext(contextDir, absolutePath) {
     if (absolutePath.startsWith(contextDir)) {
@@ -230,4 +270,3 @@ function persistRunRecord(db, record) {
         logger.warn({ err, record }, "Default-schedules reconciler run record persistence failed");
     }
 }
-//# sourceMappingURL=default-schedules-runner.js.map

package/dist/core/context/domain-index-reconciler.d.ts

@@ -70,6 +70,9 @@ export declare function relativeDomainIndexPath(domain: Domain): string;
  * Validate a relative path looks like a domain index. Used by the
  * runner's safety check before writing — defense-in-depth against a
  * caller-supplied domain that was tampered with.
+ *
+ * After CONTEXT_VAULT_REDESIGN domain indexes live at
+ * `knowledge/entities/<domain>/_index.md`.
  */
 export declare function isDomainIndexPath(relativePath: string): boolean;
 /**
@@ -78,4 +81,3 @@ export declare function isDomainIndexPath(relativePath: string): boolean;
  * for tests that exercise foreign paths).
  */
 export declare function entityDirToDomain(relativeDir: string): Domain | null;
-//# sourceMappingURL=domain-index-reconciler.d.ts.map

package/dist/core/context/domain-index-reconciler.js

@@ -165,20 +165,27 @@ function capitalize(value) {
  * runner uses this to resolve the absolute write target.
  */
 export function relativeDomainIndexPath(domain) {
-    return `${domain}/_index.md`;
+    return `knowledge/entities/${domain}/_index.md`;
 }
 /**
  * Validate a relative path looks like a domain index. Used by the
  * runner's safety check before writing — defense-in-depth against a
  * caller-supplied domain that was tampered with.
+ *
+ * After CONTEXT_VAULT_REDESIGN domain indexes live at
+ * `knowledge/entities/<domain>/_index.md`.
  */
 export function isDomainIndexPath(relativePath) {
     const segments = relativePath.split("/");
-    if (segments.length !== 2)
+    if (segments.length !== 4)
+        return false;
+    if (segments[0] !== "knowledge")
+        return false;
+    if (segments[1] !== "entities")
         return false;
-    if (segments[1] !== "_index.md")
+    if (segments[3] !== "_index.md")
         return false;
-    return DOMAINS.includes(segments[0]);
+    return DOMAINS.includes(segments[2]);
 }
 /**
  * Map an L2 entity directory back to its parent domain. Returns `null`
@@ -196,4 +203,3 @@ export function entityDirToDomain(relativeDir) {
         return null;
     return domain;
 }
-//# sourceMappingURL=domain-index-reconciler.js.map

package/dist/core/context/domain-index-runner.d.ts

@@ -32,4 +32,3 @@ export interface RunDomainIndexReconcilerOptions {
  *   - `refreshedMtime`  → number of files that already matched on disk
  */
 export declare function runDomainIndexReconciler(opts: RunDomainIndexReconcilerOptions): Promise<ReconcilerRunRecord>;
-//# sourceMappingURL=domain-index-runner.d.ts.map

package/dist/core/context/domain-index-runner.js

@@ -209,8 +209,16 @@ function writeWithSnapshot(opts, absolutePath, relativePath, content, previousCo
             logger.warn({ err, file: relativePath }, "Failed to snapshot prior content before domain-index write");
         }
     }
-    writeFileAtomically(absolutePath, content);
+    // Mark before the rename so FS-watch consumers attribute the resulting
+    // event to the agent. Roll back on failure (C2).
     opts.writeTracker?.markWriting(absolutePath, content);
+    try {
+        writeFileAtomically(absolutePath, content);
+    }
+    catch (writeErr) {
+        opts.writeTracker?.unmark(absolutePath);
+        throw writeErr;
+    }
 }
 function persistRunRecord(db, record) {
     try {
@@ -220,4 +228,3 @@ function persistRunRecord(db, record) {
         logger.warn({ err, record }, "Domain-index reconciler run record persistence failed");
     }
 }
-//# sourceMappingURL=domain-index-runner.js.map

package/dist/core/context/entity-mirror.d.ts

@@ -185,8 +185,9 @@ export declare function refreshEntityMirrorForPath(opts: RefreshOneOptions): Sin
 export declare function toRelativePath(contextDir: string, absolutePath: string): string | null;
 /**
  * True when the given relative path matches the L2 layout
- * `<domain>/<type-plural>/<slug>.md`. Does NOT validate the slug — that
- * is the parser's job — only the directory shape.
+ * `knowledge/entities/<domain>/<type-plural>/<slug>.md` (CONTEXT_VAULT_REDESIGN
+ * v4 V14). Does NOT validate the slug — that is the parser's job — only the
+ * directory shape and `_*.md` skip.
  */
 export declare function isL2EntityRelativePath(relativePath: string): boolean;
 export interface EntityMirrorWatcherOptions {
@@ -202,10 +203,12 @@ export interface EntityMirrorWatcherOptions {
      * because `shouldIndexPath` filters L2 paths out of the context-
      * index's own watcher (followups item 7).
      *
-     * No fan-out risk: the reconciler outputs (`<domain>/_index.md`,
-     * `_activity/<source>.md`) live outside the entity-mirror watcher's
-     * `<contextDir>/<domain>/<plural>/*.md` patterns and `_*.md` is
-     * explicitly ignored, so the chain cannot loop back through this
+     * No fan-out risk: the reconciler outputs
+     * (`knowledge/entities/<domain>/_index.md`,
+     * `state/activity/<source>.md`) live outside the entity-mirror
+     * watcher's `<contextDir>/knowledge/entities/<domain>/<plural>/*.md`
+     * patterns (domain-index uses `_*.md` which is ignored; Activity
+     * lives under `state/`), so the chain cannot loop back through this
      * observer.
      */
     onEntityChanged?: () => void;
@@ -224,4 +227,3 @@ export interface EntityMirrorWatcherHandle {
     stop(): Promise<void>;
 }
 export declare function startEntityMirrorWatcher(opts: EntityMirrorWatcherOptions): EntityMirrorWatcherHandle;
-//# sourceMappingURL=entity-mirror.d.ts.map