@aitne/daemon 0.1.8 → 0.1.9

package/dist/core/roadmap-truncate.js

@@ -149,4 +149,3 @@ function extractEntryYmd(entry) {
     const match = headerLine.match(YMD_RE);
     return match ? match[0] : null;
 }
-//# sourceMappingURL=roadmap-truncate.js.map

package/dist/core/roadmap-validate.d.ts

@@ -33,4 +33,3 @@ export declare function findSectionLineBounds(lines: string[], sectionName: stri
     bodyStart: number;
     bodyEnd: number;
 } | null;
-//# sourceMappingURL=roadmap-validate.d.ts.map

package/dist/core/roadmap-validate.js

@@ -208,11 +208,12 @@ function validateAgentActionPlan(lines, bounds, requireIds) {
             continue;
         }
         if (inPreparationTimeline && line.startsWith("- ") && !PREP_ROW_RE.test(line)) {
-            // 2026-05 cost-spike fix: the bare "Malformed Preparation Timeline
-            // row" message gave the agent zero signal about which part of the
-            // row was wrong, so a roadmap_refresh session retried the PUT 8x
-            // before timing out. Embed the canonical shape + the failing line
-            // verbatim so the agent can spot the diff on the next turn.
+            // Without a precise error envelope, the bare "Malformed Preparation
+            // Timeline row" message gives the agent zero signal about which
+            // part of the row was wrong, so a roadmap_refresh session retries
+            // the PUT until it times out. Embed the canonical shape + the
+            // failing line verbatim so the agent can spot the diff on the next
+            // turn.
             //
             // Truncate the received line at 200 chars so a pathological line
             // doesn't blow up the error response.
@@ -349,4 +350,3 @@ function failure(message, line) {
 function error(message, line) {
     return { message, line, path: "roadmap.md" };
 }
-//# sourceMappingURL=roadmap-validate.js.map

package/dist/core/roadmap-write-lock.d.ts

@@ -50,4 +50,3 @@ export declare class InMemoryRoadmapWriteLockManager implements RoadmapWriteLock
  * single long refresh session can never outlive its own lock.
  */
 export declare function getRoadmapWriteLockTimeoutMs(executeTimeoutMinutes: number): number;
-//# sourceMappingURL=roadmap-write-lock.d.ts.map

package/dist/core/roadmap-write-lock.js

@@ -56,4 +56,3 @@ export function getRoadmapWriteLockTimeoutMs(executeTimeoutMinutes) {
         : 60;
     return (normalizedMinutes * 2 + 10) * 60 * 1000;
 }
-//# sourceMappingURL=roadmap-write-lock.js.map

package/dist/core/routine-acquisition-plan.d.ts

@@ -215,4 +215,3 @@ export interface AcquisitionSubPlan {
  * `scoped="<key>"` attribute and the partition itself.
  */
 export declare function splitAcquisitionPlanByIntegration(input: BuildAcquisitionPlanInput): readonly AcquisitionSubPlan[];
-//# sourceMappingURL=routine-acquisition-plan.d.ts.map

package/dist/core/routine-acquisition-plan.js

@@ -455,4 +455,3 @@ export function splitAcquisitionPlanByIntegration(input) {
     }
     return out;
 }
-//# sourceMappingURL=routine-acquisition-plan.js.map

package/dist/core/routine-fetch-window-retry.d.ts

@@ -125,13 +125,12 @@ export declare function cumulativeAttemptCost(report: SubAttemptRecord, priorAtt
  * and retries (the agent fixes the arg name on retry via the
  * prior-attempt-hint).
  *
- * The motivating Unicode-whitespace failure (2026-05-18 gmail pre-pass)
- * lands as `status="partial"` with `posted === 0` and a
- * `{type:"fetch-failed", status:"permission-denied", message:"Bash tool
- * blocked..."}` — rule (4)'s partial-no-post branch sees the
- * deterministic error and short-circuits to `deterministic-failure`
- * instead of burning two more attempts on bytes the SDK will keep
- * rejecting.
+ * A Unicode-whitespace-in-mail-body failure lands as `status="partial"`
+ * with `posted === 0` and a `{type:"fetch-failed",
+ * status:"permission-denied", message:"Bash tool blocked..."}` —
+ * rule (4)'s partial-no-post branch sees the deterministic error and
+ * short-circuits to `deterministic-failure` instead of burning two more
+ * attempts on bytes the SDK will keep rejecting.
  */
 export declare const defaultRetryDecision: RetryDecisionFn;
 /**
@@ -145,4 +144,3 @@ export declare const defaultRetryDecision: RetryDecisionFn;
  * page; deeper history is context-only.
  */
 export declare function buildPriorAttemptHintBlock(attempts: readonly SubAttemptRecord[], integrationKey?: IntegrationKey): string;
-//# sourceMappingURL=routine-fetch-window-retry.d.ts.map

package/dist/core/routine-fetch-window-retry.js

@@ -123,13 +123,12 @@ function isDeterministicError(err) {
  * and retries (the agent fixes the arg name on retry via the
  * prior-attempt-hint).
  *
- * The motivating Unicode-whitespace failure (2026-05-18 gmail pre-pass)
- * lands as `status="partial"` with `posted === 0` and a
- * `{type:"fetch-failed", status:"permission-denied", message:"Bash tool
- * blocked..."}` — rule (4)'s partial-no-post branch sees the
- * deterministic error and short-circuits to `deterministic-failure`
- * instead of burning two more attempts on bytes the SDK will keep
- * rejecting.
+ * A Unicode-whitespace-in-mail-body failure lands as `status="partial"`
+ * with `posted === 0` and a `{type:"fetch-failed",
+ * status:"permission-denied", message:"Bash tool blocked..."}` —
+ * rule (4)'s partial-no-post branch sees the deterministic error and
+ * short-circuits to `deterministic-failure` instead of burning two more
+ * attempts on bytes the SDK will keep rejecting.
  */
 export const defaultRetryDecision = (report, attempt, policy, priorAttempts) => {
     // (1) Attempts cap — the loop body checks this before spawning attempt N+1.
@@ -290,4 +289,3 @@ export function buildPriorAttemptHintBlock(attempts, integrationKey) {
         .map((att) => renderOnePriorAttempt(att, integrationKey))
         .join("\n");
 }
-//# sourceMappingURL=routine-fetch-window-retry.js.map

package/dist/core/routine-fetch-window-runner.d.ts

@@ -360,14 +360,14 @@ export declare class RoutineFetchWindowRunner {
      * the parent event's `event.data.fetchReportBlock` so ContextBuilder
      * injects it into the parent prompt.
      *
-     * `routineKey` overrides the auto-derived window key. The variant
-     * collapse landed in
-     * `docs/design/appendices/morning-routine-optimization.md` Phase 4
-     * + Phase 7: morning_routine no longer toggles to a separate
-     * `routine.morning_routine_initial` (retired 2026-05-16) — both
-     * branches share the same window plan. The override seam is kept
-     * for callers that already know the canonical RoutineWindowKey and
-     * want to skip the event-shape derivation.
+     * `routineKey` overrides the auto-derived window key. After the
+     * variant collapse documented in
+     * `docs/design/appendices/morning-routine-optimization.md`,
+     * morning_routine no longer toggles to a separate
+     * `routine.morning_routine_initial` — both branches share the same
+     * window plan. The override seam is kept for callers that already
+     * know the canonical RoutineWindowKey and want to skip the event-
+     * shape derivation.
      */
     run(parentEvent: Event, routineKey?: RoutineWindowKey, options?: RoutineFetchWindowRunOptions): Promise<RoutineFetchWindowResult>;
     private runImpl;
@@ -458,4 +458,3 @@ export declare class RoutineFetchWindowRunner {
      */
     private collectAccounts;
 }
-//# sourceMappingURL=routine-fetch-window-runner.d.ts.map

package/dist/core/routine-fetch-window-runner.js

@@ -98,6 +98,15 @@ const FETCH_WINDOW_INTEGRATION_PARTIAL_PLACEHOLDER = "{integration_partial}";
  * remains the host/port/exfil chokepoint; this clamp now restricts only
  * the daemon-API namespace, which is what we actually need.
  *
+ * 2026-05-29: the observations-WRITE curl pattern is omitted ENTIRELY on
+ * the Claude backend (see `buildPrePassDaemonRestPatterns`). Claude posts
+ * via the in-process `mcp__aitne-observations__submit_observations` MCP
+ * tool — structured transport, never shell-parsed — the only path that
+ * survives the SDK's `Ae6` Unicode-whitespace bash preflight that
+ * otherwise denies `curl … -d @-` bodies and cascades to `budget-cap`.
+ * The wildcard rationale above still governs the surviving READ curls
+ * (mail/calendar/notion/integrations) and codex/gemini's write curl.
+ *
  * `jq *` stays allowed because direct-mode partials pipe curl output
  * through jq for compact projection before posting to /api/observations.
  *
@@ -106,12 +115,27 @@ const FETCH_WINDOW_INTEGRATION_PARTIAL_PLACEHOLDER = "{integration_partial}";
  * `process_backend_config` envelope (`max_turns=20`, `max_budget_usd=0.50`)
  * remains the floor on those backends.
  */
-function buildPrePassDaemonRestPatterns(apiPort) {
+function buildPrePassDaemonRestPatterns(apiPort, sessionBackend) {
     const root = `http://localhost:${apiPort}/api`;
+    // Observations WRITE surface — the only write the pre-pass performs (GET
+    // reads of pending observations live in the hourly-check session, never
+    // here). For Claude the structured MCP tool
+    // `mcp__aitne-observations__submit_observations` (added by
+    // `composePrePassAllowedTools`) is the ONLY sanctioned write path, so we
+    // deliberately OMIT the curl pattern: a `curl … -d @- <<'JSON'` body whose
+    // calendar titles / mail subjects carry Unicode whitespace (U+3000 in JP
+    // titles, NBSP/ZWS in promo subjects) makes the SDK's `Ae6` bash preflight
+    // mark the command `too-complex` ("Contains Unicode whitespace") and deny
+    // it under dontAsk — which the runner then retries until it trips the
+    // per-integration `budget-cap`. Dropping the curl allow-rule forces Claude
+    // onto the MCP transport (structured JSON, never shell-parsed) and closes
+    // that failure class. codex/gemini have no MCP transport, so they retain
+    // the curl pattern (accepted gap — see `composePrePassAllowedTools`).
+    const observationsWrite = sessionBackend === "claude"
+        ? []
+        : [`Bash(curl *${root}/observations*)`];
     return [
-        // Observations — the only write surface the pre-pass touches.
-        // Catches both POST /api/observations and GET /api/observations*.
-        `Bash(curl *${root}/observations*)`,
+        ...observationsWrite,
         // Direct-mode mail / calendar / notion reads.
         `Bash(curl *${root}/mail/*)`,
         `Bash(curl *${root}/calendar/*)`,
@@ -257,10 +281,10 @@ export function composePrePassAllowedTools(apiPort, integrations, sessionBackend
     const needsDeferredDiscovery = sessionBackend === "claude" && integrationTools.length > 0;
     // In-process MCP tool `mcp__aitne-observations__submit_observations` is
     // the structural fix for the Unicode-whitespace-in-curl-body class of
-    // failures (2026-05-18 gmail incident: Amazon promo + NBSP/ZWS in the
-    // subject caused the SDK's `Ae6` bash preflight to mark the command
-    // `too-complex` and deny it under dontAsk, burning 3 attempts +
-    // surfacing budget-cap). Server is registered in-process by
+    // failures (promotional senders + NBSP/ZWS in mail subjects cause the
+    // SDK's `Ae6` bash preflight to mark the command `too-complex` and
+    // deny it under dontAsk, burning attempts and surfacing budget-cap).
+    // Server is registered in-process by
     // `ClaudeCodeCore.getObservationsMcpServer`; per-session exposure is
     // controlled here. Claude-only because the SDK MCP transport is
     // Claude-specific; codex/gemini pre-pass sessions retain the curl
@@ -269,7 +293,7 @@ export function composePrePassAllowedTools(apiPort, integrations, sessionBackend
     // parallel structured channel).
     const observationsMcpTools = sessionBackend === "claude" ? [OBSERVATIONS_MCP_TOOL_NAME] : [];
     return [
-        ...buildPrePassDaemonRestPatterns(apiPort),
+        ...buildPrePassDaemonRestPatterns(apiPort, sessionBackend),
         ...integrationTools,
         ...observationsMcpTools,
         ...(needsDeferredDiscovery ? ["ToolSearch"] : []),
@@ -810,14 +834,14 @@ export class RoutineFetchWindowRunner {
      * the parent event's `event.data.fetchReportBlock` so ContextBuilder
      * injects it into the parent prompt.
      *
-     * `routineKey` overrides the auto-derived window key. The variant
-     * collapse landed in
-     * `docs/design/appendices/morning-routine-optimization.md` Phase 4
-     * + Phase 7: morning_routine no longer toggles to a separate
-     * `routine.morning_routine_initial` (retired 2026-05-16) — both
-     * branches share the same window plan. The override seam is kept
-     * for callers that already know the canonical RoutineWindowKey and
-     * want to skip the event-shape derivation.
+     * `routineKey` overrides the auto-derived window key. After the
+     * variant collapse documented in
+     * `docs/design/appendices/morning-routine-optimization.md`,
+     * morning_routine no longer toggles to a separate
+     * `routine.morning_routine_initial` — both branches share the same
+     * window plan. The override seam is kept for callers that already
+     * know the canonical RoutineWindowKey and want to skip the event-
+     * shape derivation.
      */
     async run(parentEvent, routineKey, options) {
         // B2 observability — announce pre-pass entry so the dashboard can
@@ -1811,4 +1835,3 @@ export class RoutineFetchWindowRunner {
         return rows;
     }
 }
-//# sourceMappingURL=routine-fetch-window-runner.js.map

package/dist/core/routine-windows.d.ts

@@ -6,11 +6,7 @@
  * fetcher (`routine.fetch_window`) and its assembly helper (§6.4)
  * consult to build the `<acquisition-plan>` block.
  *
- * Phase 1 ships the catalog only. The dispatcher hooks that consume it
- * land in Phase 4; the partials that use the `WINDOW_QUERIES` strings
- * land in Phase 2.
- *
- * Design invariants preserved here:
+ * Design invariants:
  *
  *  - **No model IDs.** Routine windows describe *what to fetch*; tier
  *    binding for `routine.fetch_window` lives in
@@ -48,11 +44,10 @@ export type WindowSymbol = (typeof WINDOW_SYMBOLS)[number];
  * acquisition appear here.
  *
  * `routine.morning_routine_initial` was retired by
- * `docs/design/appendices/morning-routine-optimization.md` Phase 7
- * (2026-05-16). Both the recurring and first-run branches now flow
- * through `routine.morning_routine`; the daemon-prepared
- * `<roadmap_skeleton>` block (not a window fetch) handles the
- * first-run roadmap populate.
+ * `docs/design/appendices/morning-routine-optimization.md`. Both the
+ * recurring and first-run branches now flow through
+ * `routine.morning_routine`; the daemon-prepared `<roadmap_skeleton>`
+ * block (not a window fetch) handles the first-run roadmap populate.
  */
 export declare const ROUTINE_WINDOW_KEYS: readonly ["routine.morning_routine", "routine.today_refresh", "routine.hourly_check", "routine.evening_review", "routine.weekly_review", "routine.monthly_review"];
 export type RoutineWindowKey = (typeof ROUTINE_WINDOW_KEYS)[number];
@@ -172,4 +167,3 @@ export declare function lookupWindowQuery(symbol: WindowSymbol, integration: Int
  * covered by ContextBuilder blocks (today: `monthly_review`).
  */
 export declare function routineHasWindows(key: RoutineWindowKey): boolean;
-//# sourceMappingURL=routine-windows.d.ts.map

package/dist/core/routine-windows.js

@@ -6,11 +6,7 @@
  * fetcher (`routine.fetch_window`) and its assembly helper (§6.4)
  * consult to build the `<acquisition-plan>` block.
  *
- * Phase 1 ships the catalog only. The dispatcher hooks that consume it
- * land in Phase 4; the partials that use the `WINDOW_QUERIES` strings
- * land in Phase 2.
- *
- * Design invariants preserved here:
+ * Design invariants:
  *
  *  - **No model IDs.** Routine windows describe *what to fetch*; tier
  *    binding for `routine.fetch_window` lives in
@@ -48,8 +44,8 @@ export const WINDOW_SYMBOLS = [
     // with the matching `ROUTINE_WINDOWS` row.
     "cal_next_24h_drift",
     // `cal_iso_week_to_now` — weekly_review's calendar retrospective.
-    // Renamed from `cal_past_7d` 2026-05-17: the previous semantics was a
-    // rolling 7-day window ending at `now`, which (a) silently included
+    // Previously named `cal_past_7d` with rolling-7-day-ending-at-now
+    // semantics, which (a) silently included
     // last week's Fri–Sun events that did not appear in any current-ISO-week
     // daily/*.md file, forcing the agent to disambiguate, and (b) misaligned
     // the direct-mode UTC `date+days` shape with the delegated/native
@@ -60,8 +56,8 @@ export const WINDOW_SYMBOLS = [
     // same set of days across all three modes.
     "cal_iso_week_to_now",
     "imminent_2h",
-    // morning_routine's 7-day calendar fetch — A8 / Finding 5 (2026-05-13).
-    // ContextBuilder's `<calendar_events_7d>` covers `direct` mode inline,
+    // morning_routine's 7-day calendar fetch. ContextBuilder's
+    // `<calendar_events_7d>` covers `direct` mode inline,
     // but emits a "fetch yourself" directive for `delegated` / `native`
     // modes — which forces the main routine session (Sonnet) to drive the
     // MCP fan-out and burn medium-tier turns on a fetch the Haiku pre-pass
@@ -79,11 +75,10 @@ export const WINDOW_SYMBOLS = [
  * acquisition appear here.
  *
  * `routine.morning_routine_initial` was retired by
- * `docs/design/appendices/morning-routine-optimization.md` Phase 7
- * (2026-05-16). Both the recurring and first-run branches now flow
- * through `routine.morning_routine`; the daemon-prepared
- * `<roadmap_skeleton>` block (not a window fetch) handles the
- * first-run roadmap populate.
+ * `docs/design/appendices/morning-routine-optimization.md`. Both the
+ * recurring and first-run branches now flow through
+ * `routine.morning_routine`; the daemon-prepared `<roadmap_skeleton>`
+ * block (not a window fetch) handles the first-run roadmap populate.
  */
 export const ROUTINE_WINDOW_KEYS = [
     "routine.morning_routine",
@@ -147,8 +142,8 @@ export const ROUTINE_WINDOWS = {
         { kind: "calendar", window: "cal_morning_7d", perAccount: false },
         { kind: "notion", window: "updated_24h", perAccount: false },
     ],
-    // `routine.morning_routine_initial` retired by Phase 7 (2026-05-16);
-    // its plan was identical to `routine.morning_routine` above.
+    // `routine.morning_routine_initial` is retired — its plan was identical
+    // to `routine.morning_routine` above.
     "routine.today_refresh": [
         { kind: "calendar", window: "cal_next_24h_drift", perAccount: false },
     ],
@@ -214,9 +209,9 @@ export const WINDOW_QUERIES = {
     // Gmail noise filter (`-category:promotions -category:social`) is baked
     // into every inbox-windowing query. Promotional and social-network
     // emails account for the majority of unread volume in most accounts and
-    // are deterministic to identify (Gmail labels them server-side). The
-    // 2026-05-18 incident that triggered this design — Amazon promo with
-    // an NBSP in the subject — is exactly the kind of payload that's both
+    // are deterministic to identify (Gmail labels them server-side).
+    // Promotional payloads (Amazon promo with NBSP in the subject is a
+    // representative case) are exactly the kind of payload that's both
     // (a) noise the user doesn't want triaged and (b) likely to carry
     // shell-fragile Unicode whitespace. Filtering at the FETCH boundary
     // means the agent never sees these messages at all: zero cost, zero
@@ -313,10 +308,10 @@ export const WINDOW_QUERIES = {
     },
     // `cal_iso_week_to_now` — weekly_review retrospective spanning the
     // current ISO week's Monday 00:00 local through `now`. Direct mode uses
-    // `timeMin`/`timeMax` (added 2026-05-17 to `/api/calendar/events` for
-    // exactly this row) so the daemon REST path returns the same window the
-    // delegated/native MCP fan-out sees. Before the rename this row used a
-    // UTC `date+days=7` shape, which (a) silently dropped current-day events
+    // `timeMin`/`timeMax` on `/api/calendar/events` so the daemon REST
+    // path returns the same window the delegated/native MCP fan-out sees.
+    // Before the rename this row used a UTC `date+days=7` shape, which
+    // (a) silently dropped current-day events
     // for non-UTC timezones (the window ended at today's UTC midnight, i.e.
     // 09:00 JST) and (b) drifted away from the ISO week boundary that
     // `daily/YYYY-MM-DD.md` is keyed on.
@@ -416,4 +411,3 @@ export function routineHasWindows(key) {
 // the wrong abstraction. ContextBuilder's call-sites pass an explicit
 // `prepassCovers` flag instead, derived from local knowledge of
 // which window they are constructing.
-//# sourceMappingURL=routine-windows.js.map

package/dist/core/schedule-insert-helper.d.ts

@@ -43,4 +43,3 @@ export declare function shouldTriggerRoadmapRefresh(input: TriggerDecisionInput)
  * run without it.
  */
 export declare function maybeTriggerRoadmapRefresh(input: TriggerDecisionInput, triggerRoadmapRefresh: ((source: string) => void) | null | undefined, source: string): void;
-//# sourceMappingURL=schedule-insert-helper.d.ts.map

package/dist/core/schedule-insert-helper.js

@@ -49,4 +49,3 @@ export function maybeTriggerRoadmapRefresh(input, triggerRoadmapRefresh, source)
         logger.warn({ err, source }, "triggerRoadmapRefresh threw — continuing");
     }
 }
-//# sourceMappingURL=schedule-insert-helper.js.map

package/dist/core/schedule-maintenance.d.ts

@@ -19,4 +19,3 @@ export declare function discardStalePendingSchedules(db: Database.Database, curr
  */
 export declare function recoverOrphanedRunningSchedules(db: Database.Database, currentAgentDayStartUtc: string): OrphanedRunningRecoveryResult;
 export declare function hasActionInWindow(db: Database.Database, actionType: string, startUtc: string, endUtc: string): boolean;
-//# sourceMappingURL=schedule-maintenance.d.ts.map

package/dist/core/schedule-maintenance.js

@@ -54,4 +54,3 @@ export function hasActionInWindow(db, actionType, startUtc, endUtc) {
         .get(actionType, startUtc, endUtc);
     return !!row;
 }
-//# sourceMappingURL=schedule-maintenance.js.map

package/dist/core/scheduler.d.ts

@@ -2,6 +2,7 @@ import type Database from "better-sqlite3";
 import type { AgentConfig } from "../config.js";
 import type { EventBus } from "./event-bus.js";
 import type { MessageDelivery } from "../adapters/message-hub.js";
+import type { AgentEnabledCache } from "./agents/loader.js";
 /**
  * Build the cron expression that drives the hourly check.
  *
@@ -75,6 +76,16 @@ export declare const USER_PROFILE_SWEEP_EVENING_CRON_EXPR = "50 17 * * *";
  * `docs/design/appendices/evening-review-slimdown.md` §2.2.
  */
 export declare const ROADMAP_MAINTENANCE_CRON_EXPR = "45 17 * * *";
+/**
+ * Cron expression for the BROWSER_HISTORY_INTEGRATION_PLAN §5.F2 P4a
+ * pre-morning digest: 60 min before the day boundary, wrapping
+ * backward across midnight (so `dayBoundaryHour = 4` → "0 3 * * *",
+ * `dayBoundaryHour = 0` → "0 23 * * *"). Extracted as a pure helper
+ * so the wrap arithmetic — identical in shape to
+ * `buildUserProfileSweepMorningCronExpr` but at the top of the hour —
+ * is asserted without standing up node-cron in tests.
+ */
+export declare function buildBrowserHistoryPreMorningDigestCronExpr(dayBoundaryHour: number): string;
 /**
  * AgentScheduler — manages recurring cron jobs and the DB-driven ScheduleWatcher.
  *
@@ -133,6 +144,20 @@ export declare class AgentScheduler {
      * agent/journal.md append.
      */
     private onRoadmapMaintenance;
+    /**
+     * BROWSER_HISTORY_INTEGRATION_PLAN §5.F2 P4a — pre-morning digest
+     * builder. Fires at `dayBoundaryHour − 1` local each night so the
+     * morning Stage B journal reads a static `context/browser/yesterday-<date>.md`
+     * file (pre-warmed) rather than calling `GET /api/browser-history/
+     * yesterday-summary` at 04:00. The callback is deterministic Node
+     * code (no LLM in the path); the scheduler treats it as
+     * fire-and-forget like the roadmap-maintenance and context-index
+     * callbacks above. A failure here logs but never cascades into the
+     * 04:00 morning routine — the journal task-flow has a documented
+     * fallback to the `/api/browser-history/pre-morning-digest/{date}`
+     * endpoint.
+     */
+    private onBrowserHistoryPreMorningDigest;
     /**
      * Setup gate — returns a skip reason when autonomous work should be
      * paused (initial setup incomplete, or setup conversation active).
@@ -142,6 +167,13 @@ export declare class AgentScheduler {
      */
     private autonomousGate;
     private lastGateBlockLoggedAt;
+    /**
+     * AGENT_DEFINITIONS_DESIGN.md §7.1 — per-built-in enabled gate. Wired from
+     * the Phase-7 boot path via {@link setAgentEnabledCache}; until then (and in
+     * tests that construct a bare scheduler) it is `null` and the gate is a
+     * no-op, so disabling is opt-in and never accidentally stops a routine.
+     */
+    private agentEnabledCache;
     /**
      * Single source of truth for the ScheduleWatcher's between-poll wake
      * signaling, unifying what was previously a (pollAbort: AbortController
@@ -202,11 +234,38 @@ export declare class AgentScheduler {
      * evening_review.
      */
     setRoadmapMaintenanceCallback(fn: () => void): void;
+    /**
+     * Register the BROWSER_HISTORY_INTEGRATION_PLAN §5.F2 P4a
+     * pre-morning digest cron callback. Fires at `dayBoundaryHour − 1`
+     * local; the callback is fire-and-forget — it builds the digest
+     * from `browser_visits` / `browser_research_clusters` /
+     * `browser_pending_offers` and writes the markdown + JSON sidecar
+     * into the daemon-owned `context/browser/` directory. Failures
+     * inside the callback log but do not throw outward.
+     */
+    setBrowserHistoryPreMorningDigestCallback(fn: () => void): void;
     /**
      * Register the autonomous-work gate. Returning null allows autonomous work;
      * any non-null string is treated as a skip reason and surfaced in logs.
      */
     setAutonomousGate(fn: () => null | string): void;
+    /**
+     * Wire the live built-in enabled cache (AGENT_DEFINITIONS_DESIGN.md §7.1).
+     * The loader watcher + the `PATCH /api/agents/:slug` handler call
+     * `cache.invalidate()` so the next firing re-queries the DB.
+     */
+    setAgentEnabledCache(cache: AgentEnabledCache): void;
+    /**
+     * Per-built-in enabled gate (§7.1), checked BEFORE `autonomousGate()` in
+     * every built-in routine's cron callback. Returns `true` to proceed; on a
+     * disabled Agent returns `false` and records a throttled `agent.firing_blocked`
+     * audit row (one per agent-day, then `detail.suppressed_count++` — §12.3). It
+     * is placed AFTER each callback's runtime gates (monthly last-day, hourly
+     * interval, skill-curation cadence) so a per-minute hourly tick that is not a
+     * real firing never inflates the suppressed count. A `null` cache (unwired /
+     * tests) always proceeds.
+     */
+    private isAgentEnabledForFiring;
     /** Log gate blocks at most once every 5 minutes to avoid spam. */
     private logGateBlock;
     /**
@@ -337,4 +396,3 @@ export declare class AgentScheduler {
     /** Daily cleanup: expire sessions, run retention */
     private dailyCleanup;
 }
-//# sourceMappingURL=scheduler.d.ts.map