@aitne/daemon 0.1.8 → 0.1.9

package/dist/core/management-md.js

@@ -3,18 +3,21 @@ import { dirname, resolve } from "node:path";
 import * as chokidar from "chokidar";
 import { BACKEND_IDS, defaultIntegrationsMap, INTEGRATION_DESCRIPTORS, INTEGRATION_KEYS, integrationPatchSchema, isIntegrationKey, } from "@aitne/shared";
 import { readIntegrations, writeIntegrations, } from "../db/integrations-store.js";
-import { missingDelegatedVariants, missingNativeVariants } from "./skills-compiler.js";
+import { missingDelegatedVariants, missingNativeVariants } from "./skills-compiler-variants.js";
 import { createLogger } from "../logging.js";
 const logger = createLogger("management-md");
 const FILE_NAME = "integrations.md";
+const VAULT_RELATIVE_PATH = "policies/integrations.md";
 /**
  * Integration Delegation Framework — `integrations.md` render + parse + watch
  * (Phase 1).
  *
- * `integrations.md` lives at `<dataDir>/integrations.md` (top-level, alongside
- * `.env` and `data.db`). It is the human-editable view of the integrations
- * map; the DB (`settings` table, key `"integrations"`) is the authoritative
- * source for the daemon.
+ * After the CONTEXT_VAULT_REDESIGN restructure (§11.5), `integrations.md`
+ * lives at `<contextDir>/policies/integrations.md` — inside the vault,
+ * under the policies class. The legacy `~/.personal-agent/integrations.md`
+ * location is migrated on the first boot post-upgrade by the
+ * `0004-context-vault-restructure` migration. The DB (`settings` table,
+ * key `"integrations"`) remains the authoritative source for the daemon.
  *
  * Write paths:
  *   - `PATCH /api/integrations/:key` → DB update → `renderManagementMd()`
@@ -30,9 +33,23 @@ const FILE_NAME = "integrations.md";
  * unconditionally, so hand-edits that round-trip cleanly through the
  * parser produce identical bytes on the next render (no churn).
  */
