@aitne/daemon 0.1.8 → 0.1.10

package/dist/core/skills-manifest.d.ts

@@ -9,7 +9,7 @@ export declare const ALL_SKILLS: string[];
  * The slim built-in evening steps (Handoff, Long-term Plans promotion,
  * Review-date fire, Raw Signals graduation) emit no user-facing output.
  * `notify` is only load-bearing when the operator has written at least
- * one `### <label>` rule into `routines/evening.md` that may post to
+ * one `### <label>` rule into `policies/routines/evening.md` that may post to
  * `/api/notify` — the universal message-discipline contract in the
  * notify skill is the binding format guide for those rules.
  *
@@ -69,6 +69,7 @@ export declare function managedTasksActive(db: Database.Database | null | undefi
  * anchor / phrase.
  */
 export declare function managedTasksActiveForDm(db: Database.Database | null | undefined, messageText: string | null | undefined): boolean;
+export declare function agentCreateActiveForDm(messageText: string | null | undefined): boolean;
 /**
  * `evening-review-slimdown.md` §2.1 — context-aware manifest resolver.
  *
@@ -109,4 +110,31 @@ export declare function getProfileForEvent(eventType: string): string;
 export declare function getSkillsForEvent(eventType: string): string[];
 export declare function getProfileForProcess(processKey: ProcessKey): string;
 export declare function getSkillsForProcess(processKey: ProcessKey): string[];
-//# sourceMappingURL=skills-manifest.d.ts.map
+/**
+ * Compose an Agent definition's `tools.skills` (AGENT_DEFINITIONS_DESIGN.md
+ * §4.2 / `packages/shared/src/agent-definitions.ts` `skills_replace`) with the
+ * process-key default skill bundle. The schema comment promised "the loader
+ * composes the effective set"; this is that composition, applied at session
+ * materialisation (`materializeSessionBundle`) where the skill set is actually
+ * resolved.
+ *
+ * Semantics:
+ *   - `replace === false` (default): union — the default bundle PLUS every
+ *     extra slug not already present. Base order first (so the manifest's
+ *     intentional ordering is preserved), then appended extras.
+ *   - `replace === true`: the extra list is a strict subset that fully
+ *     supplants the default bundle.
+ *   - empty / absent `extra`: pure no-op — returns a copy of `base` unchanged,
+ *     INCLUDING when `replace` is true. An Agent that sets `skills_replace`
+ *     with no `skills` is treated as "no override" rather than "strip every
+ *     skill", because stripping `context` / `notify` from the bundle would
+ *     break the run; callers that want an empty set pass it explicitly and
+ *     the dispatcher gates the override on a non-empty list anyway.
+ *
+ * Output is always deduped (a slug appearing in both base and extra, or twice
+ * in extra, lands once). Unknown slugs are NOT filtered here — the
+ * materialiser skips any slug whose `SKILL.md` is absent on disk, and the
+ * Agent loader already emits an "unknown skill" warning at parse time — so
+ * keeping them keeps the stamp/drift snapshot and this list in agreement.
+ */
+export declare function composeSkillSet(base: readonly string[], extra: readonly string[] | undefined | null, replace: boolean): string[];

package/dist/core/skills-manifest.js

@@ -56,7 +56,7 @@ export const EVENT_SKILL_SETS = {
     // roadmap skill. See ROADMAP-REDESIGN.md §3.7.
     // Morning routine input cap: the task-flow drives mail + calendar + roadmap
     // walk + today.md write + schedule register. Skills outside that surface
-    // (`external-services`, `notion`, `travel`, `travel-time`) inline 20+ KB of
+    // (`external-services`, `notion`, `travel`) inline 20+ KB of
     // API reference for endpoints the routine never calls — every dropped slug
     // here is one whose endpoints don't appear in routine.morning_routine.md.
     // Notion drain happens via /api/observations (taught by `observations`);
@@ -80,10 +80,9 @@ export const EVENT_SKILL_SETS = {
         // for a natural opportunity. See profile-interview-queue.md §3.1.
         "user-interview",
     ],
-    // `routine.morning_routine_initial` retired by
-    // morning-routine-optimization.md Phase 7 (2026-05-16). The first-run
-    // branch flows through `routine.morning_routine_today` (Stage A) below.
-    // morning-routine-optimization.md Phase 5/6 — split morning routine.
+    // `routine.morning_routine_initial` is retired. The first-run branch
+    // flows through `routine.morning_routine_today` (Stage A) below. See
+    // morning-routine-optimization.md for the split rationale.
     // Stage A (today.md synthesis) inherits the legacy bundle PLUS
     // `agent-actions` for the structured self-report Step 9 makes through
     // `PATCH /api/agent-actions/self`. The skill is small (~120 lines of
@@ -101,20 +100,21 @@ export const EVENT_SKILL_SETS = {
         "user-interview",
         "agent-actions",
     ],
-    // Stage B (daily journal author) is intentionally minimal — only the
-    // context skill for vault-path writes to `daily/<date>.md` (the
-    // single PUT/PATCH this stage emits). No mail / schedule / roadmap /
-    // observations: those are Stage A's territory and inflating Stage B's
-    // bundle would defeat the cold-start floor that makes lite-tier
-    // viable for the journal-author workload.
-    "routine.morning_routine_journal": ["context"],
+    // docs/design/appendices/daily-journal-daemon-write.md §4.10 — Stage B
+    // no longer needs the `context` skill (or any other skill). The
+    // daemon-side composer (`core/morning/daily-journal-composer.ts`)
+    // performs the daily-journal write deterministically from the LLM's
+    // tagged final-text output; Stage B has zero tool requirement so the
+    // `dontAsk` denial layer that previously trapped Haiku's
+    // `cat > /tmp/...` attempts becomes structurally moot.
+    "routine.morning_routine_journal": [],
     // `evening-review-slimdown.md` §2.1 — Phase 2 dropped `travel`
     // unconditionally (was only kept for Step 4's "newly detected bookings"
     // path, deleted alongside Step 4). `notify` is loaded *conditionally* via
     // `resolveSkillManifest` — the built-in steps emit no user-facing output,
     // so the universal message-discipline contract is only needed when the
     // user has authored at least one `### ` rule in
-    // `routines/evening.md` that may call `POST /api/notify`. Callers MUST go
+    // `policies/routines/evening.md` that may call `POST /api/notify`. Callers MUST go
     // through `resolveSkillManifest(event, { contextDir })` to apply the gate;
     // direct `EVENT_SKILL_SETS[event]` reads see the static (`notify`-on)
     // shape and are intentionally conservative for tooling that doesn't have
@@ -153,6 +153,30 @@ export const EVENT_SKILL_SETS = {
         "reading",
     ],
     "routine.roadmap_refresh": ["context", "external-services", "notion", "roadmap"],
+    // BROWSER_HISTORY_INTEGRATION_PLAN P3. Each browser-history routine
+    // loads the agent-facing browser-history skill (curl chokepoint to
+    // /api/browser-history/*) plus `context` for the research-journal /
+    // assistance / wiki write paths. `notify` is layered on for any
+    // routine that DMs the user — the routine_protocol block tells the
+    // agent that /api/notify is the only user-visible channel for
+    // routines, but only `notify`'s SKILL.md carries the actual curl
+    // shape (host, port, body schema, priority field, awareness-gate
+    // rules). Without it the agent has to guess the API surface, which
+    // breaks the "DM the owner with..." instructions in the task-flows.
+    //
+    // cluster_update stays silent — it appends to a journal file and
+    // does not DM. The offer DM routine has the curl shape inline in
+    // its task-flow so the narrow skill set is acceptable there; the
+    // two accept-path routines (research_dispatch, research_wiki_summary)
+    // need `notify` because their task-flows just say "DM the owner".
+    "routine.research_cluster_update": ["browser-history", "context"],
+    // BROWSER_HISTORY_INTEGRATION_PLAN §10.1 (seventh-pass) — offer DM
+    // composition is its own lite-tier session. The task-flow inlines
+    // the curl shape; no browser-history-respond — that skill lives on
+    // the message.dm side where the user's reply lands.
+    "routine.research_offer_dm": ["browser-history", "context"],
+    "routine.research_dispatch": ["browser-history", "context", "notify"],
+    "routine.research_wiki_summary": ["browser-history", "context", "notify"],
     // Dashboard-triggered manual refresh of today.md's User Schedule
     // section. Intentionally narrow — the flow only reads the calendar
     // and PATCHes user_schedule / agent_log. No mail, no roadmap, no
@@ -187,10 +211,9 @@ export const EVENT_SKILL_SETS = {
         "external-services",
         "mail",
         "notion",
-        // docs/design/appendices/skills-improvement.md §9-§11 — merged from travel +
-        // travel-time + receipts. Conditionally loaded via
-        // `gmailLifestyleActiveForDm` so DMs that don't mention
-        // travel / receipts / commute and have no fresh bookings or
+        // docs/design/appendices/skills-improvement.md §9-§11 — merged from travel
+        // + receipts. Conditionally loaded via `gmailLifestyleActiveForDm` so DMs
+        // that don't mention travel / receipts and have no fresh bookings or
         // unsaved receipts don't pay the ~180-line cost.
         "gmail-lifestyle",
         "roadmap",
@@ -203,6 +226,9 @@ export const EVENT_SKILL_SETS = {
         // DB has zero rows AND the message text carries no `mt_<n>` /
         // "managed task" / "recurring fetch" anchor.
         "managed-tasks",
+        // Scheduling split — author a recurring Agent when the user asks for an
+        // ongoing cadence (`/schedule` is one-shot only).
+        "agent-create",
     ],
     "message.received.dm_first": [
         "context",
@@ -218,11 +244,22 @@ export const EVENT_SKILL_SETS = {
         "roadmap",
         "management-policy",
         "managed-tasks",
+        // Scheduling split — recurring tasks are Agents (see `message.received`).
+        "agent-create",
         // DM handler decides whether the inbound topic is a natural moment
         // to weave a latent profile question into the reply, and ticks the
         // queue when the user answers a previously-asked one. See
         // profile-interview-queue.md §3.3 + the latent-opportunity block.
         "user-interview",
+        // BROWSER_TASK_REDESIGN_PLAN.md §10 / Phase 5 — also loaded for the
+        // user's first DM. The redesign's stated intent ("DM agent can hand
+        // any natural-language browser request") covers first-time DMs too;
+        // omitting it here would mean the user's literal first message
+        // "post to X" silently misses the skill and the agent has to
+        // bluff. The `browser-history-respond` skill is correctly absent
+        // (no prior research offer to respond to) — that exclusion does
+        // not generalise.
+        "browser-task",
     ],
     "message.received.dm": [
         "context",
@@ -239,6 +276,35 @@ export const EVENT_SKILL_SETS = {
         "management-policy",
         "managed-tasks",
         "user-interview",
+        // Scheduling split — recurring tasks are Agents (see `message.received`).
+        "agent-create",
+        // BROWSER_HISTORY_INTEGRATION_PLAN §10.1 (seventh-pass) — narrow
+        // accept-surface for natural-language reply to a research offer
+        // DM. The skill body documents the intent-mapping rules
+        // (research/dig → research_assist; summarise → wiki_summary;
+        // no thanks → decline). Conditional load is intentionally absent;
+        // the skill itself no-ops when `GET /offers/pending` is empty,
+        // and the cost of having the skill text in DM context is small.
+        "browser-history-respond",
+        // BROWSER_TASK_REDESIGN_PLAN.md §10 / Phase 5 — DM-driven entry
+        // point to the open-ended browser-task surface. The legacy
+        // `browser-history-managed` skill (and the
+        // `routine.browser_automation_request` / `routine.managed_sync_health_check`
+        // process keys that loaded it) was retired in Phase 6; the new
+        // `browser-task` skill teaches the DM agent to POST a
+        // natural-language description, relay sub-agent clarifications via
+        // /clarify, and cancel on user request — without ever touching the
+        // `!~xxxxxxxx` final-confirm token (that round-trip stays between
+        // the daemon and the user). Loaded for `message.received.dm` AND
+        // `message.received.dm_first` (`dashboard.chat` and `message.dm`
+        // inherit the former via PROCESS_TO_EVENT_TYPE). Mentions /
+        // scheduled DMs / routines do not carry it — mentions land on
+        // `message.received` which is a shared-channel surface, and
+        // scheduled DMs are daemon-initiated (no user-driven browser ask
+        // to relay). No conditional gate — the skill body is small and
+        // the agent simply does not call its endpoints when the user's
+        // request doesn't ask for a browser task.
+        "browser-task",
     ],
     // ── Task events ──
     "schedule.approaching": [
@@ -459,8 +525,8 @@ export const ALL_SKILLS = [
     "external-services",
     "mail",
     "notion",
-    // docs/design/appendices/skills-improvement.md §9-§11 — merged from travel +
-    // travel-time + receipts. Conditionally loaded for DMs / routines via
+    // docs/design/appendices/skills-improvement.md §9-§11 — merged from travel
+    // + receipts. Conditionally loaded for DMs / routines via
     // `gmailLifestyleActive*` predicates.
     "gmail-lifestyle",
     "roadmap",
@@ -480,6 +546,28 @@ export const ALL_SKILLS = [
     "wiki-trace",
     "wiki-connect",
     "wiki-graduate",
+    // BROWSER_HISTORY_INTEGRATION_PLAN P3 — agent-facing skill for the
+    // /api/browser-history/* surface. Bundled with `context` for the
+    // research-journal write path.
+    "browser-history",
+    // BROWSER_HISTORY_INTEGRATION_PLAN §10.1 (seventh-pass) — narrow
+    // accept-surface skill loaded for `message.received.dm` (which both
+    // `message.dm` and `dashboard.chat` inherit). Exposes only the
+    // pending-offers list + accept/decline endpoints so the standard
+    // DM agent can translate a user's natural-language reply into the
+    // structured dispatch call. The full `browser-history` skill is
+    // intentionally NOT loaded for message.dm — DM agent isolation.
+    "browser-history-respond",
+    // BROWSER_TASK_REDESIGN_PLAN.md §10 / Phase 5 — DM-driven entry
+    // point to the open-ended browser-task surface. Loaded only for
+    // `message.received.dm` (DM agent + dashboard chat). The legacy
+    // `browser-history-managed` skill that fronted the frozen workflow
+    // registry was retired alongside the route + routines in Phase 6.
+    "browser-task",
+    // Scheduling split — `/schedule` is one-shot only; recurring tasks are
+    // Agents. This skill teaches the DM agent to author a detailed recurring
+    // Agent (`POST /api/agents`) when the user asks for an ongoing cadence.
+    "agent-create",
 ];
 const PROCESS_TO_EVENT_TYPE = {
     "routine.morning_routine": "routine.morning_routine",
@@ -495,6 +583,10 @@ const PROCESS_TO_EVENT_TYPE = {
     "routine.roadmap_refresh": "routine.roadmap_refresh",
     "routine.today_refresh": "routine.today_refresh",
     "routine.user_profile_sweep": "routine.user_profile_sweep",
+    "routine.research_cluster_update": "routine.research_cluster_update",
+    "routine.research_offer_dm": "routine.research_offer_dm",
+    "routine.research_dispatch": "routine.research_dispatch",
+    "routine.research_wiki_summary": "routine.research_wiki_summary",
     "message.dm": "message.received.dm",
     "message.mention": "message.received",
     "dashboard.chat": "message.received.dm",
@@ -523,7 +615,7 @@ const PROCESS_TO_EVENT_TYPE = {
  * The slim built-in evening steps (Handoff, Long-term Plans promotion,
  * Review-date fire, Raw Signals graduation) emit no user-facing output.
  * `notify` is only load-bearing when the operator has written at least
- * one `### <label>` rule into `routines/evening.md` that may post to
+ * one `### <label>` rule into `policies/routines/evening.md` that may post to
  * `/api/notify` — the universal message-discipline contract in the
  * notify skill is the binding format guide for those rules.
  *
@@ -616,7 +708,6 @@ export function gmailLifestyleActive(db) {
  */
 const GMAIL_LIFESTYLE_TRIGGER_RE = new RegExp(String.raw `\b(receipts?|expenses?|invoices?|flights?|hotels?|trains?|commute|trips?|bookings?|reservations?)\b`, "i");
 const GMAIL_LIFESTYLE_PHRASE_TRIGGERS = [
-    "travel time",
     "departure time",
 ];
 function dmMentionsGmailLifestyle(messageText) {
@@ -708,6 +799,27 @@ export function managedTasksActiveForDm(db, messageText) {
         return true;
     return dmMentionsManagedTasks(messageText);
 }
+/**
+ * Scheduling split — predicate for the `agent-create` skill (teaches the DM
+ * agent to author a recurring **work** Agent via `POST /api/agents`). Loaded
+ * only when the inbound DM looks like a recurring-autonomous-work request:
+ * a recurring cadence AND an autonomous-work verb (so a recurring *DM*
+ * — "DM me every morning", which belongs on `dm_session` — and a one-shot
+ * "remind me tomorrow" both miss). A direct "automate" / "recurring agent"
+ * phrasing fires on its own. Message-only (the skill has no runtime DB state);
+ * a DM with no message text (test default) drops the skill.
+ */
+const AGENT_CREATE_CADENCE_RE = /\b(every\s+(day|morning|evening|night|hour|week|month|monday|tuesday|wednesday|thursday|friday|saturday|sunday)|each\s+(day|morning|week|month)|daily|weekly|monthly|hourly|recurring|recurrence|from now on|on a schedule|regularly|periodically)\b/i;
+const AGENT_CREATE_WORK_RE = /\b(triage|check|review|monitor|fetch|pull|scan|audit|sync|compile|summari[sz]e|update|maintain|run|process|organi[sz]e|generate|analy[sz]e|watch|track)\b/i;
+const AGENT_CREATE_DIRECT_RE = /\b(recurring agent|automate|automatically|set up an agent|create an agent|spawn an agent)\b/i;
+export function agentCreateActiveForDm(messageText) {
+    if (!messageText)
+        return false;
+    if (AGENT_CREATE_DIRECT_RE.test(messageText))
+        return true;
+    return (AGENT_CREATE_CADENCE_RE.test(messageText) &&
+        AGENT_CREATE_WORK_RE.test(messageText));
+}
 /**
  * `evening-review-slimdown.md` §2.1 — context-aware manifest resolver.
  *
@@ -754,6 +866,10 @@ export function resolveSkillManifest(eventType, opts) {
             !managedTasksActiveForDm(opts?.db ?? null, opts?.messageText ?? null)) {
             result = result.filter((slug) => slug !== "managed-tasks");
         }
+        if (result.includes("agent-create") &&
+            !agentCreateActiveForDm(opts?.messageText ?? null)) {
+            result = result.filter((slug) => slug !== "agent-create");
+        }
     }
     else if (routineEventsWithGmailLifestyle.has(eventType)) {
         if (result.includes("gmail-lifestyle") &&
@@ -788,4 +904,44 @@ export function getProfileForProcess(processKey) {
 export function getSkillsForProcess(processKey) {
     return getSkillsForEvent(PROCESS_TO_EVENT_TYPE[processKey] ?? processKey);
 }
-//# sourceMappingURL=skills-manifest.js.map
+/**
+ * Compose an Agent definition's `tools.skills` (AGENT_DEFINITIONS_DESIGN.md
+ * §4.2 / `packages/shared/src/agent-definitions.ts` `skills_replace`) with the
+ * process-key default skill bundle. The schema comment promised "the loader
+ * composes the effective set"; this is that composition, applied at session
+ * materialisation (`materializeSessionBundle`) where the skill set is actually
+ * resolved.
+ *
+ * Semantics:
+ *   - `replace === false` (default): union — the default bundle PLUS every
+ *     extra slug not already present. Base order first (so the manifest's
+ *     intentional ordering is preserved), then appended extras.
+ *   - `replace === true`: the extra list is a strict subset that fully
+ *     supplants the default bundle.
+ *   - empty / absent `extra`: pure no-op — returns a copy of `base` unchanged,
+ *     INCLUDING when `replace` is true. An Agent that sets `skills_replace`
+ *     with no `skills` is treated as "no override" rather than "strip every
+ *     skill", because stripping `context` / `notify` from the bundle would
+ *     break the run; callers that want an empty set pass it explicitly and
+ *     the dispatcher gates the override on a non-empty list anyway.
+ *
+ * Output is always deduped (a slug appearing in both base and extra, or twice
+ * in extra, lands once). Unknown slugs are NOT filtered here — the
+ * materialiser skips any slug whose `SKILL.md` is absent on disk, and the
+ * Agent loader already emits an "unknown skill" warning at parse time — so
+ * keeping them keeps the stamp/drift snapshot and this list in agreement.
+ */
+export function composeSkillSet(base, extra, replace) {
+    if (!extra || extra.length === 0)
+        return [...base];
+    const source = replace ? extra : [...base, ...extra];
+    const seen = new Set();
+    const out = [];
+    for (const slug of source) {
+        if (seen.has(slug))
+            continue;
+        seen.add(slug);
+        out.push(slug);
+    }
+    return out;
+}

package/dist/core/system-reset.d.ts

@@ -87,7 +87,7 @@ export declare function resetRuntimeConfig(params: {
 };
 /**
  * Remove everything inside the context directory, including
- * `rules/management.md` — so `/setup/status` flips back to
+ * `policies/management.md` — so `/setup/status` flips back to
  * `needsSetup: true` on the next read.
  *
  * The context directory itself is kept so downstream code that
@@ -290,4 +290,3 @@ export declare function factoryReset(params: {
     secretStore?: SecretStore;
     applyDefaults: () => void;
 }): Promise<FactoryResetResult>;
-//# sourceMappingURL=system-reset.d.ts.map

package/dist/core/system-reset.js

@@ -182,7 +182,7 @@ export function resetRuntimeConfig(params) {
 }
 /**
  * Remove everything inside the context directory, including
- * `rules/management.md` — so `/setup/status` flips back to
+ * `policies/management.md` — so `/setup/status` flips back to
  * `needsSetup: true` on the next read.
  *
  * The context directory itself is kept so downstream code that
@@ -883,4 +883,3 @@ export async function factoryReset(params) {
         errors,
     };
 }
-//# sourceMappingURL=system-reset.js.map

package/dist/core/template-store.d.ts

@@ -43,9 +43,9 @@ export type RetemplateFileStatus = "pending" | "started" | "completed" | "skippe
 export type RetemplateRunStatus = "running" | "success" | "partial" | "failed";
 export interface RetemplateTarget {
     slug: string;
-    /** Relative context path without the trailing `.md` (e.g. `projects/aitne`). */
+    /** Relative context path without the trailing `.md` (e.g. `plans/projects/aitne`). */
     contextPath: string;
-    /** Relative context file with `.md` (e.g. `projects/aitne.md`). */
+    /** Relative context file with `.md` (e.g. `plans/projects/aitne.md`). */
     contextFile: string;
     /** Path inside `backupRoot` mirroring the contextDir layout. */
     backupRelPath: string;
@@ -167,4 +167,3 @@ export declare function safeFileSize(absPath: string): number | undefined;
  * though all callers pass values produced by `selectRetemplateTargets`.
  */
 export declare function resolveContextFilePath(contextDir: string, contextFile: string): string;
-//# sourceMappingURL=template-store.d.ts.map

package/dist/core/template-store.js

@@ -235,10 +235,14 @@ export function prepareRetemplateRun(options) {
         correlationId,
         targets,
     };
+    const retemplateLabel = `Re-conform ${targets.length} ${options.kind === "project" ? "project" : "git-repo"} document(s) to the current ${templateFileName(options.kind)} template.`;
     const insert = options.db.prepare(`INSERT INTO agent_schedule
-       (scheduled_for, task_type, task_description, task_context, correlation_id, model, status)
-     VALUES (?, 'git.project.retemplate', ?, ?, ?, NULL, 'pending')`);
-    const result = insert.run(formatSqliteDatetime(now), `Re-conform ${targets.length} ${options.kind === "project" ? "project" : "git-repo"} document(s) to the current ${templateFileName(options.kind)} template.`, JSON.stringify(taskContext), correlationId);
+       (scheduled_for, task_type, task_description, task_prompt, task_context, correlation_id, model, status)
+     VALUES (?, 'git.project.retemplate', ?, ?, ?, ?, NULL, 'pending')`);
+    const result = insert.run(formatSqliteDatetime(now), 
+    // task_description (label) === task_prompt (agent body); routing is via
+    // task_context.processKey = "git.project.retemplate".
+    retemplateLabel, retemplateLabel, JSON.stringify(taskContext), correlationId);
     const scheduleId = Number(result.lastInsertRowid);
     const record = {
         scheduleId,
@@ -385,4 +389,3 @@ export function resolveContextFilePath(contextDir, contextFile) {
     }
     return abs;
 }
-//# sourceMappingURL=template-store.js.map

package/dist/core/template-versions.d.ts

@@ -20,7 +20,7 @@ import type Database from "better-sqlite3";
  * action.
  *
  * Scope:
- *  - Skip: `today.md`, `roadmap.md`, `projects/_active.base`, and any
+ *  - Skip: `today.md`, `roadmap.md`, `plans/projects/_active.base`, and any
  *    future file without YAML frontmatter (no place to carry the version
  *    marker).
  *  - Skip: files whose user-side copy is missing (user deleted it).
@@ -92,4 +92,3 @@ export declare function readPendingTemplateUpgrades(db: Database.Database): Pend
  * yields an empty list (no action) — see `readTemplateManifest`.
  */
 export declare function checkTemplateUpgrades(db: Database.Database, templatesRoot: string | null, contextDir: string): PendingTemplateUpgrade[];
-//# sourceMappingURL=template-versions.d.ts.map

package/dist/core/template-versions.js

@@ -22,7 +22,7 @@ import { readRuntimeState, writeRuntimeState, } from "../db/runtime-state.js";
  * action.
  *
  * Scope:
- *  - Skip: `today.md`, `roadmap.md`, `projects/_active.base`, and any
+ *  - Skip: `today.md`, `roadmap.md`, `plans/projects/_active.base`, and any
  *    future file without YAML frontmatter (no place to carry the version
  *    marker).
  *  - Skip: files whose user-side copy is missing (user deleted it).
@@ -172,4 +172,3 @@ export function checkTemplateUpgrades(db, templatesRoot, contextDir) {
     writePendingTemplateUpgrades(db, pending);
     return pending;
 }
-//# sourceMappingURL=template-versions.js.map

package/dist/core/today-agent-plan.d.ts

@@ -30,4 +30,3 @@ export declare function normalizeAgentPlanAction(action: string): string;
 export declare function getTodayAgentPlanFingerprint(date: string, row: Pick<TodayAgentPlanRow, "time" | "action" | "category" | "trigger">): string;
 export declare function buildTodayAgentPlanMetadata(date: string, row: Pick<TodayAgentPlanRow, "time" | "action" | "category" | "trigger">): TodayAgentPlanMetadata;
 export declare function readTodayAgentPlanMetadata(taskContext: Record<string, unknown>): TodayAgentPlanMetadata | null;
-//# sourceMappingURL=today-agent-plan.d.ts.map

package/dist/core/today-agent-plan.js

@@ -117,4 +117,3 @@ function isTodayAgentPlanTrigger(value) {
         value === "check-in" ||
         value === "wake");
 }
-//# sourceMappingURL=today-agent-plan.js.map

package/dist/core/today-direct-writer.d.ts

@@ -1,9 +1,15 @@
 /**
- * Daemon-direct writer that appends a single bullet to today.md
- * `## Agent Log` without going through the agent at all. Used by the
- * three-stage hourly_check gate (cost-reduction-structural §B) on the
- * stage0_silent / stage2_log_only paths so a "no-op" cron tick still
- * leaves an audit trail in today.md without paying for an LLM session.
+ * Daemon-direct, lock-aware writes to today.md that run *before* (or
+ * instead of) an agent session — bypassing `/api/context/*` because there
+ * is no subprocess to issue the curl call from. Two operations live here:
+ *
+ *   1. {@link appendAgentLogLine} — append a single `## Agent Log` bullet.
+ *      Used by the three-stage hourly_check gate (cost-reduction-structural
+ *      §B) on the stage0_silent / stage2_log_only paths so a "no-op" cron
+ *      tick still leaves an audit trail without paying for an LLM session.
+ *   2. {@link ensureTodaySkeleton} — seed the canonical empty skeleton when
+ *      today.md is **absent**, so a section-only refresh routine has a valid
+ *      PATCH target instead of 404-ing and budget-burning on full-file PUTs.
  *
  * Why this lives in the daemon (not /api/context/* via curl):
  *   - These paths run *before* the agent is spawned. There is no
@@ -12,15 +18,16 @@
  *     `context-staleness.ts`) — the same tier the PATCH route already
  *     classifies for `## Agent Log` appends. Bypassing the route is
  *     fine because we never touch the prompt-context-changed hook here.
- *   - The today-write-lock invariant is preserved: we acquire it before
- *     mutating the file, so morning_routine and direct writes never
- *     interleave.
- *
- * Failure mode: when today.md is missing, malformed, or lacks the
- * `## Agent Log` heading, the writer logs a warning and returns false
- * rather than synthesizing the structure — that is the morning routine's
- * job. The gate caller treats false as "log not appended; consume
- * observations regardless".
+ *   - The today-write-lock invariant is preserved: both functions acquire
+ *     it before mutating the file, so morning_routine and direct writes
+ *     never interleave.
+ *
+ * Synthesis boundary: `appendAgentLogLine` NEVER synthesizes structure —
+ * a missing / malformed / heading-less file returns false and the gate
+ * caller proceeds. `ensureTodaySkeleton` synthesizes ONLY the empty
+ * skeleton, ONLY when the file is entirely absent, and never touches a
+ * present file. Neither populates today.md — full creation and repair stay
+ * the morning routine's job.
  */
 import type { TodayWriteLockManager } from "./today-write-lock.js";
 export interface AppendAgentLogLineInput {
@@ -49,8 +56,57 @@ export interface AppendAgentLogLineResult {
  * Append a single bullet line to today.md `## Agent Log`. Idempotent
  * shape — repeated calls each add a new bullet (the gate guarantees at
  * most one call per cron tick anyway).
+ *
+ * Async because the read-modify-write block runs inside the daemon-wide
+ * {@link serializeContextFileWrite} so it cannot interleave with the HTTP
+ * Context API's PUT/PATCH on the same today.md file. Without that fence
+ * a concurrent HTTP PATCH could read the pre-bullet bytes, compute its
+ * update, and rename over the file AFTER this writer's rename, silently
+ * dropping the bullet. The cross-session `todayWriteLock` is still
+ * acquired around the serialized block so the morning routine (which
+ * holds the lock + passes X-Lock-Id) continues to fence other direct
+ * writers cleanly.
+ */
+export declare function appendAgentLogLine(input: AppendAgentLogLineInput): Promise<AppendAgentLogLineResult>;
+export interface EnsureTodaySkeletonInput {
+    contextDir: string;
+    todayWriteLock: TodayWriteLockManager;
+}
+export interface EnsureTodaySkeletonResult {
+    seeded: boolean;
+    reason?: "already_present" | "lock_unavailable" | "io_error";
+}
+/**
+ * Guarantee a `today.md` working surface exists before a section-only
+ * refresh routine (`routine.today_refresh`) assumes it.
+ *
+ * `rotateDayFiles()` intentionally renames `today.md` → `yesterday.md` at
+ * the day boundary and relies on the morning routine to recreate the
+ * dated file. When the morning routine has not run yet — or failed (e.g.
+ * a quota/budget death with no fallback backend) — `today.md` is absent
+ * and the refresh task flow's `PATCH section=user_schedule` 404s. The
+ * agent then improvises full-file `PUT`s, which the strict
+ * `validateTodayContent` schema rejects line-by-line; on a single-backend
+ * binding with a tight per-turn budget that loop tips into
+ * `BackendQuotaError(max_budget_usd)` and the refresh dies without ever
+ * writing the file — the "Refresh Today does nothing" symptom.
+ *
+ * This deterministic pre-step removes that whole failure mode: when the
+ * file is **entirely absent** we seed the canonical empty skeleton so the
+ * agent's section PATCH always has a valid target. A file that already
+ * exists is left byte-untouched — a valid dated file OR the legacy
+ * `# Today` bridge stub both accept the section PATCH (the route's
+ * `allowLegacyToday` branch). We never repair a malformed-but-present
+ * file and never overwrite user content; full creation/repair stays the
+ * morning routine's job. The seeded skeleton is dateless (`# Today`), so
+ * it does NOT satisfy `hasCurrentAgentDayTodayMd()` and the pending
+ * morning-routine retry still fires and upgrades it.
+ *
+ * Lock-aware exactly like {@link appendAgentLogLine}: if the morning
+ * routine holds the today-write-lock (mid-creation) we skip and let it
+ * win — the refresh session then 409-defers on its own PATCH.
  */
-export declare function appendAgentLogLine(input: AppendAgentLogLineInput): AppendAgentLogLineResult;
+export declare function ensureTodaySkeleton(input: EnsureTodaySkeletonInput): Promise<EnsureTodaySkeletonResult>;
 /**
  * Splice a new bullet line into the `## Agent Log` section, immediately
  * before the next `## ` heading or end-of-file. Returns null when the
@@ -59,4 +115,3 @@ export declare function appendAgentLogLine(input: AppendAgentLogLineInput): Appe
  * Exported for unit tests; the writer above is the production entry.
  */
 export declare function appendBulletToAgentLog(content: string, bullet: string): string | null;
-//# sourceMappingURL=today-direct-writer.d.ts.map