-export function getManagementMdPath(dataDir) {
-    return resolve(dataDir, FILE_NAME);
+/**
+ * Resolve the canonical absolute path to the management/integrations
+ * markdown file under the vault: `<contextDir>/policies/integrations.md`.
+ *
+ * `contextDir` is the preferred input — production callers thread
+ * `getContextDir(config, db)` through so the path is correct in both
+ * plain and Obsidian-vault modes. The optional `(dataDir)` fallback to
+ * `<dataDir>/context` exists for test fixtures that don't construct a
+ * full `AgentConfig`; it is NOT correct for Obsidian users (V18) and is
+ * scheduled for removal once every test thread has been audited.
+ */
+export function getManagementMdPath(dataDir, contextDir) {
+    const root = contextDir ?? resolve(dataDir, "context");
+    return resolve(root, VAULT_RELATIVE_PATH);
 }
+/** Filename portion only — preserved for callers that need to mirror it. */
+export const MANAGEMENT_MD_FILENAME = FILE_NAME;
 const pendingSelfWrites = new Set();
 function markSelfWrite(absPath) {
     pendingSelfWrites.add(absPath);
@@ -355,6 +372,8 @@ function dataPathPrefixFor(key) {
             return "mail";
         case "outlook_calendar":
             return "calendar/outlook";
+        case "browser_history":
+            return "browser-history";
     }
 }
 export function renderManagementMd(integrations, notes = {
@@ -547,8 +566,8 @@ function isIsoDate(value) {
  * handler is wired (SETUP-FLOW-REDESIGN-PLAN §6.2) so any user edit
  * round-trips through the proper inputs.
  */
-export async function writeManagementMd(dataDir, integrations, notes) {
-    const path = getManagementMdPath(dataDir);
+export async function writeManagementMd(dataDir, integrations, notes, contextDir) {
+    const path = getManagementMdPath(dataDir, contextDir);
     await mkdir(dirname(path), { recursive: true });
     const body = renderManagementMd(integrations, notes);
     markSelfWrite(path);
@@ -559,8 +578,8 @@ export async function writeManagementMd(dataDir, integrations, notes) {
  * Read + parse the file from disk. Returns `null` when the file does not
  * exist — callers treat that as "first run, write defaults and move on".
  */
-export async function readAndParseManagementMd(dataDir) {
-    const path = getManagementMdPath(dataDir);
+export async function readAndParseManagementMd(dataDir, contextDir) {
+    const path = getManagementMdPath(dataDir, contextDir);
     try {
         const body = await readFile(path, "utf-8");
         return parseManagementMd(body);
@@ -584,8 +603,8 @@ export async function readAndParseManagementMd(dataDir) {
  *      file moves back to a known-good state. The owner-DM branch is
  *      Phase 2+; for now we only log.
  */
-export async function bootstrapManagementMd(dataDir, db, workspaceDir, notes) {
-    const path = getManagementMdPath(dataDir);
+export async function bootstrapManagementMd(dataDir, db, workspaceDir, notes, contextDir) {
+    const path = getManagementMdPath(dataDir, contextDir);
     const dbState = readIntegrations(db);
     let fileExists = true;
     try {
@@ -600,14 +619,14 @@ export async function bootstrapManagementMd(dataDir, db, workspaceDir, notes) {
         }
     }
     if (!fileExists) {
-        await writeManagementMd(dataDir, dbState, notes);
+        await writeManagementMd(dataDir, dbState, notes, contextDir);
         logger.info({ path }, "integrations.md created with default integrations map");
         return { path, created: true, integrations: dbState, rejections: [] };
     }
-    const parsed = await readAndParseManagementMd(dataDir);
+    const parsed = await readAndParseManagementMd(dataDir, contextDir);
     if (!parsed || !parsed.ok) {
         logger.warn({ path, errors: parsed?.errors, warnings: parsed?.warnings }, "integrations.md did not parse cleanly; re-rendering from DB");
-        await writeManagementMd(dataDir, dbState, notes);
+        await writeManagementMd(dataDir, dbState, notes, contextDir);
         return { path, created: false, integrations: dbState, rejections: [] };
     }
     const merged = mergeParsedIntoDb(dbState, parsed.integrations);
@@ -628,7 +647,7 @@ export async function bootstrapManagementMd(dataDir, db, workspaceDir, notes) {
     // Always re-render so daemon-owned columns are canonical — and so any
     // reverted rows are visibly corrected in the file even when the user
     // doesn't re-edit.
-    await writeManagementMd(dataDir, filtered, notes);
+    await writeManagementMd(dataDir, filtered, notes, contextDir);
     if (parsed.warnings.length > 0) {
         logger.warn({ warnings: parsed.warnings }, "integrations.md boot warnings");
     }
@@ -749,8 +768,8 @@ function integrationRowChanged(a, b) {
  * re-rendered to show the rollback, and (if `sendNotification` is wired)
  * the owner gets a DM explaining which files need to be authored.
  */
-export function startManagementMdWatcher(dataDir, db, options = {}) {
-    const path = getManagementMdPath(dataDir);
+export function startManagementMdWatcher(dataDir, db, options = {}, contextDir) {
+    const path = getManagementMdPath(dataDir, contextDir);
     const watcher = chokidar.watch(path, {
         persistent: true,
         ignoreInitial: true,
@@ -765,13 +784,13 @@ export function startManagementMdWatcher(dataDir, db, options = {}) {
             return;
         }
         try {
-            const parsed = await readAndParseManagementMd(dataDir);
+            const parsed = await readAndParseManagementMd(dataDir, contextDir);
             if (!parsed)
                 return;
             if (!parsed.ok) {
                 logger.warn({ path, errors: parsed.errors, warnings: parsed.warnings }, "integrations.md parse failed — rewriting from DB");
                 const dbState = readIntegrations(db);
-                await writeManagementMd(dataDir, dbState, options.getNoteSources?.());
+                await writeManagementMd(dataDir, dbState, options.getNoteSources?.(), contextDir);
                 return;
             }
             const dbState = readIntegrations(db);
@@ -799,14 +818,14 @@ export function startManagementMdWatcher(dataDir, db, options = {}) {
                 logger.info({ path, changedKeys: diffKeys(dbState, filtered), reason }, "integrations.md edit applied to DB");
                 // Re-render so timestamps the parser stamped with `now` become
                 // the canonical serialized form.
-                await writeManagementMd(dataDir, filtered, options.getNoteSources?.());
+                await writeManagementMd(dataDir, filtered, options.getNoteSources?.(), contextDir);
             }
             else if (rejections.length > 0) {
                 // The only change was a rejected delegated flip — filtered
                 // equals dbState, so no DB write, but we still want the file to
                 // visibly reflect the reverted state (otherwise the user's edit
                 // would appear to "stick" on disk).
-                await writeManagementMd(dataDir, filtered, options.getNoteSources?.());
+                await writeManagementMd(dataDir, filtered, options.getNoteSources?.(), contextDir);
             }
             else if (parsed.warnings.length > 0) {
                 logger.warn({ warnings: parsed.warnings }, "integrations.md: semantic-equivalent edit with warnings");
@@ -840,4 +859,3 @@ function buildRevertDm(rejections) {
     lines.push("Author these variants (or narrow the registry's skillsTouched / taskFlowsTouched) before retrying.");
     return lines.join("\n");
 }
-//# sourceMappingURL=management-md.js.map

package/dist/core/management-registry.d.ts

@@ -3,7 +3,7 @@ import { type ManagedTask, type SotBindings } from "@aitne/shared";
 import { type ManagementMdWriteLockManager } from "./management-md-write-lock.js";
 import { type ManagementParseFailureSection } from "../db/management-parse-failures-store.js";
 /**
- * `rules/management.md` registry — render / parse / boot / watch
+ * `policies/management.md` registry — render / parse / boot / watch
  * (docs/design/21-management-registry-and-entities.md §7.2, §11, P2).
  *
  * Architectural mirror of `core/management-md.ts` (which owns the
@@ -205,7 +205,7 @@ export type WatcherReconcileResult = {
  */
 export declare function reconcileManagementMdFromFile(contextDir: string, db: Database.Database, lockManager: ManagementMdWriteLockManager, reason?: "change" | "add" | "manual"): Promise<WatcherReconcileResult>;
 /**
- * Watch `rules/management.md` for hand-edits and reconcile them against
+ * Watch `policies/management.md` for hand-edits and reconcile them against
  * the DB (§7.2 watch path). Self-writes are ignored. Fatal parse errors
  * trigger a re-render from the DB; row-level failures are recorded in
  * `management_parse_failures` and the dashboard surfaces a banner.
@@ -216,7 +216,7 @@ export declare function reconcileManagementMdFromFile(contextDir: string, db: Da
  */
 export declare function startManagementRegistryWatcher(contextDir: string, db: Database.Database, options?: ManagementRegistryWatcherOptions): ManagementRegistryWatcherHandle;
 /**
- * §0.2 — `rules/management.md` is the first wildcard ref in
+ * §0.2 — `policies/management.md` is the first wildcard ref in
  * `policy-files.ts`'s registry. The P2 plan calls out a verification
  * gate: "Verify `policy-files.ts` wildcard ref still loads the v3 file
  * unchanged." This helper is exposed so the boot path (and tests)
@@ -234,4 +234,3 @@ export declare function verifyManagementMdLoadable(contextDir: string, policyFil
     ok: false;
     reason: string;
 };
-//# sourceMappingURL=management-registry.d.ts.map

package/dist/core/management-registry.js

@@ -13,7 +13,7 @@ import { recordManagementMdRenderDuration } from "./management-telemetry.js";
 import { createLogger } from "../logging.js";
 const logger = createLogger("management-registry");
 /**
- * `rules/management.md` registry — render / parse / boot / watch
+ * `policies/management.md` registry — render / parse / boot / watch
  * (docs/design/21-management-registry-and-entities.md §7.2, §11, P2).
  *
  * Architectural mirror of `core/management-md.ts` (which owns the
@@ -64,7 +64,7 @@ const DEFAULT_C_STUB = [
     SECTION_C_HEADER,
     "",
     "Auto-maintained by the daemon (do not edit). Source files live under",
-    "`rules/policies/<slug>.md`; capture new policies via the",
+    "`policies/management-captures/<slug>.md`; capture new policies via the",
     "`management-policy` skill. Full index: [[rules/policies/_index.md]]",
     "",
     "_No active policies yet._",
@@ -74,7 +74,7 @@ const DEFAULT_NOTES_BLOCK = [
     "## Notes",
     "",
     "- The agent cannot use `Edit` / `Write` tools on this file — writes go",
-    "  through `/api/context/rules/management` (locked + snapshotted) or the",
+    "  through `/api/context/policies/management` (locked + snapshotted) or the",
     "  managed-tasks / sot-bindings API surfaces.",
     "- This file is injected into every flow via `policy-files.ts`. Keep it",
     "  concise so prompt assembly stays cheap.",
@@ -815,7 +815,7 @@ export async function reconcileManagementMdFromFile(contextDir, db, lockManager,
     return outcome;
 }
 /**
- * Watch `rules/management.md` for hand-edits and reconcile them against
+ * Watch `policies/management.md` for hand-edits and reconcile them against
  * the DB (§7.2 watch path). Self-writes are ignored. Fatal parse errors
  * trigger a re-render from the DB; row-level failures are recorded in
  * `management_parse_failures` and the dashboard surfaces a banner.
@@ -857,7 +857,7 @@ export function startManagementRegistryWatcher(contextDir, db, options = {}) {
 /* c8 ignore stop */
 // ── policy-files.ts compatibility check (P2 acceptance gate) ───────────────
 /**
- * §0.2 — `rules/management.md` is the first wildcard ref in
+ * §0.2 — `policies/management.md` is the first wildcard ref in
  * `policy-files.ts`'s registry. The P2 plan calls out a verification
  * gate: "Verify `policy-files.ts` wildcard ref still loads the v3 file
  * unchanged." This helper is exposed so the boot path (and tests)
@@ -882,4 +882,3 @@ export function verifyManagementMdLoadable(contextDir, policyFileMaxBytes) {
     }
     return { ok: true, bytes };
 }
-//# sourceMappingURL=management-registry.js.map

package/dist/core/management-telemetry.d.ts

@@ -39,7 +39,7 @@ export declare function recordManagementMdRenderDuration(durationMs: number): vo
 /**
  * Record one per-source activity-view rebuild wall-clock sample. The
  * `source` is the user-typed app label (matches the `source:`
- * frontmatter in `_activity/<source>.md`).
+ * frontmatter in `state/activity/<source>.md`).
  */
 export declare function recordActivityViewRebuildDuration(source: string, durationMs: number): void;
 /**
@@ -97,4 +97,3 @@ export declare function resetManagementTelemetry(): void;
  * without poking the module-level buffer.
  */
 export declare function summarize(samples: readonly number[]): HistogramSummary;
-//# sourceMappingURL=management-telemetry.d.ts.map

package/dist/core/management-telemetry.js

@@ -51,7 +51,7 @@ export function recordManagementMdRenderDuration(durationMs) {
 /**
  * Record one per-source activity-view rebuild wall-clock sample. The
  * `source` is the user-typed app label (matches the `source:`
- * frontmatter in `_activity/<source>.md`).
+ * frontmatter in `state/activity/<source>.md`).
  */
 export function recordActivityViewRebuildDuration(source, durationMs) {
     if (!Number.isFinite(durationMs) || durationMs < 0)
@@ -153,4 +153,3 @@ function percentile(sorted, p) {
     const idx = Math.min(Math.floor(sorted.length * p), sorted.length - 1);
     return sorted[idx];
 }
-//# sourceMappingURL=management-telemetry.js.map

package/dist/core/message-recorder.d.ts

@@ -9,9 +9,9 @@ import type { IMessageRecorder } from "./dispatcher.js";
  * INSERT and the UPDATE run in the same `db.transaction(...)` so the
  * counter cannot drift from the actual row count: if the INSERT rolls
  * back (FK break, disk full, corruption), the UPDATE rolls back too.
- * This replaces the older paired `recordMessage(...); touchSession(...)`
- * calling convention, which was the root cause of the v28 FK regression
- * leaving `message_count` counting phantom turns.
+ * Replaces the older paired `recordMessage(...); touchSession(...)`
+ * calling convention, whose split-transaction shape left
+ * `message_count` counting phantom turns when the INSERT rolled back.
  *
  * Returns `true` on successful persistence, `false` on error (caller
  * decides whether to surface it — the dispatcher, for example, turns an
@@ -35,4 +35,3 @@ export declare class MessageRecorder implements IMessageRecorder {
         notificationDispatchId?: string | null;
     }): boolean;
 }
-//# sourceMappingURL=message-recorder.d.ts.map

package/dist/core/message-recorder.js

@@ -9,9 +9,9 @@ const logger = createLogger("message-recorder");
  * INSERT and the UPDATE run in the same `db.transaction(...)` so the
  * counter cannot drift from the actual row count: if the INSERT rolls
  * back (FK break, disk full, corruption), the UPDATE rolls back too.
- * This replaces the older paired `recordMessage(...); touchSession(...)`
- * calling convention, which was the root cause of the v28 FK regression
- * leaving `message_count` counting phantom turns.
+ * Replaces the older paired `recordMessage(...); touchSession(...)`
+ * calling convention, whose split-transaction shape left
+ * `message_count` counting phantom turns when the INSERT rolled back.
  *
  * Returns `true` on successful persistence, `false` on error (caller
  * decides whether to surface it — the dispatcher, for example, turns an
@@ -85,4 +85,3 @@ export class MessageRecorder {
         }
     }
 }
-//# sourceMappingURL=message-recorder.js.map

package/dist/core/metrics.d.ts

@@ -549,4 +549,3 @@ interface PrePassParsedAttempt {
  */
 export declare function aggregatePrePassMetrics(attempts: readonly PrePassParsedAttempt[], windowDays: number, collectedAt: string): PrePassMetricsSnapshot;
 export {};
-//# sourceMappingURL=metrics.d.ts.map

package/dist/core/metrics.js

@@ -1075,4 +1075,3 @@ export function aggregatePrePassMetrics(attempts, windowDays, collectedAt) {
         costUsdByBackend: costUsdByBackendBuckets,
     };
 }
-//# sourceMappingURL=metrics.js.map

package/dist/core/migration-backup.d.ts

@@ -215,4 +215,3 @@ export declare function stashOverwrittenTargetEntries(targetDir: string, entries
  * collisions too) then re-places the original target-side version.
  */
 export declare function restoreOverwrittenTargetEntries(backup: BackupResult, targetDir: string, entries: string[]): void;
-//# sourceMappingURL=migration-backup.d.ts.map

package/dist/core/migration-backup.js

@@ -331,6 +331,7 @@ export function inspectDir(rootDir) {
  * user data that happens to share the name.
  */
 export const AGENT_FILE_TOP_LEVEL = new Set([
+    // Loose top-level survivors (legacy + canonical _index.md).
     "today.md",
     "yesterday.md",
     "roadmap.md",
@@ -338,6 +339,9 @@ export const AGENT_FILE_TOP_LEVEL = new Set([
     "context-index.md",
     "agent-journal.md",
     "user.md",
+    // Legacy top-level dirs (pre-CONTEXT_VAULT_REDESIGN) — kept so an
+    // upgrading install whose target carries them is not flagged
+    // foreign.
     "agent",
     "bases",
     "daily",
@@ -353,6 +357,13 @@ export const AGENT_FILE_TOP_LEVEL = new Set([
     "user",
     "user-details",
     "weekly",
+    // CONTEXT_VAULT_REDESIGN six-class top-level dirs.
+    "identity",
+    "state",
+    "plans",
+    "journal",
+    "knowledge",
+    "policies",
 ]);
 /**
  * Entries the migration silently ignores in a target directory — either
@@ -931,4 +942,3 @@ function restoreDirectory(srcDir, dstDir) {
         }
     }
 }
-//# sourceMappingURL=migration-backup.js.map

package/dist/core/morning/agent-journal-appender.d.ts

@@ -1,6 +1,6 @@
 /**
  * `appendMorningRoutineJournalEntry` — assemble the one-block English
- * audit-trail entry for `agent/journal.md` from **structured sources
+ * audit-trail entry for `journal/agent.md` from **structured sources
  * only** (agent_actions rows + daily/<yesterday>.md frontmatter
  * deterministic fs read) and append it to the journal file.
  *
@@ -19,9 +19,18 @@
  *     - Checks from routines/morning.md: (none)
  *     - Anomalies / skipped steps: (none)
  *
- * Initial-flow / Stage-B-failed branches surface the rev1 variant:
+ * The `- Journal: ...` line is replaced by a `Journal synthesis: ...`
+ * variant when the daily file is absent or Stage B did not succeed:
  *
- *     - Journal synthesis: skipped (no prior-day data)
+ *     - Journal synthesis: skipped (no prior-day data)               (first-run)
+ *     - Journal synthesis: failed (audit row missing — see daemon log) (anomaly)
+ *     - Journal synthesis: failed (Stage B <state>)                   (terminal failure)
+ *     - Journal synthesis: failed (Stage B success but daily file missing) (PUT lost)
+ *
+ * The verb (`skipped` vs `failed`) reflects whether Stage B was even
+ * attempted — `skipped` is reserved for the first-run case where the
+ * orchestrator never dispatched Stage B; everything else surfaces as
+ * `failed` so the audit-trail language matches reality.
  *
  * No LLM final-text parsing anywhere — every field is sourced from a
  * structured channel: `agent_actions.metadata` (written by Stage A via
@@ -39,7 +48,40 @@ export interface StageActionRow {
     result: "success" | "failed" | "partial" | "skipped" | "in_progress";
     /** Parsed JSON. `{}` when the column was NULL or non-object. */
     metadata: Record<string, unknown>;
+    /**
+     * daily-journal-daemon-write.md §4.7 — Stage B `agent_actions.detail`
+     * carries a discriminated `dailyWrite` block when the daemon-side
+     * composer ran. Three states map to the journal-line verbs:
+     *   - `"complete"` → "Journal: daily/<date>.md (N lines, M projects)"
+     *   - `"partial"`  → "Journal: daily/<date>.md (N lines, **partial — <reason>**)"
+     *   - `false`      → "Journal synthesis: failed (<reason>)"
+     *
+     * Absent on rows written before the §4.11 wiring landed; readers fall
+     * back to the file-presence heuristic for backward compatibility.
+     */
+    dailyWrite?: DailyWriteDetail | null;
 }
+/**
+ * Mirror of `DailyWriteAuditDetail` in `dispatcher-types.ts`. Re-declared
+ * here rather than imported to keep the appender's import graph stable
+ * (it sits below the dispatcher in the dep order today). The fields
+ * are read defensively — `parseDailyWriteDetail` validates the shape
+ * before consumption so a malformed row degrades to "field absent"
+ * rather than corrupting the audit line.
+ */
+export type DailyWriteDetail = {
+    ok: "complete";
+    bytesWritten?: number;
+    wroteMode?: "put" | "append_revision";
+} | {
+    ok: "partial";
+    bytesWritten?: number;
+    wroteMode?: "put" | "append_revision";
+    partialReason: "frontmatter_tag_missing" | "frontmatter_invalid_json" | "frontmatter_schema_invalid";
+} | {
+    ok: false;
+    reason: "stage_b_null" | "empty_output" | "body_tag_missing" | "write_failed";
+};
 export interface AgentJournalAppenderDeps {
     db: Database.Database;
     contextDir: string;
@@ -59,7 +101,7 @@ export interface AgentJournalAppenderArgs {
      * summary used to live in the user-facing `daily/<date>.md` `## Actions`
      * section, but was moved here as part of the user-diary refocus: the
      * user-side journal no longer carries agent telemetry, while the
-     * agent-side footprint (`agent/journal.md`) gains a single inline
+     * agent-side footprint (`journal/agent.md`) gains a single inline
      * summary line so the breakdown remains discoverable to operators
      * running `pnpm audit`. The orchestrator owns the timezone /
      * dayBoundaryHour math; passing the window in keeps this module pure
@@ -140,6 +182,32 @@ export interface JournalEntryComposeInputs {
      * SQLite aggregation.
      */
     actionsSummary?: ActionsSummaryInput;
+    /**
+     * Whether Stage B was attempted (i.e. `yesterday.md` existed when the
+     * orchestrator built Stage B's inputs — `buildStageBInputs` returns
+     * non-null iff yesterday.md is on disk). The end-to-end
+     * `appendMorningRoutineJournalEntry` derives this from a live
+     * `existsSync(yesterday.md)` check.
+     *
+     * Disambiguates two states that previously rendered identically as
+     * `Journal synthesis: skipped (no prior-day data)`:
+     *   - `false` → first-run / no prior-day data: legitimate skip.
+     *   - `true` AND `stageB === null` → Stage B was dispatched but its
+     *     `agent_actions` row never landed. This is a defence-in-depth
+     *     anomaly path: with the orchestrator-side failure-row write in
+     *     place (`recordStageFailure` → `audit.logError`), the only way
+     *     to reach this state is a rare SQLite write failure inside
+     *     `audit.logError` itself. Surface it as `Journal synthesis:
+     *     failed (audit row missing — see daemon log)` instead of
+     *     masking the failure as a first-run.
+     *
+     * Optional so unit tests that don't care about the disambiguation
+     * stay terse; when omitted the composer falls back to the legacy
+     * heuristic (`stageB === null` → first-run), preserving the
+     * pre-disambiguation behaviour for callers that haven't been
+     * updated.
+     */
+    stageBAttempted?: boolean;
 }
 /**
  * Pure composer — every output byte is a deterministic function of the
@@ -148,14 +216,14 @@ export interface JournalEntryComposeInputs {
  */
 export declare function composeMorningRoutineJournalEntry(inputs: JournalEntryComposeInputs): string;
 /**
- * Append the composed entry to `agent/journal.md`. Mirrors the write
- * chokepoint that `PATCH /api/context/agent/journal?mode=append_to_file`
+ * Append the composed entry to `journal/agent.md`. Mirrors the write
+ * chokepoint that `PATCH /api/context/journal/agent?mode=append_to_file`
  * exposes to the agent: snapshot the existing file into
  * `md_file_snapshots`, write the new content atomically, then notify
  * the write tracker + indexer so observers don't tag the write as a
  * user-actor change.
  */
-export declare function appendMorningRoutineJournalEntry(deps: AgentJournalAppenderDeps, args: AgentJournalAppenderArgs): AgentJournalAppenderResult;
+export declare function appendMorningRoutineJournalEntry(deps: AgentJournalAppenderDeps, args: AgentJournalAppenderArgs): Promise<AgentJournalAppenderResult>;
 /**
  * Append a new top-level block (delimited by H2 heading) to the
  * journal. When the file does not yet exist, seed it with the
@@ -194,4 +262,3 @@ export interface DailyJournalStats {
  * Exposed for testing so the parsing branches stay pinnable.
  */
 export declare function inspectDailyJournal(content: string): DailyJournalStats;
-//# sourceMappingURL=agent-journal-appender.d.ts.map