@genesislcap/ai-assistant 15.12.0 → 15.13.0

package/dist/custom-elements.json

@@ -367,6 +367,14 @@
             "module": "./utils/sum-usage"
           }
         },
+        {
+          "kind": "js",
+          "name": "messageUsage",
+          "declaration": {
+            "name": "messageUsage",
+            "module": "./utils/sum-usage"
+          }
+        },
         {
           "kind": "js",
           "name": "sumUsage",
@@ -447,6 +455,14 @@
             "module": "./state/persistence/diagnostics"
           }
         },
+        {
+          "kind": "js",
+          "name": "withFreshMetaSnapshot",
+          "declaration": {
+            "name": "withFreshMetaSnapshot",
+            "module": "./state/persistence/diagnostics"
+          }
+        },
         {
           "kind": "js",
           "name": "DebugLog",
@@ -4075,7 +4091,7 @@
                   "text": "DebugLog"
                 }
               },
-              "description": "The live current-page debug log (`{ readme, timeline, meta }`). @public"
+              "description": "The live current-page debug log (`{ readme, sessionUsage, timeline, meta }`). @public"
             },
             {
               "kind": "method",
@@ -4088,6 +4104,17 @@
               },
               "description": "Build the current page's diagnostic entries (GENC-1351 §5.8) — the debug-log\ntimeline entries (`message`/`turn`/`event`) plus one `meta-snapshot` carrying\nthe export-time `meta` block. `getDebugLog()` reassembles these into the live\nlog; the persister's forward-capture path (`SessionPersister.flushDiagnostics`,\nfed these via the `getDiagnosticEntries` dep) diffs them against what's already\nbeen appended to the persisted stream."
             },
+            {
+              "kind": "method",
+              "name": "buildMetaSnapshot",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "DiagnosticEntry"
+                }
+              },
+              "description": "The single `meta-snapshot` entry for right now — the export-time `meta` block\n(agent summary, active prompt/state, context + cost) plus the `dedupSignature`\nthe forward-capture delta keys on.\n\nSeparate from `buildDiagnosticEntries` because the download path needs a\nFRESH one on its own: the persisted stream only re-appends this block when the\nnear-static config changes, so the newest stored snapshot's volatile half — the\n`context` figures especially — is typically frozen at the session's first flush."
+            },
             {
               "kind": "method",
               "name": "downloadDebugLog",
@@ -4106,7 +4133,7 @@
                   "text": "Promise<DebugLog>"
                 }
               },
-              "description": "The log to download (GENC-1351 §5.8). When the provider persists diagnostics,\nstitch the **whole lifetime** stream (every page load) rather than just the\ncurrent page's in-memory view: flush the current delta first so it's included,\nthen reassemble everything `loadDiagnostics` returns. Independent of \"remember\nchat\" — diagnostics are a forensic stream keyed on provider capability, not on\nwhether the *chat* is remembered (like preferences). Falls back to the live\ncurrent-page log when diagnostics isn't available or the fetch fails."
+              "description": "The log to download (GENC-1351 §5.8). When the provider persists diagnostics,\nstitch the **whole lifetime** stream (every page load) rather than just the\ncurrent page's in-memory view: flush the current delta first so it's included,\nthen reassemble everything `loadDiagnostics` returns. Independent of \"remember\nchat\" — diagnostics are a forensic stream keyed on provider capability, not on\nwhether the *chat* is remembered (like preferences). Falls back to the live\ncurrent-page log when diagnostics isn't available or the fetch fails.\n\nThe stored `meta-snapshot`s are replaced by a fresh one (`withFreshMetaSnapshot`)\nbefore reassembly. The persisted stream only re-appends that block when the\nnear-static config signature changes (see `collectDiagnosticsDelta`), so on a session\nwhose config never changes the newest STORED snapshot is the first one — its\n`context` half (session cost/usage, context tokens, live agent state) frozen seconds\ninto the session, which is how a lifetime log came out reporting near-zero spend\nagainst a transcript full of priced messages."
             },
             {
               "kind": "method",
@@ -4649,48 +4676,6 @@
         }
       ]
     },
-    {
-      "kind": "javascript-module",
-      "path": "src/provider/ai-provider-switcher.ts",
-      "declarations": [
-        {
-          "kind": "variable",
-          "name": "AIProviderSwitcher",
-          "description": "The DI token for the (AIProviderSwitcher:interface). Resolves a noop until the app\nregisters one."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "AIProviderSwitcher",
-          "declaration": {
-            "name": "AIProviderSwitcher",
-            "module": "src/provider/ai-provider-switcher.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/provider/assistant-app-settings.ts",
-      "declarations": [
-        {
-          "kind": "variable",
-          "name": "AssistantAppSettingsProvider",
-          "description": "The DI token for the (AssistantAppSettingsProvider:interface). Resolves a noop\nuntil the host registers one."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "AssistantAppSettingsProvider",
-          "declaration": {
-            "name": "AssistantAppSettingsProvider",
-            "module": "src/provider/assistant-app-settings.ts"
-          }
-        }
-      ]
-    },
     {
       "kind": "javascript-module",
       "path": "src/state/ai-assistant-slice.ts",
@@ -4916,7 +4901,7 @@
           "type": {
             "text": "readonly string[]"
           },
-          "default": "[\n  'This is an exported debug log for the Genesis AI assistant. Read it top-to-bottom.',\n  '`timeline` is the entire session as one array, already sorted chronologically by `timestamp` (ISO 8601). Every entry has a `kind`.',\n  'Timestamps are millisecond-resolution; entries that share the same millisecond are ordered by a fixed kind rank (event, then turn, then message), which is a heuristic and may not reflect exact causal order within that millisecond — e.g. a user message and the turn it triggered, or a final assistant message and its turn.end event, can appear in either order depending on whether they landed in the same millisecond. Read the logical structure of a turn rather than over-interpreting the micro-ordering of co-timestamped entries of different kinds.',\n  \"kind:'message' — the conversation. `role` is user/assistant/tool/system-event/synthetic-user; `agentName` says which agent produced it; `toolCalls`/`toolResult`/`interaction` carry tool and widget activity; `inputTokens`/`outputTokens`/`cost` are per-message LLM usage, where `inputTokens` is the WHOLE prompt for that request and `cacheReadTokens`/`cacheWriteTokens` BREAK IT DOWN rather than add to it — uncached input is `inputTokens` minus those two, and adding the cache fields to `inputTokens` counts the prompt twice. The cache fields are absent on providers that report no cache split (Gemini reports reads only, since implicit caching bills no write) and on messages persisted before they existed, so read them as 0 when missing. Each bucket bills at a different rate — cache reads a fraction of uncached input, cache writes a premium, output highest — so a large token count at a small cost means the prompt was mostly cache hits. `externalCostUsd` is any non-LLM cost a widget reported for its own external service calls (folded into the session cost total alongside `cost`). On model-produced assistant messages, `model` is the concrete model id that generated it (e.g. 'gemini-2.5-flash-lite') and `providerName` is the registry slot it resolved under (e.g. a tier name like 'high'/'low', or the default); together they attribute the message — and any tool calls it carries — to an exact model even across a mid-session vendor/tier switch, where one slot name can map to different models before and after the switch. Both are undefined on any entry that is NOT an LLM response: non-assistant roles (user/tool/system-event) and 'synthetic-user' echoes; assistant interaction/widget entries (empty content carrying an `interaction` — a rendered widget, not a model turn); driver-authored assistant fallbacks (the timeout, repeated-malformed-call, and empty-response apology messages); and messages restored from a session persisted before these fields existed. One partial case: on a genuine model turn whose provider exposes no `getStatus` (or reports no model), `providerName` is still set but `model` alone is undefined. A 'synthetic-user' message is a display-only echo of an interaction outcome (e.g. the answer a widget reported): it renders on the user's side of the chat and `agentName` is the agent that created it, but it is never sent to the LLM — so it has no matching 'turn' and the model learns the outcome only from the corresponding tool result.\",\n  \"Sub-agent messages appear inline. When a tool delegates to a sub-agent (via `requestSubAgent`), the sub-agent's whole conversation — its own assistant/tool messages, each with their own `content`/`thinking`/`toolCalls`/`toolResult` and per-message `model`/`providerName`/`inputTokens`/`outputTokens`/`cacheReadTokens`/`cacheWriteTokens`/`cost` — is hoisted into the timeline as ordinary kind:'message' entries, interleaved by timestamp right after the tool call that spawned them (so you read the delegation top-to-bottom). A hoisted entry is marked: `subAgentDepth` is its delegation depth (1 for a sub-agent, 2 for a sub-agent's sub-agent, …), `subAgentOf` is the id of the parent tool call that spawned it (correlates it back even when two sub-agents run in one parent turn), `subAgentName` is the sub-agent's own name, and `agentName` is rewritten to a `\\\"<parent> › <sub-agent>\\\"` breadcrumb (composing when nested, e.g. `\\\"UI Builder › Planner › Grounding\\\"`). The sub-agent's per-LLM-call snapshots also surface as kind:'turn' entries with an N-M `turnIndex`, and subagent.started/completed (or subagent.failed) events bracket the run. Per-message `cost` on hoisted entries is already part of the session total (it is summed from the un-flattened history), so summing the top-level timeline does NOT double-count.\",\n  \"kind:'turn' — one LLM call. `turnIndex` is a string: a top-level turn is the bare counter ('0', '1', …); a sub-agent's turns are numbered under the parent turn that activated them ('3-1', '3-2', …, and a nested sub-agent contributes '3-2-1', …), and `agentName` names the agent that ran the turn. `systemPrompt` and `toolNames` are what the model saw. A systemPrompt of '<repeated — identical to turn N>' was byte-identical to turn N and de-duplicated; the full prompt is shown whenever it changes (often because a stateful agent advanced), so prompt evolution is visible.\",\n  \"kind:'turn'.`agentSnapshot` — the active agent's own view of its internal state, captured at that turn. An agent opts into this by exposing a `getDebugSnapshot()` that returns JSON-serializable per-state info; stateful/flow agents wire it automatically, so you can watch a flow advance turn-by-turn (e.g. current step, cursor, collected fields, pending changes). Absent for agents that don't expose one.\",\n  \"kind:'event' — a meta/lifecycle event. `type` names it (see below); `detail` carries structured data. `detail.placement` is the emitting UI instance: 'bubble' (collapsed), 'panel' (popped-out), or 'standalone'.\",\n  \"Each 'event' also has an `importance`: 'high' (failures/limits — turn.error, tool.failed, subagent.failed, file.read-failed, suggestions.failed, context.threshold-crossed), 'normal' (session flow — connects, turns, retries, handoffs, agent/provider changes, interactions, sub-agent start/complete), or 'low' (skippable UI/bookkeeping noise — panel.toggled, attachment.added, driver.wired/unwired, context.updated, context.condensed). To skim, ignore importance:'low'; to triage a failure, filter to importance:'high' then read the nearby messages and turns. A 'high' turn.error is often preceded by one or more 'normal' turn.retry events for the same reason — read them together to see how many attempts were made before bailing. 'message' and 'turn' entries carry no importance — they are the substance, always read them.\",\n  'Event types: assistant.connected/disconnected (mount + placement + whether the session was created or restored), assistant.popout/popin (window placement), driver.created/wired/unwired (which driver is live and why it stops/starts responding across a popout), state.changed (idle↔loading), turn.start/turn.end (turn boundary; turn.end carries durationMs), turn.retry (a recoverable in-turn retry — detail.reason plus attempt/maxAttempts; for malformed calls also finishMessage; for empty responses also the provider finishReason + thoughtsTokens + parts breakdown), turn.error (a turn failed or hit a guardrail — detail.reason is one of exception/malformed-function-call/empty-response/unknown-tool-limit/max-iterations/response-truncated/refusal/budget-exhausted, plus reason-specific diagnostics: attempts (for empty-response also finishReason + thoughtsTokens + a parts breakdown, distinguishing a thinking-only STOP from a truly empty turn), finishMessage, for response-truncated the model + maxTokens + outputTokens + tools, unknownTools (split into staleTools — real earlier this activation but retired by the current state or hidden behind an open exclusive fold — and hallucinatedTools — never advertised) + availableTools, iterations + limit, for budget-exhausted the budgetUsd + spentUsd figures reported by the proxy plus the resolved vendor, or name + message for exceptions), tool.failed (a tool threw), tool.unresolved (the model called a tool that could not be dispatched — detail.kind is folded/fold-hidden/stale/unknown, plus tool + agent and, for the counted kinds, the consecutive streak; the recurring lead-up to an unknown-tool-limit turn.error), subagent.started/completed/failed (the lifecycle of a `requestSubAgent` delegation — detail.agent names the sub-agent; these bracket the sub-agent turns that appear as kind:turn entries with an N-M `turnIndex`; subagent.failed also carries detail.reason, one of max_iterations/malformed_tool_call/empty_response/unknown_tool_limit/timeout/response_truncated/refusal/budget_exhausted; budget_exhausted is terminal for the PARENT turn too — the parent stops rather than calling the model again into the same wall), agent.handoff (routing; from=null is the initial activation), agent.pinned/unpinned (forced routing), provider.selected (model/provider for the upcoming turns), interaction.requested/resolved (blocking user widgets — explain quiet gaps; note that when a sub-agent opens a widget, detail.agent — and the agentName on the interaction message — is the HOST agent that owns the widget, NOT the sub-agent that asked, because widgets render and resolve on the host driver), context.updated/threshold-crossed (token + cost), context.condensed (a stale tool payload was collapsed out of the model-bound history by a `condenseWhen` declaration on the tool — detail.tool + toolCallId, target args|response, trigger (superseded:<key> or age:<n>), stubLen, and an estimated tokensSaved; stored history and this log keep the FULL payload, so the model-visible slice at any point is the full history minus the condensations recorded up to then), panel.toggled, attachment.added, file.read-failed, suggestions.failed.',\n  'Sub-agent meta events: a sub-agent\\'s own turn.retry/turn.error/tool.failed/tool.unresolved events are merged into this same timeline, tagged with `detail.subAgent` — a `\"<parent> › <sub-agent>\"` breadcrumb that composes when nested (e.g. `\"UI Builder › Planner › Grounding\"`) — and interleaved by their original timestamps within the subagent.started→completed/failed bracket. These are the per-attempt/per-failure signals that do NOT appear among the sub-agent\\'s (hoisted) messages: a malformed/empty attempt that gets retried produces no message, and the stale-vs-hallucinated split and streak counts live only on the event. A sub-agent\\'s high-volume, message-derivable events (turn.start/turn.end, provider.selected, context.updated) are intentionally NOT merged — read its hoisted messages for model/tokens/cost and turn-by-turn activity, and the bracketing subagent.* events for the run\\'s span.',\n  \"`meta` holds context captured at export time: agentSummary (full agent configs), context (active model, token usage, session cost), activeDebugSnapshot (the active agent's `getDebugSnapshot()` taken fresh at export — reflects state NOW, which may have advanced beyond the last turn's agentSnapshot), debug (optional host-supplied debug state), host, and the export timestamp.\",\n  'To debug a failure: find the last turn.error or tool.failed, then read upward for the user message, the turn(s), and the agent/provider/state events that led into it.',\n]",
+          "default": "[\n  'This is an exported debug log for the Genesis AI assistant. Read it top-to-bottom.',\n  \"`sessionUsage` is what this session spent: `costUsd` (USD, provider-reported per request and summed, cache discounts already applied) plus the four TOKEN BUCKETS — `uncachedInputTokens`, `cacheReadTokens`, `cacheWriteTokens`, `outputTokens`. Those four are disjoint and safe to add up for a total-tokens figure; the per-message fields further down are NOT (see kind:'message'). Each bucket bills at a different rate — cache reads a fraction of uncached input, cache writes a premium, output highest — so a big token count against a small cost means the prompt was mostly cache hits, not a missing charge. It covers sub-agent turns and spend a compaction banked, so for the CONVERSATION it is the authoritative total: prefer it over re-summing the timeline, which can be short by whatever the ring buffers evicted. The same figures appear under `meta.context`. It is as current as the snapshot it came from: the assistant's own download stamps a fresh one, but a log stitched by another tool can carry an older one — compare `meta.timestamp` with the last timeline entry, and if it is well behind, read these totals as historical and fall back to summing the timeline. One scope caveat: it is derived from the transcript, so it excludes billed calls that produced no message (a blank or refused attempt that was retried — see kind:'turn'.`usage`). Summing the turns can therefore come out HIGHER than this, and the difference is exactly that discarded spend, not a double-count.\",\n  \"What 'session' means for those figures: the CURRENT conversation under this session key (a host-supplied per-project id, or the element id + header title when the host supplies none) — which is not necessarily everything in `timeline`. It is re-derived from the live transcript, so it spans page loads only when the chat is being remembered, and a Clear resets it to zero. `timeline` is append-only regardless: it keeps every page load and the pre-Clear conversation, with the session.cleared event as the boundary. So on a long-lived log, read these totals as the latest conversation's and the earlier sections as history — not as a total of the whole file.\",\n  '`timeline` is the entire session as one array, already sorted chronologically by `timestamp` (ISO 8601). Every entry has a `kind`.',\n  'Timestamps are millisecond-resolution; entries that share the same millisecond are ordered by a fixed kind rank (event, then turn, then message), which is a heuristic and may not reflect exact causal order within that millisecond — e.g. a user message and the turn it triggered, or a final assistant message and its turn.end event, can appear in either order depending on whether they landed in the same millisecond. Read the logical structure of a turn rather than over-interpreting the micro-ordering of co-timestamped entries of different kinds.',\n  \"kind:'message' — the conversation. `role` is user/assistant/tool/system-event/synthetic-user; `agentName` says which agent produced it; `toolCalls`/`toolResult`/`interaction` carry tool and widget activity; `inputTokens`/`outputTokens`/`cost` are per-message LLM usage, where `inputTokens` is the WHOLE prompt for that request and `cacheReadTokens`/`cacheWriteTokens` BREAK IT DOWN rather than add to it — uncached input is `inputTokens` minus those two, and adding the cache fields to `inputTokens` counts the prompt twice. The cache fields are absent on providers that report no cache split (Gemini reports reads only, since implicit caching bills no write) and on messages persisted before they existed, so read them as 0 when missing. Each bucket bills at a different rate — cache reads a fraction of uncached input, cache writes a premium, output highest — so a large token count at a small cost means the prompt was mostly cache hits. `externalCostUsd` is any non-LLM cost a widget reported for its own external service calls (folded into the session cost total alongside `cost`). On model-produced assistant messages, `model` is the concrete model id that generated it (e.g. 'gemini-2.5-flash-lite') and `providerName` is the registry slot it resolved under (e.g. a tier name like 'high'/'low', or the default); together they attribute the message — and any tool calls it carries — to an exact model even across a mid-session vendor/tier switch, where one slot name can map to different models before and after the switch. Both are undefined on any entry that is NOT an LLM response: non-assistant roles (user/tool/system-event) and 'synthetic-user' echoes; assistant interaction/widget entries (empty content carrying an `interaction` — a rendered widget, not a model turn); driver-authored assistant fallbacks (the timeout, repeated-malformed-call, and empty-response apology messages); and messages restored from a session persisted before these fields existed. One partial case: on a genuine model turn whose provider exposes no `getStatus` (or reports no model), `providerName` is still set but `model` alone is undefined. A 'synthetic-user' message is a display-only echo of an interaction outcome (e.g. the answer a widget reported): it renders on the user's side of the chat and `agentName` is the agent that created it, but it is never sent to the LLM — so it has no matching 'turn' and the model learns the outcome only from the corresponding tool result.\",\n  \"Sub-agent messages appear inline. When a tool delegates to a sub-agent (via `requestSubAgent`), the sub-agent's whole conversation — its own assistant/tool messages, each with their own `content`/`thinking`/`toolCalls`/`toolResult` and per-message `model`/`providerName`/`inputTokens`/`outputTokens`/`cacheReadTokens`/`cacheWriteTokens`/`cost` — is hoisted into the timeline as ordinary kind:'message' entries, interleaved by timestamp right after the tool call that spawned them (so you read the delegation top-to-bottom). A hoisted entry is marked: `subAgentDepth` is its delegation depth (1 for a sub-agent, 2 for a sub-agent's sub-agent, …), `subAgentOf` is the id of the parent tool call that spawned it (correlates it back even when two sub-agents run in one parent turn), `subAgentName` is the sub-agent's own name, and `agentName` is rewritten to a `\\\"<parent> › <sub-agent>\\\"` breadcrumb (composing when nested, e.g. `\\\"UI Builder › Planner › Grounding\\\"`). The sub-agent's per-LLM-call snapshots also surface as kind:'turn' entries with an N-M `turnIndex`, and subagent.started/completed (or subagent.failed) events bracket the run. Per-message `cost` on hoisted entries is already part of the session total (it is summed from the un-flattened history), so summing the top-level timeline does NOT double-count.\",\n  \"kind:'turn' — one LLM call. `turnIndex` is a string: a top-level turn is the bare counter ('0', '1', …); a sub-agent's turns are numbered under the parent turn that activated them ('3-1', '3-2', …, and a nested sub-agent contributes '3-2-1', …), and `agentName` names the agent that ran the turn. `systemPrompt` and `toolNames` are what the model saw. A systemPrompt of '<repeated — identical to turn N>' was byte-identical to turn N and de-duplicated; the full prompt is shown whenever it changes (often because a stateful agent advanced), so prompt evolution is visible.\",\n  \"kind:'turn'.`model`/`providerName`/`provider` — which model ran that call: the concrete model id, the registry slot it resolved under (a tier name like 'high'/'low', or the default), and the vendor. Recorded per CALL, so an agent whose `provider` selector varies by state — a flow that plans on a high tier and executes on a low one — has every step attributed, including calls that produced no message. `model` is the SERVING model where the provider reports one, so a turn answered by a server-side fallback names the model that answered rather than the one requested; it always matches the `model` on the message that call produced. Absent when the provider exposes no `getStatus` and the transport stamped nothing.\",\n  \"kind:'turn'.`usage` — what that ONE call cost, in the same four-bucket + `costUsd` shape as `sessionUsage`. Absent while a call is in flight and on providers that report no usage. This is the SAME money as the message the call produced, not extra money: never add turn usage to message usage, and read a turn plus its message as one charge. Its distinct value is the calls that produced NO message — a blank or refused response is billed and then discarded before the retry, so the turn entry is the only record of that spend, and a turn with `usage` but no message after it is exactly that. `costUsd: 0` alongside a nonzero token count means the provider reported no price, not that the call was free.\",\n  \"kind:'turn'.`agentSnapshot` — the active agent's own view of its internal state, captured at that turn. An agent opts into this by exposing a `getDebugSnapshot()` that returns JSON-serializable per-state info; stateful/flow agents wire it automatically, so you can watch a flow advance turn-by-turn (e.g. current step, cursor, collected fields, pending changes). Absent for agents that don't expose one.\",\n  \"kind:'event' — a meta/lifecycle event. `type` names it (see below); `detail` carries structured data. `detail.placement` is the emitting UI instance: 'bubble' (collapsed), 'panel' (popped-out), or 'standalone'.\",\n  \"Each 'event' also has an `importance`: 'high' (failures/limits — turn.error, tool.failed, subagent.failed, file.read-failed, suggestions.failed, context.threshold-crossed), 'normal' (session flow — connects, turns, retries, handoffs, agent/provider changes, interactions, sub-agent start/complete), or 'low' (skippable UI/bookkeeping noise — panel.toggled, attachment.added, driver.wired/unwired, context.updated, context.condensed). To skim, ignore importance:'low'; to triage a failure, filter to importance:'high' then read the nearby messages and turns. A 'high' turn.error is often preceded by one or more 'normal' turn.retry events for the same reason — read them together to see how many attempts were made before bailing. 'message' and 'turn' entries carry no importance — they are the substance, always read them.\",\n  'Event types: assistant.connected/disconnected (mount + placement + whether the session was created or restored), assistant.popout/popin (window placement), driver.created/wired/unwired (which driver is live and why it stops/starts responding across a popout), state.changed (idle↔loading), turn.start/turn.end (turn boundary; turn.end carries durationMs), turn.retry (a recoverable in-turn retry — detail.reason plus attempt/maxAttempts; for malformed calls also finishMessage; for empty responses also the provider finishReason + thoughtsTokens + parts breakdown), turn.error (a turn failed or hit a guardrail — detail.reason is one of exception/malformed-function-call/empty-response/unknown-tool-limit/max-iterations/response-truncated/refusal/budget-exhausted, plus reason-specific diagnostics: attempts (for empty-response also finishReason + thoughtsTokens + a parts breakdown, distinguishing a thinking-only STOP from a truly empty turn), finishMessage, for response-truncated the model + maxTokens + outputTokens + tools, unknownTools (split into staleTools — real earlier this activation but retired by the current state or hidden behind an open exclusive fold — and hallucinatedTools — never advertised) + availableTools, iterations + limit, for budget-exhausted the budgetUsd + spentUsd figures reported by the proxy plus the resolved vendor, or name + message for exceptions), tool.failed (a tool threw), tool.unresolved (the model called a tool that could not be dispatched — detail.kind is folded/fold-hidden/stale/unknown, plus tool + agent and, for the counted kinds, the consecutive streak; the recurring lead-up to an unknown-tool-limit turn.error), subagent.started/completed/failed (the lifecycle of a `requestSubAgent` delegation — detail.agent names the sub-agent; these bracket the sub-agent turns that appear as kind:turn entries with an N-M `turnIndex`; subagent.failed also carries detail.reason, one of max_iterations/malformed_tool_call/empty_response/unknown_tool_limit/timeout/response_truncated/refusal/budget_exhausted; budget_exhausted is terminal for the PARENT turn too — the parent stops rather than calling the model again into the same wall), agent.handoff (routing; from=null is the initial activation), agent.pinned/unpinned (forced routing), provider.selected (the resolved provider for the upcoming turns — detail.provider is the registry SLOT/tier name, detail.model the concrete model behind it and detail.vendor its vendor; emitted only when the slot CHANGES, so read the per-turn `model` for the model of any given call rather than assuming the nearest event still applies), interaction.requested/resolved (blocking user widgets — explain quiet gaps; note that when a sub-agent opens a widget, detail.agent — and the agentName on the interaction message — is the HOST agent that owns the widget, NOT the sub-agent that asked, because widgets render and resolve on the host driver), context.updated/threshold-crossed (token + cost), context.condensed (a stale tool payload was collapsed out of the model-bound history by a `condenseWhen` declaration on the tool — detail.tool + toolCallId, target args|response, trigger (superseded:<key> or age:<n>), stubLen, and an estimated tokensSaved; stored history and this log keep the FULL payload, so the model-visible slice at any point is the full history minus the condensations recorded up to then), panel.toggled, attachment.added, file.read-failed, suggestions.failed.',\n  'Sub-agent meta events: a sub-agent\\'s own turn.retry/turn.error/tool.failed/tool.unresolved events are merged into this same timeline, tagged with `detail.subAgent` — a `\"<parent> › <sub-agent>\"` breadcrumb that composes when nested (e.g. `\"UI Builder › Planner › Grounding\"`) — and interleaved by their original timestamps within the subagent.started→completed/failed bracket. These are the per-attempt/per-failure signals that do NOT appear among the sub-agent\\'s (hoisted) messages: a malformed/empty attempt that gets retried produces no message, and the stale-vs-hallucinated split and streak counts live only on the event. A sub-agent\\'s high-volume, message-derivable events (turn.start/turn.end, provider.selected, context.updated) are intentionally NOT merged — read its hoisted messages for model/tokens/cost and turn-by-turn activity, and the bracketing subagent.* events for the run\\'s span.',\n  \"`meta` holds context captured at export time: agentSummary (full agent configs), context (active model, contextTokens/contextLimit/contextUsagePercent for the last call, and the session totals — sessionCostUsd, sessionTokensConsumed, and the four-bucket sessionUsage lifted to the top of this log), activeDebugSnapshot (the active agent's `getDebugSnapshot()` taken fresh at export — reflects state NOW, which may have advanced beyond the last turn's agentSnapshot), debug (optional host-supplied debug state), host, and the export timestamp.\",\n  'Note the two different scopes in `meta.context`: `contextTokens` is the prompt size of the LAST call (against `contextLimit`, the model context window), while `sessionUsage`/`sessionTokensConsumed` are cumulative BILLED throughput. Every turn resends the conversation, so the cumulative figure counts each turn’s prompt again in the next turn’s and is expected to dwarf the context size — that is not double-counting.',\n  'To debug a failure: find the last turn.error or tool.failed, then read upward for the user message, the turn(s), and the agent/provider/state events that led into it.',\n]",
           "description": "Human/agent-facing guide emitted as the first key of the exported debug log,\nso whoever opens the JSON (often an AI agent) knows how to read it without\nreverse-engineering the shape. Kept here next to the event catalogue it\ndescribes — but proximity alone demonstrably did NOT keep the two in sync\n(`refusal` was missing from both reason lists for a whole release), so\n`debug-event-log.test.ts` now asserts that every `TurnFailureReason` and every\n`SubAgentFailureReason` is named here, and fails the build when one is added\nwithout a matching sentence. Enumerations below read as exhaustive and WILL be\ntrusted by an agent reading the JSON — keep them so."
         }
       ],
@@ -5429,6 +5414,48 @@
       "declarations": [],
       "exports": []
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/provider/ai-provider-switcher.ts",
+      "declarations": [
+        {
+          "kind": "variable",
+          "name": "AIProviderSwitcher",
+          "description": "The DI token for the (AIProviderSwitcher:interface). Resolves a noop until the app\nregisters one."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "AIProviderSwitcher",
+          "declaration": {
+            "name": "AIProviderSwitcher",
+            "module": "src/provider/ai-provider-switcher.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/provider/assistant-app-settings.ts",
+      "declarations": [
+        {
+          "kind": "variable",
+          "name": "AssistantAppSettingsProvider",
+          "description": "The DI token for the (AssistantAppSettingsProvider:interface). Resolves a noop\nuntil the host registers one."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "AssistantAppSettingsProvider",
+          "declaration": {
+            "name": "AssistantAppSettingsProvider",
+            "module": "src/provider/assistant-app-settings.ts"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "src/types/ai-chat-widget.ts",
@@ -6557,6 +6584,24 @@
           ],
           "description": "`a + b`, per bucket, as a new object.\n\nUsed to lay a row's banked (pre-transcript) spend over what the live transcript\nproves. Pure rather than in-place because both operands are live state a caller\nmust not mutate."
         },
+        {
+          "kind": "function",
+          "name": "messageUsage",
+          "return": {
+            "type": {
+              "text": "AggregateUsage | undefined"
+            }
+          },
+          "parameters": [
+            {
+              "name": "m",
+              "type": {
+                "text": "ChatMessage"
+              }
+            }
+          ],
+          "description": "The four buckets plus USD for ONE message — the per-message fields projected into\nthe disjoint, addable shape, or `undefined` when the message reports no usage at\nall (a user turn, a display-only reasoning/narration split, a provider that\nreports none).\n\nShallow by design: it does NOT recurse into `toolCalls[].subAgentTrace` and does\nNOT count `compaction.rolledUpUsage`, so it answers \"what did this one request\ncost\" rather than \"what did this message and everything under it cost\". Use\nsumUsage for the latter — passing a whole transcript through this one\nmessage at a time would silently drop both.\n\n`costUsd` folds in `externalCostUsd` (non-LLM spend a widget reported), matching\n`sumUsage`. It is `0` when the provider priced nothing, which is NOT a claim that\nthe call was free — see AggregateUsage; `UsageRow.costUsd` is the\nshape that keeps unpriced distinguishable, and is the right tool for a ledger."
+        },
         {
           "kind": "function",
           "name": "sumUsage",
@@ -6601,6 +6646,14 @@
             "module": "src/utils/sum-usage.ts"
           }
         },
+        {
+          "kind": "js",
+          "name": "messageUsage",
+          "declaration": {
+            "name": "messageUsage",
+            "module": "src/utils/sum-usage.ts"
+          }
+        },
         {
           "kind": "js",
           "name": "sumUsage",
@@ -8639,7 +8692,7 @@
               "privacy": "private",
               "return": {
                 "type": {
-                  "text": "void"
+                  "text": "TurnSnapshot"
                 }
               },
               "parameters": [
@@ -8668,7 +8721,7 @@
                   }
                 }
               ],
-              "description": "Push one snapshot to the ring buffer. Called inside `runToolLoop` just\nbefore each LLM call — that's the latest point where the prompt, tool\nsurface, and agent state line up with what the model is about to see."
+              "description": "Push one snapshot to the ring buffer. Called inside `runToolLoop` just\nbefore each LLM call — that's the latest point where the prompt, tool\nsurface, and agent state line up with what the model is about to see.\n\nReturns the pushed object so the caller can back-fill what only the response\nknows (`usage`). Mutating it after the fact is safe whether or not the ring\nbuffer has since evicted it — an evicted snapshot is simply no longer exported."
             },
             {
               "kind": "method",
@@ -10178,333 +10231,114 @@
     },
     {
       "kind": "javascript-module",
-      "path": "src/components/popout-manager/index.ts",
+      "path": "src/components/settings-modal/index.ts",
       "declarations": [],
       "exports": [
         {
           "kind": "js",
-          "name": "*",
+          "name": "SettingsModalTemplate",
           "declaration": {
-            "name": "*",
-            "package": "./popout-manager"
+            "name": "SettingsModalTemplate",
+            "module": "./settings-modal.template"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "type",
+          "declaration": {
+            "name": "type",
+            "module": "./settings-modal.template"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "SettingsModalTab",
+          "declaration": {
+            "name": "SettingsModalTab",
+            "module": "./settings-modal.template"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "settingsModalStyles",
+          "declaration": {
+            "name": "settingsModalStyles",
+            "module": "./settings-modal.styles"
           }
         }
       ]
     },
     {
       "kind": "javascript-module",
-      "path": "src/components/popout-manager/popout-manager.ts",
+      "path": "src/components/settings-modal/settings-modal.styles.ts",
       "declarations": [
         {
-          "kind": "class",
-          "description": "App-shell component that owns the pop-out/pop-in lifecycle for the AI assistant bubble.",
-          "name": "FoundationAiPopoutManager",
-          "members": [
-            {
-              "kind": "field",
-              "name": "canDock",
-              "type": {
-                "text": "boolean"
-              },
-              "default": "false",
-              "description": "True when a dock provider is registered — controls expand button visibility."
-            },
-            {
-              "kind": "field",
-              "name": "assistantEl",
-              "type": {
-                "text": "HTMLElement | null"
-              },
-              "privacy": "private",
-              "default": "null",
-              "description": "The single assistant element. Captured while it's in the bubble slot and held\nacross the move (it's the same instance whether docked or in the bubble), so\npop-in can re-home it even though it's no longer a child of this manager."
-            },
+          "kind": "variable",
+          "name": "settingsModalStyles",
+          "default": "css`\n  /*\n   * Section headings come from the shared fragment the package also exports, so a host titling\n   * its own slotted section applies the same rule rather than a copy of it.\n   */\n  ${assistantSettingsSectionTitleStyles}\n\n  *,\n  *::before,\n  *::after {\n    box-sizing: border-box;\n  }\n\n  .settings-modal {\n    --ai-tier-badge-bg-mix: 14%;\n    --ai-tier-badge-text-lighten: 18%;\n  }\n\n  .settings-modal::part(dialog) {\n    max-width: 620px;\n    width: calc(100vw - 48px);\n    max-height: calc(100vh - 48px);\n    padding: 0;\n  }\n\n  .settings-modal::part(content) {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    padding: 0;\n    width: 100%;\n  }\n\n  .settings-modal::part(top) {\n    padding: calc(var(--design-unit) * 4px) calc(var(--design-unit) * 5px);\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal::part(bottom) {\n    padding: calc(var(--design-unit) * 4px) calc(var(--design-unit) * 5px);\n    border-top: 1px solid var(--neutral-stroke-rest);\n    border-bottom-left-radius: var(--card-border-radius, calc(var(--control-corner-radius) * 1px));\n    border-bottom-right-radius: var(--card-border-radius, calc(var(--control-corner-radius) * 1px));\n    background-color: var(--neutral-layer-2);\n  }\n\n  .settings-modal-header {\n    display: flex;\n    align-items: center;\n    min-width: 0;\n  }\n\n  .settings-modal-title {\n    margin: 0;\n    font-size: 16px;\n    font-weight: 600;\n    display: flex;\n    align-items: center;\n    gap: calc(var(--design-unit) * 2px);\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-modal-content {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    flex: 1 1 auto;\n  }\n\n  .settings-modal-tabs::part(tablist) {\n    border-bottom: 0;\n    padding: 0 calc(var(--design-unit) * 5px);\n    column-gap: calc(var(--design-unit) * 5px);\n  }\n\n  .settings-modal-tabs::part(activeIndicator) {\n    height: 2px;\n  }\n\n  .settings-modal-tab {\n    padding: 0;\n    font-weight: 600;\n    gap: 6px;\n  }\n\n  .settings-modal-tab[aria-selected='true'] {\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-modal-tabs::part(tabpanel) {\n    border-top: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal-tab-panel {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    flex: 1 1 auto;\n    padding: 0;\n    border-radius: 0;\n  }\n\n  .settings-modal-tab-panel[hidden] {\n    display: none !important;\n  }\n\n  .settings-modal-body {\n    overflow-y: auto;\n    padding: 0 calc(var(--design-unit) * 5px) calc(var(--design-unit) * 2px);\n    max-height: min(60vh, 520px);\n  }\n\n  .settings-modal-section {\n    padding: calc(var(--design-unit) * 5px) 0;\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal-section:last-child {\n    border-bottom: none;\n  }\n\n  /*\n   * Only the spacing. Everything else about this heading comes from the exported fragment\n   * above, which the assistant and its hosts share; margin is deliberately not in there,\n   * since the gap below a heading depends on the layout around it.\n   */\n  .ai-settings-section-title {\n    margin: 0 0 calc(var(--design-unit) * 3px);\n  }\n\n  .settings-modal-section-note {\n    margin: calc(var(--design-unit) * -2px) 0 calc(var(--design-unit) * 3px);\n    font-size: 12px;\n    line-height: 1.5;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-modal-section-body {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-toggle-row {\n    display: flex;\n    align-items: flex-start;\n    gap: calc(var(--design-unit) * 3px);\n    padding: 0 0 calc(var(--design-unit) * 4px) 0;\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-toggle-row:last-child {\n    border-bottom: none;\n    padding-bottom: calc(var(--design-unit) * 1px);\n  }\n\n  .settings-toggle-row.is-stacked {\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * For rows whose control is a button rather than a switch. The base row top-aligns, which suits\n   * a switch (it lands level with the title), but a button is tall enough that top-aligning leaves\n   * it above the title-plus-description block it acts on.\n   */\n  .settings-toggle-row.is-centered {\n    align-items: center;\n  }\n\n  .settings-animation-list {\n    display: flex;\n    flex-direction: column;\n    width: 100%;\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.2px);\n    padding: calc(var(--design-unit) * 2px);\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-animation-list .settings-toggle-row {\n    border: 0;\n  }\n\n  .settings-animation-category {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-animation-category-label {\n    font-weight: 600;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-toggle-row + .settings-animation-category-label {\n    border-top: 1px solid var(--neutral-stroke-rest);\n    padding-top: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-animation-option {\n    padding: 0;\n    margin: 0;\n  }\n\n  .settings-animation-option:last-child {\n    border-bottom: none;\n    padding-bottom: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-toggle-text {\n    flex: 1;\n    min-width: 0;\n  }\n\n  .settings-toggle-title {\n    font-size: 14px;\n    font-weight: 500;\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-toggle-desc {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    line-height: 1.5;\n    max-width: 92%;\n  }\n\n  .settings-toggle-control {\n    flex: 0 0 auto;\n    min-width: 0;\n  }\n\n  .settings-toggle-control-wide {\n    width: 100%;\n    max-width: 280px;\n  }\n\n  .settings-toggle-row.is-stacked .settings-toggle-desc {\n    max-width: none;\n  }\n\n  .settings-toggle-row.is-stacked .settings-toggle-control-wide {\n    width: 100%;\n    max-width: none;\n  }\n\n  /*\n   * Sub-heading over the provider toggle group. Unlike the section headings it sits INSIDE\n   * .settings-modal-section-body, so the parent's 4-unit flex gap already separates it from the\n   * first toggle — and flex does not collapse margins, so the shared rule's 3-unit margin-bottom\n   * would add to that gap rather than replace it, leaving the label adrift from the rows it\n   * names. Zero the margin and pull back 2 of the 4 gap units, expressed in the same token so it\n   * tracks if that gap changes.\n   */\n  .settings-app-toggles-title {\n    margin: 0 0 calc(var(--design-unit) * -2px);\n  }\n\n  .settings-app-toggle-block {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 1px);\n  }\n\n  .settings-toggle-hint {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    line-height: 1.4;\n    padding-left: calc(var(--design-unit) * 1px);\n    font-style: italic;\n  }\n\n  /*\n   * The budget meter (GENC-1464) is the context indicator's money sibling and\n   * shares its row anatomy 1:1, so the budget classes JOIN these rules rather\n   * than restating them — one place to restyle the header/label/figures shape,\n   * and the two indicators cannot drift apart. Design-system tokens only, and\n   * unfallbacked: every token here ships a DS default, so a var(--x, y)\n   * fallback would be dead code that hides a broken token name (#2411/#2436\n   * review rule, pinned by settings-modal.styles.test.ts).\n   */\n  .settings-context-header,\n  .settings-budget-header {\n    display: flex;\n    justify-content: space-between;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 2px);\n    font-size: 12px;\n  }\n\n  .settings-context-label,\n  .settings-budget-label {\n    color: var(--neutral-foreground-hint);\n    font-size: 11px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n  }\n\n  .settings-context-tokens,\n  .settings-budget-figures {\n    color: var(--neutral-foreground-rest);\n  }\n\n  /* Freshness footer (GENC-1464): refresh button + label under the vendor\n     rows, left-aligned — a footnote to the figures above it. The button's\n     inline padding is pinned and cancelled by the container margin so the\n     ICON GLYPH (not the button box) sits flush with the budget labels'\n     left edge, whatever the density tokens say. */\n  .settings-budget-toolbar {\n    display: flex;\n    justify-content: flex-start;\n    align-items: center;\n    gap: 4px;\n    margin-inline-start: -4px;\n  }\n\n  .settings-budget-refresh::part(control) {\n    padding-inline: 4px;\n  }\n\n  .settings-budget-updated {\n    color: var(--neutral-foreground-hint);\n    font-size: 11px;\n  }\n\n  /*\n   * ONE rhythm for every meter row. The outer wrapper holds the context\n   * indicator and the budget meter; the inner one holds the budget meter's\n   * vendor rows — and both gap by the same 2 units (half the section body's 4)\n   * so that visually identical meter rows are evenly spaced whatever mix of\n   * them is on screen. Without the wrapper the context row inherits the body's\n   * 4-unit gap while the vendor rows keep 2, and three identical-looking rows\n   * read as an uneven 4/2/2. The wrapper renders only when at least one meter\n   * does — see settingsUsageMetersTemplate for why an always-on one would cost\n   * a stray gap.\n   */\n  .settings-usage-meters,\n  .settings-budget-usage {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-current-build,\n  .settings-lifetime-usage {\n    background: var(--neutral-layer-2);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.5px);\n    padding: calc(var(--design-unit) * 4px);\n    margin: calc(var(--design-unit) * 3px) 0;\n  }\n\n  /*\n   * Deliberately quieter than the live block: no pulsing badge and no accent, so the eye lands\n   * on what is being built now — which is why that block leads the tab and this one follows,\n   * under the history heading whose rows it totals.\n   */\n  .settings-lifetime-usage-top {\n    display: flex;\n    align-items: center;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-lifetime-label {\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 700;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-current-build-top {\n    display: flex;\n    align-items: center;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  /*\n   * Optically centring these 10px caps against the 14px project name beside them. Flex offers\n   * only two alignments and neither lands it, because a box centre and a text baseline are\n   * different lines:\n   *   - align-items: center   sits the badge baseline about 1.2px high\n   *   - align-items: baseline matches baselines, but the caps then read as bottom-aligned\n   *     against the name's ascenders, so the badge looks low\n   * The eye wants the midpoint, so: centre the boxes, then translate down by the ~1px of\n   * overshoot. This is a nudge, but it corrects a fixed relationship between two font sizes\n   * rather than some neighbouring element's layout, so unlike a margin tuned to a sibling it\n   * cannot rot when that sibling changes. In em, so it tracks the badge text.\n   *\n   * display: block, not inline-flex: a flex container has no text baseline of its own and\n   * synthesizes one from its first child, which here is the dot, an empty span. As a block box\n   * the badge takes the baseline of its first line, i.e. the text.\n   */\n  .settings-live-badge {\n    display: block;\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 700;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--accent-fill-rest);\n    white-space: nowrap;\n    transform: translateY(0.1em);\n  }\n\n  .settings-live-dot {\n    display: inline-block;\n    width: 7px;\n    height: 7px;\n\n    /* Replaces the flex gap the badge no longer has. */\n    margin-right: calc(var(--design-unit) * 1px);\n\n    /* Centres the dot on the text beside it without disturbing that text's baseline. */\n    vertical-align: middle;\n    border-radius: 50%;\n    background: var(--accent-fill-rest);\n    animation: settings-live-pulse 1.6s ease-out infinite;\n  }\n\n  @keyframes settings-live-pulse {\n    0% {\n      box-shadow: 0 0 0 0 color-mix(in srgb, var(--accent-fill-rest) 55%, transparent);\n    }\n\n    70% {\n      box-shadow: 0 0 0 7px transparent;\n    }\n\n    100% {\n      box-shadow: 0 0 0 0 transparent;\n    }\n  }\n\n  .settings-current-build-name {\n    font-size: 14px;\n    line-height: 1;\n    font-weight: 600;\n  }\n\n  /*\n   * Cost and the token buckets side by side: one number in its own box, the four buckets\n   * sharing the box next to it. Stretch, so the two are the same height however tall the 22px\n   * cost value makes the left one.\n   */\n  .settings-usage-row {\n    display: flex;\n    flex-wrap: wrap;\n    align-items: stretch;\n    gap: calc(var(--design-unit) * 3px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-usage-row-tokens {\n    display: flex;\n    flex: 1 1 auto;\n    min-width: 0;\n  }\n\n  .settings-build-stat {\n    min-width: 0;\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1px);\n    padding: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-build-stat-label {\n    font-size: 10px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-build-stat-value {\n    font-size: 22px;\n    font-weight: 700;\n    margin-top: calc(var(--design-unit) * 1px);\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-build-stat-value .prefix,\n  .settings-build-stat-value .suffix {\n    color: var(--accent-fill-rest);\n  }\n\n  /*\n   * Per-bucket token split, beneath the headline cost. Small paired label/value cells\n   * rather than four more stat cards: they are the detail behind the cost above, so they\n   * have to read as subordinate to it rather than compete with it. The four buckets ARE\n   * the token figure now — there is no merged total anywhere for them to break down.\n   */\n  .settings-token-breakdown {\n    display: flex;\n    flex-direction: column;\n\n    /*\n     * Tight against the buckets below. One design unit rather than two, because each bucket\n     * separates its own label from its value by only 2px — at two units the title sat four\n     * times further from the bucket labels than they sit from their own numbers, which read\n     * as a gap between unrelated blocks instead of a heading over its content.\n     */\n    gap: calc(var(--design-unit) * 1px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n    padding: calc(var(--design-unit) * 2px) calc(var(--design-unit) * 3px);\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1px);\n  }\n\n  /*\n   * Titles the box, because nothing else in it named the unit. Same styling and position as\n   * the cost box's label, so two boxes sitting side by side are titled the same way; the\n   * hierarchy against the bucket labels comes from position, not a second type size.\n   */\n  .settings-token-breakdown-label {\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-token-buckets {\n    display: flex;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-token-bucket {\n    display: flex;\n\n    /*\n     * min-content (not 0) so a bucket cannot be shrunk narrower than its own unbreakable label.\n     * With the label set to nowrap, a zero minimum would overflow it into the next column instead\n     * of wrapping — so the container's flex-wrap takes over and moves a bucket to a second row,\n     * which is the degradation we want when the modal is dragged narrow.\n     */\n    min-width: min-content;\n    flex-direction: column;\n    gap: 2px;\n  }\n\n  .settings-token-bucket-label {\n    font-size: 10px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n\n    /*\n     * One line, always. The rate marker is a separate inline box after collapsible whitespace, so\n     * a wrappable label gives it a break opportunity of its own — in a narrow column it orphaned\n     * onto line 2, which also pushed that bucket's value a line below the other three and broke\n     * the row of figures. nowrap removes every break opportunity in the label, the space before\n     * the marker included, so no glue character is needed.\n     */\n    white-space: nowrap;\n  }\n\n  .settings-token-bucket-value {\n    font-size: 13px;\n    font-weight: 600;\n    color: var(--neutral-foreground-rest);\n  }\n\n  /*\n   * The price-direction marker on a cache bucket's label — down for reads (a fraction of the\n   * uncached input rate), up for writes (a premium over it). Three tiers, so a bucket with no\n   * marker is the reference rate rather than an unlabelled fourth case.\n   *\n   * Carried by the label rather than the value, which is what this used to do: cache reads are\n   * usually the largest bucket by a wide margin in an agentic session, so the value was muted to\n   * stop the biggest number reading as the dominant cost driver. That priced the treatment to the\n   * wrong thing — a dimmed 0 (every Gemini cache write) looked disabled next to a normal 0, and a\n   * rate is a property of the bucket, not of this turn's figure.\n   *\n   * Sized down and nudged up rather than tinted: the label is already the hint colour, so a\n   * dimmer marker would vanish and a brighter one would out-shout the word it qualifies.\n   */\n  .settings-token-bucket-rate {\n    font-size: 8px;\n    line-height: 1;\n    vertical-align: 0.15em;\n    letter-spacing: 0;\n  }\n\n  /*\n   * Usage-row overrides. Placed after the base rules they refine rather than up beside\n   * .settings-usage-row itself, because stylelint's no-descending-specificity rejects a\n   * compound selector appearing before the plain one it overrides.\n   */\n\n  /* Sized by its content; the buckets take the rest, since four cells need the width. */\n  .settings-usage-row > .settings-build-stat {\n    flex: 0 1 auto;\n  }\n\n  .settings-usage-row .settings-token-breakdown {\n    flex: 1 1 auto;\n\n    /* The row owns the spacing now; this centres the column against the taller cost box. */\n    justify-content: center;\n    margin-bottom: 0;\n  }\n\n  /*\n   * Basis auto, not 0: a zero basis splits the row into four equal columns, so CACHE WRITE is\n   * squeezed exactly as hard as INPUT despite being twice the label. Sizing from content gives the\n   * long labels the room their text needs and lets the short ones concede it, which is what makes\n   * white-space: nowrap above safe — every column starts at least as wide as its own content,\n   * then shares the slack. Still grows and shrinks, so the four stay flush edge to edge.\n   */\n  .settings-usage-row .settings-token-bucket {\n    flex: 1 1 auto;\n  }\n\n  .settings-model-tags {\n    display: flex;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-model-tag {\n    font-size: 11px;\n    font-weight: 600;\n    padding: 3px 9px;\n    border-radius: 20px;\n    font-family: ui-monospace, monospace;\n    border: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-model-tag,\n  .settings-cost-history-icon {\n    --model-tag-color: var(--neutral-foreground-rest);\n\n    background: color-mix(\n      in srgb,\n      var(--model-tag-color) var(--ai-tier-badge-bg-mix),\n      var(--neutral-layer-1)\n    );\n    border-color: color-mix(in srgb, var(--model-tag-color) 20%, var(--neutral-layer-1));\n    color: color-mix(in srgb, var(--model-tag-color), white var(--ai-tier-badge-text-lighten));\n  }\n\n  .settings-cost-history-title {\n    font-size: 11px;\n    text-transform: uppercase;\n    letter-spacing: 0.08em;\n    color: var(--neutral-foreground-hint);\n    font-weight: 600;\n    margin: calc(var(--design-unit) * 4px) 0 calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * The heading labels the lifetime card as well as the rows, so the card gives up its own top\n   * margin and the gap becomes the heading's alone. Adjacent siblings collapse to the LARGER of\n   * the two margins, so leaving both would space the caps 3 units off the block they label while\n   * the rows below sit at 2 — reading as though the heading belonged to neither.\n   */\n  .settings-cost-history-title + .settings-lifetime-usage {\n    margin-top: 0;\n  }\n\n  .settings-cost-history {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n    padding-bottom: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-cost-history-icon {\n    flex: 0 0 auto;\n    width: 36px;\n    height: 36px;\n    border-radius: calc(var(--control-corner-radius) * 1px);\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    font-size: 16px;\n    font-weight: 700;\n    border: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-cost-history-row {\n    display: flex;\n    flex-direction: column;\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.5px);\n    padding: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-cost-history-row-content {\n    display: flex;\n    align-items: flex-start;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * All of these carry a ?hidden binding, and all declare display: flex — which silently beat the\n   * UA [hidden] { display: none } rule, because author-origin declarations outrank user-agent\n   * origin whatever the specificity. Without this, showTokens: false still rendered the full\n   * breakdown in the lifetime block, the live block and every history row, and an empty row list\n   * still occupied its padding under the lifetime total. Sibling elements that hide correctly do\n   * so only by declaring no display at all. Same treatment as .settings-modal-tab-panel[hidden]\n   * near the top of this file.\n   */\n  .settings-usage-row-tokens[hidden],\n  .settings-cost-history[hidden],\n  .settings-cost-history-row-content[hidden] {\n    display: none !important;\n  }\n\n  /*\n   * The buckets inside a history row drop the panel treatment they carry in the summary\n   * blocks — the row is already a bordered card, and a second box inside it reads as a\n   * nested panel. The adjacent-sibling rule above supplies the separator instead.\n   */\n  .settings-cost-history-row-breakdown .settings-token-breakdown {\n    flex: 1 1 auto;\n    margin-bottom: 0;\n    padding: 0;\n    background: none;\n    border: none;\n  }\n\n  .settings-cost-history-row-content + .settings-cost-history-row-content {\n    border-top: 1px solid var(--neutral-stroke-rest);\n    margin-top: calc(var(--design-unit) * 2px);\n    padding-top: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-cost-history-row-body {\n    flex: 1 1 auto;\n    min-width: 0;\n    display: flex;\n    gap: calc(var(--design-unit) * 2px);\n    justify-content: space-between;\n  }\n\n  /*\n   * Holds the cost and the delete button as one centred pair. The button used to be a sibling\n   * of the whole row body, kept in place by a -2px nudge tuned for when the metrics column had\n   * two lines (cost plus a merged token total). Dropping that second line left the nudge\n   * compensating for nothing. Centring the two against each other needs no magic number and\n   * cannot drift again if the metrics content changes.\n   *\n   * NB this rule previously set align-items with no display:flex, so it had no effect at all.\n   */\n  .settings-cost-history-row-right {\n    display: flex;\n    align-items: center;\n    gap: calc(var(--design-unit) * 1px);\n    flex: 0 0 auto;\n  }\n\n  .settings-cost-history-row-cost,\n  .settings-cost-history-row-title {\n    font-size: 14px;\n    font-weight: 600;\n    color: var(--neutral-foreground-rest);\n    min-width: 0;\n  }\n\n  .settings-cost-history-row-metrics {\n    display: flex;\n    flex-direction: column;\n    flex: 0 0 auto;\n    font-size: 13px;\n    font-family: ui-monospace, monospace;\n    color: var(--neutral-foreground-rest);\n    white-space: nowrap;\n  }\n\n  .settings-cost-history-row-date {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-cost-history-delete {\n    flex: 0 0 auto;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-cost-history-delete:hover {\n    color: var(--error-color);\n  }\n\n  .settings-cost-history ::slotted(*) {\n    display: block;\n  }\n\n  .settings-modal-footer {\n    width: 100%;\n  }\n\n  .settings-done-button {\n    margin-left: auto;\n  }\n\n  .settings-modal-footer-actions {\n    display: flex;\n    align-items: center;\n    justify-content: space-between;\n    gap: calc(var(--design-unit) * 2px);\n    width: 100%;\n  }\n\n  .settings-disclaimer {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    max-width: 60%;\n    line-height: 1.4;\n  }\n\n  /*\n   * Inline spinner shown in the \"Download agent log\" button while the log builds\n   * (GENC-1351 §5.8) — the lifetime-stitch path is an async provider round-trip.\n   * Sized to the button label and tinted with currentColor so it tracks the\n   * button's text colour in every appearance / theme.\n   */\n  [part='download-button'] .download-spinner {\n    display: inline-block;\n    width: 12px;\n    height: 12px;\n    margin-right: calc(var(--design-unit) * 1px);\n    vertical-align: -1px;\n    border: 2px solid currentColor;\n    border-right-color: transparent;\n    border-radius: 50%;\n    animation: download-spin 0.6s linear infinite;\n  }\n\n  @keyframes download-spin {\n    to {\n      transform: rotate(360deg);\n    }\n  }\n`",
+          "description": "Styles for the assistant settings modal (tabs, sections, toggles, cost summary)."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "settingsModalStyles",
+          "declaration": {
+            "name": "settingsModalStyles",
+            "module": "src/components/settings-modal/settings-modal.styles.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/components/settings-modal/settings-modal.template.ts",
+      "declarations": [
+        {
+          "kind": "function",
+          "name": "SettingsModalTemplate",
+          "return": {
+            "type": {
+              "text": "ViewTemplate<FoundationAiAssistant>"
+            }
+          },
+          "parameters": [
             {
-              "kind": "field",
-              "name": "dockProvider",
+              "name": "designSystemPrefix",
               "type": {
-                "text": "AiDockProvider | null"
-              },
-              "privacy": "private",
-              "default": "null"
-            },
+                "text": "string"
+              }
+            }
+          ],
+          "description": "Modal shell for assistant settings — Configuration and Usage tabs, section slots for\napp-specific UI, and built-in chat-bot toggles."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "SettingsModalTemplate",
+          "declaration": {
+            "name": "SettingsModalTemplate",
+            "module": "src/components/settings-modal/settings-modal.template.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/state/persistence/build-timeline-entries.ts",
+      "declarations": [
+        {
+          "kind": "function",
+          "name": "buildTimelineEntries",
+          "return": {
+            "type": {
+              "text": "DiagnosticEntry[]"
+            }
+          },
+          "parameters": [
             {
-              "kind": "field",
-              "name": "isDocked",
-              "type": {
-                "text": "boolean"
-              },
-              "privacy": "private",
-              "default": "false"
-            },
-            {
-              "kind": "field",
-              "name": "unsubBus",
-              "type": {
-                "text": "() => void | undefined"
-              },
-              "privacy": "private"
-            },
-            {
-              "kind": "method",
-              "name": "findAssistant",
-              "privacy": "private",
-              "return": {
-                "type": {
-                  "text": "HTMLElement | null"
-                }
-              },
-              "description": "Locate the assistant element currently slotted into the bubble."
-            },
-            {
-              "kind": "method",
-              "name": "adoptAssistant",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "parameters": [
-                {
-                  "name": "el",
-                  "type": {
-                    "text": "HTMLElement"
-                  }
-                },
-                {
-                  "name": "docked",
-                  "type": {
-                    "text": "boolean"
-                  }
-                }
-              ],
-              "description": "Register an externally-created assistant element and its docked state. For\nsingle-element hosts that create the assistant directly in a layout pane (rather\nthan statically in the bubble), so the manager tracks the one element, whether it's\ncurrently docked (for pop-in re-homing), reflects the right `popout-mode` on it\n(drives the header button), and hides the empty bubble."
-            },
-            {
-              "kind": "method",
-              "name": "syncBubbleVisibility",
-              "privacy": "private",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Hide the floating bubble unless it currently contains the assistant."
-            },
-            {
-              "kind": "method",
-              "name": "canDockChanged"
-            },
-            {
-              "kind": "method",
-              "name": "registerDockProvider",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "parameters": [
-                {
-                  "name": "provider",
-                  "type": {
-                    "text": "AiDockProvider"
-                  }
-                }
-              ]
-            },
-            {
-              "kind": "method",
-              "name": "deregisterDockProvider",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              }
-            },
-            {
-              "kind": "method",
-              "name": "collapseIfDocked",
-              "return": {
-                "type": {
-                  "text": "Promise<void>"
-                }
-              },
-              "description": "If the assistant is currently docked, collapses it back into the bubble.\nAwait this in `onBeforeNavButtonClick` to ensure cleanup before navigation."
-            }
-          ],
-          "superclass": {
-            "name": "GenesisElement",
-            "package": "@genesislcap/web-core"
-          },
-          "tagName": "foundation-ai-popout-manager",
-          "customElement": true
-        },
-        {
-          "kind": "function",
-          "name": "isAiAssistantDocked",
-          "return": {
-            "type": {
-              "text": "boolean"
-            }
-          },
-          "description": "True when the assistant is active in the layout panel (docked) rather than the bubble."
-        },
-        {
-          "kind": "function",
-          "name": "getAiPopoutManager",
-          "return": {
-            "type": {
-              "text": "FoundationAiPopoutManager | undefined"
-            }
-          },
-          "description": "Returns the active `FoundationAiPopoutManager` instance, or `undefined` if none is mounted.\nImport this in pages to call `registerDockProvider` / `deregisterDockProvider`."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "FoundationAiPopoutManager",
-          "declaration": {
-            "name": "FoundationAiPopoutManager",
-            "module": "src/components/popout-manager/popout-manager.ts"
-          }
-        },
-        {
-          "kind": "custom-element-definition",
-          "name": "foundation-ai-popout-manager",
-          "declaration": {
-            "name": "FoundationAiPopoutManager",
-            "module": "src/components/popout-manager/popout-manager.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "isAiAssistantDocked",
-          "declaration": {
-            "name": "isAiAssistantDocked",
-            "module": "src/components/popout-manager/popout-manager.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "getAiPopoutManager",
-          "declaration": {
-            "name": "getAiPopoutManager",
-            "module": "src/components/popout-manager/popout-manager.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/components/settings-modal/index.ts",
-      "declarations": [],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "SettingsModalTemplate",
-          "declaration": {
-            "name": "SettingsModalTemplate",
-            "module": "./settings-modal.template"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "type",
-          "declaration": {
-            "name": "type",
-            "module": "./settings-modal.template"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "SettingsModalTab",
-          "declaration": {
-            "name": "SettingsModalTab",
-            "module": "./settings-modal.template"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "settingsModalStyles",
-          "declaration": {
-            "name": "settingsModalStyles",
-            "module": "./settings-modal.styles"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/components/settings-modal/settings-modal.styles.ts",
-      "declarations": [
-        {
-          "kind": "variable",
-          "name": "settingsModalStyles",
-          "default": "css`\n  /*\n   * Section headings come from the shared fragment the package also exports, so a host titling\n   * its own slotted section applies the same rule rather than a copy of it.\n   */\n  ${assistantSettingsSectionTitleStyles}\n\n  *,\n  *::before,\n  *::after {\n    box-sizing: border-box;\n  }\n\n  .settings-modal {\n    --ai-tier-badge-bg-mix: 14%;\n    --ai-tier-badge-text-lighten: 18%;\n  }\n\n  .settings-modal::part(dialog) {\n    max-width: 620px;\n    width: calc(100vw - 48px);\n    max-height: calc(100vh - 48px);\n    padding: 0;\n  }\n\n  .settings-modal::part(content) {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    padding: 0;\n    width: 100%;\n  }\n\n  .settings-modal::part(top) {\n    padding: calc(var(--design-unit) * 4px) calc(var(--design-unit) * 5px);\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal::part(bottom) {\n    padding: calc(var(--design-unit) * 4px) calc(var(--design-unit) * 5px);\n    border-top: 1px solid var(--neutral-stroke-rest);\n    border-bottom-left-radius: var(--card-border-radius, calc(var(--control-corner-radius) * 1px));\n    border-bottom-right-radius: var(--card-border-radius, calc(var(--control-corner-radius) * 1px));\n    background-color: var(--neutral-layer-2);\n  }\n\n  .settings-modal-header {\n    display: flex;\n    align-items: center;\n    min-width: 0;\n  }\n\n  .settings-modal-title {\n    margin: 0;\n    font-size: 16px;\n    font-weight: 600;\n    display: flex;\n    align-items: center;\n    gap: calc(var(--design-unit) * 2px);\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-modal-content {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    flex: 1 1 auto;\n  }\n\n  .settings-modal-tabs::part(tablist) {\n    border-bottom: 0;\n    padding: 0 calc(var(--design-unit) * 5px);\n    column-gap: calc(var(--design-unit) * 5px);\n  }\n\n  .settings-modal-tabs::part(activeIndicator) {\n    height: 2px;\n  }\n\n  .settings-modal-tab {\n    padding: 0;\n    font-weight: 600;\n    gap: 6px;\n  }\n\n  .settings-modal-tab[aria-selected='true'] {\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-modal-tabs::part(tabpanel) {\n    border-top: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal-tab-panel {\n    display: flex;\n    flex-direction: column;\n    min-height: 0;\n    flex: 1 1 auto;\n    padding: 0;\n    border-radius: 0;\n  }\n\n  .settings-modal-tab-panel[hidden] {\n    display: none !important;\n  }\n\n  .settings-modal-body {\n    overflow-y: auto;\n    padding: 0 calc(var(--design-unit) * 5px) calc(var(--design-unit) * 2px);\n    max-height: min(60vh, 520px);\n  }\n\n  .settings-modal-section {\n    padding: calc(var(--design-unit) * 5px) 0;\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-modal-section:last-child {\n    border-bottom: none;\n  }\n\n  /*\n   * Only the spacing. Everything else about this heading comes from the exported fragment\n   * above, which the assistant and its hosts share; margin is deliberately not in there,\n   * since the gap below a heading depends on the layout around it.\n   */\n  .ai-settings-section-title {\n    margin: 0 0 calc(var(--design-unit) * 3px);\n  }\n\n  .settings-modal-section-note {\n    margin: calc(var(--design-unit) * -2px) 0 calc(var(--design-unit) * 3px);\n    font-size: 12px;\n    line-height: 1.5;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-modal-section-body {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-toggle-row {\n    display: flex;\n    align-items: flex-start;\n    gap: calc(var(--design-unit) * 3px);\n    padding: 0 0 calc(var(--design-unit) * 4px) 0;\n    border-bottom: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-toggle-row:last-child {\n    border-bottom: none;\n    padding-bottom: calc(var(--design-unit) * 1px);\n  }\n\n  .settings-toggle-row.is-stacked {\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * For rows whose control is a button rather than a switch. The base row top-aligns, which suits\n   * a switch (it lands level with the title), but a button is tall enough that top-aligning leaves\n   * it above the title-plus-description block it acts on.\n   */\n  .settings-toggle-row.is-centered {\n    align-items: center;\n  }\n\n  .settings-animation-list {\n    display: flex;\n    flex-direction: column;\n    width: 100%;\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.2px);\n    padding: calc(var(--design-unit) * 2px);\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-animation-list .settings-toggle-row {\n    border: 0;\n  }\n\n  .settings-animation-category {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-animation-category-label {\n    font-weight: 600;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-toggle-row + .settings-animation-category-label {\n    border-top: 1px solid var(--neutral-stroke-rest);\n    padding-top: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-animation-option {\n    padding: 0;\n    margin: 0;\n  }\n\n  .settings-animation-option:last-child {\n    border-bottom: none;\n    padding-bottom: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-toggle-text {\n    flex: 1;\n    min-width: 0;\n  }\n\n  .settings-toggle-title {\n    font-size: 14px;\n    font-weight: 500;\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-toggle-desc {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    line-height: 1.5;\n    max-width: 92%;\n  }\n\n  .settings-toggle-control {\n    flex: 0 0 auto;\n    min-width: 0;\n  }\n\n  .settings-toggle-control-wide {\n    width: 100%;\n    max-width: 280px;\n  }\n\n  .settings-toggle-row.is-stacked .settings-toggle-desc {\n    max-width: none;\n  }\n\n  .settings-toggle-row.is-stacked .settings-toggle-control-wide {\n    width: 100%;\n    max-width: none;\n  }\n\n  /*\n   * Sub-heading over the provider toggle group. Unlike the section headings it sits INSIDE\n   * .settings-modal-section-body, so the parent's 4-unit flex gap already separates it from the\n   * first toggle — and flex does not collapse margins, so the shared rule's 3-unit margin-bottom\n   * would add to that gap rather than replace it, leaving the label adrift from the rows it\n   * names. Zero the margin and pull back 2 of the 4 gap units, expressed in the same token so it\n   * tracks if that gap changes.\n   */\n  .settings-app-toggles-title {\n    margin: 0 0 calc(var(--design-unit) * -2px);\n  }\n\n  .settings-app-toggle-block {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 1px);\n  }\n\n  .settings-toggle-hint {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    line-height: 1.4;\n    padding-left: calc(var(--design-unit) * 1px);\n    font-style: italic;\n  }\n\n  /*\n   * The budget meter (GENC-1464) is the context indicator's money sibling and\n   * shares its row anatomy 1:1, so the budget classes JOIN these rules rather\n   * than restating them — one place to restyle the header/label/figures shape,\n   * and the two indicators cannot drift apart. Design-system tokens only, and\n   * unfallbacked: every token here ships a DS default, so a var(--x, y)\n   * fallback would be dead code that hides a broken token name (#2411/#2436\n   * review rule, pinned by settings-modal.styles.test.ts).\n   */\n  .settings-context-header,\n  .settings-budget-header {\n    display: flex;\n    justify-content: space-between;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 2px);\n    font-size: 12px;\n  }\n\n  .settings-context-label,\n  .settings-budget-label {\n    color: var(--neutral-foreground-hint);\n    font-size: 11px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n  }\n\n  .settings-context-tokens,\n  .settings-budget-figures {\n    color: var(--neutral-foreground-rest);\n  }\n\n  /* Freshness footer (GENC-1464): refresh button + label under the vendor\n     rows, left-aligned — a footnote to the figures above it. The button's\n     inline padding is pinned and cancelled by the container margin so the\n     ICON GLYPH (not the button box) sits flush with the budget labels'\n     left edge, whatever the density tokens say. */\n  .settings-budget-toolbar {\n    display: flex;\n    justify-content: flex-start;\n    align-items: center;\n    gap: 4px;\n    margin-inline-start: -4px;\n  }\n\n  .settings-budget-refresh::part(control) {\n    padding-inline: 4px;\n  }\n\n  .settings-budget-updated {\n    color: var(--neutral-foreground-hint);\n    font-size: 11px;\n  }\n\n  /*\n   * ONE rhythm for every meter row. The outer wrapper holds the context\n   * indicator and the budget meter; the inner one holds the budget meter's\n   * vendor rows — and both gap by the same 2 units (half the section body's 4)\n   * so that visually identical meter rows are evenly spaced whatever mix of\n   * them is on screen. Without the wrapper the context row inherits the body's\n   * 4-unit gap while the vendor rows keep 2, and three identical-looking rows\n   * read as an uneven 4/2/2. The wrapper renders only when at least one meter\n   * does — see settingsUsageMetersTemplate for why an always-on one would cost\n   * a stray gap.\n   */\n  .settings-usage-meters,\n  .settings-budget-usage {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-current-build,\n  .settings-lifetime-usage {\n    background: var(--neutral-layer-2);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.5px);\n    padding: calc(var(--design-unit) * 4px);\n    margin: calc(var(--design-unit) * 3px) 0;\n  }\n\n  /*\n   * Deliberately quieter than the live block: no pulsing badge and no accent, so the eye lands\n   * on what is being built now — which is why that block leads the tab and this one follows,\n   * under the history heading whose rows it totals.\n   */\n  .settings-lifetime-usage-top {\n    display: flex;\n    align-items: center;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-lifetime-label {\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 700;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-current-build-top {\n    display: flex;\n    align-items: center;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  /*\n   * Optically centring these 10px caps against the 14px project name beside them. Flex offers\n   * only two alignments and neither lands it, because a box centre and a text baseline are\n   * different lines:\n   *   - align-items: center   sits the badge baseline about 1.2px high\n   *   - align-items: baseline matches baselines, but the caps then read as bottom-aligned\n   *     against the name's ascenders, so the badge looks low\n   * The eye wants the midpoint, so: centre the boxes, then translate down by the ~1px of\n   * overshoot. This is a nudge, but it corrects a fixed relationship between two font sizes\n   * rather than some neighbouring element's layout, so unlike a margin tuned to a sibling it\n   * cannot rot when that sibling changes. In em, so it tracks the badge text.\n   *\n   * display: block, not inline-flex: a flex container has no text baseline of its own and\n   * synthesizes one from its first child, which here is the dot, an empty span. As a block box\n   * the badge takes the baseline of its first line, i.e. the text.\n   */\n  .settings-live-badge {\n    display: block;\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 700;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--accent-fill-rest);\n    white-space: nowrap;\n    transform: translateY(0.1em);\n  }\n\n  .settings-live-dot {\n    display: inline-block;\n    width: 7px;\n    height: 7px;\n\n    /* Replaces the flex gap the badge no longer has. */\n    margin-right: calc(var(--design-unit) * 1px);\n\n    /* Centres the dot on the text beside it without disturbing that text's baseline. */\n    vertical-align: middle;\n    border-radius: 50%;\n    background: var(--accent-fill-rest);\n    animation: settings-live-pulse 1.6s ease-out infinite;\n  }\n\n  @keyframes settings-live-pulse {\n    0% {\n      box-shadow: 0 0 0 0 color-mix(in srgb, var(--accent-fill-rest) 55%, transparent);\n    }\n\n    70% {\n      box-shadow: 0 0 0 7px transparent;\n    }\n\n    100% {\n      box-shadow: 0 0 0 0 transparent;\n    }\n  }\n\n  .settings-current-build-name {\n    font-size: 14px;\n    line-height: 1;\n    font-weight: 600;\n  }\n\n  /*\n   * Cost and the token buckets side by side: one number in its own box, the four buckets\n   * sharing the box next to it. Stretch, so the two are the same height however tall the 22px\n   * cost value makes the left one.\n   */\n  .settings-usage-row {\n    display: flex;\n    flex-wrap: wrap;\n    align-items: stretch;\n    gap: calc(var(--design-unit) * 3px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-usage-row-tokens {\n    display: flex;\n    flex: 1 1 auto;\n    min-width: 0;\n  }\n\n  .settings-build-stat {\n    min-width: 0;\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1px);\n    padding: calc(var(--design-unit) * 3px);\n  }\n\n  .settings-build-stat-label {\n    font-size: 10px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-build-stat-value {\n    font-size: 22px;\n    font-weight: 700;\n    margin-top: calc(var(--design-unit) * 1px);\n    color: var(--neutral-foreground-rest);\n  }\n\n  .settings-build-stat-value .prefix,\n  .settings-build-stat-value .suffix {\n    color: var(--accent-fill-rest);\n  }\n\n  /*\n   * Per-bucket token split, beneath the headline cost. Small paired label/value cells\n   * rather than four more stat cards: they are the detail behind the cost above, so they\n   * have to read as subordinate to it rather than compete with it. The four buckets ARE\n   * the token figure now — there is no merged total anywhere for them to break down.\n   */\n  .settings-token-breakdown {\n    display: flex;\n    flex-direction: column;\n\n    /*\n     * Tight against the buckets below. One design unit rather than two, because each bucket\n     * separates its own label from its value by only 2px — at two units the title sat four\n     * times further from the bucket labels than they sit from their own numbers, which read\n     * as a gap between unrelated blocks instead of a heading over its content.\n     */\n    gap: calc(var(--design-unit) * 1px);\n    margin-bottom: calc(var(--design-unit) * 3px);\n    padding: calc(var(--design-unit) * 2px) calc(var(--design-unit) * 3px);\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1px);\n  }\n\n  /*\n   * Titles the box, because nothing else in it named the unit. Same styling and position as\n   * the cost box's label, so two boxes sitting side by side are titled the same way; the\n   * hierarchy against the bucket labels comes from position, not a second type size.\n   */\n  .settings-token-breakdown-label {\n    font-size: 10px;\n    line-height: 1;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-token-buckets {\n    display: flex;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-token-bucket {\n    display: flex;\n\n    /*\n     * min-content (not 0) so a bucket cannot be shrunk narrower than its own unbreakable label.\n     * With the label set to nowrap, a zero minimum would overflow it into the next column instead\n     * of wrapping — so the container's flex-wrap takes over and moves a bucket to a second row,\n     * which is the degradation we want when the modal is dragged narrow.\n     */\n    min-width: min-content;\n    flex-direction: column;\n    gap: 2px;\n  }\n\n  .settings-token-bucket-label {\n    font-size: 10px;\n    font-weight: 600;\n    text-transform: uppercase;\n    letter-spacing: 0.06em;\n    color: var(--neutral-foreground-hint);\n\n    /*\n     * One line, always. The rate marker is a separate inline box after collapsible whitespace, so\n     * a wrappable label gives it a break opportunity of its own — in a narrow column it orphaned\n     * onto line 2, which also pushed that bucket's value a line below the other three and broke\n     * the row of figures. nowrap removes every break opportunity in the label, the space before\n     * the marker included, so no glue character is needed.\n     */\n    white-space: nowrap;\n  }\n\n  .settings-token-bucket-value {\n    font-size: 13px;\n    font-weight: 600;\n    color: var(--neutral-foreground-rest);\n  }\n\n  /*\n   * The price-direction marker on a cache bucket's label — down for reads (a fraction of the\n   * uncached input rate), up for writes (a premium over it). Three tiers, so a bucket with no\n   * marker is the reference rate rather than an unlabelled fourth case.\n   *\n   * Carried by the label rather than the value, which is what this used to do: cache reads are\n   * usually the largest bucket by a wide margin in an agentic session, so the value was muted to\n   * stop the biggest number reading as the dominant cost driver. That priced the treatment to the\n   * wrong thing — a dimmed 0 (every Gemini cache write) looked disabled next to a normal 0, and a\n   * rate is a property of the bucket, not of this turn's figure.\n   *\n   * Sized down and nudged up rather than tinted: the label is already the hint colour, so a\n   * dimmer marker would vanish and a brighter one would out-shout the word it qualifies.\n   */\n  .settings-token-bucket-rate {\n    font-size: 8px;\n    line-height: 1;\n    vertical-align: 0.15em;\n    letter-spacing: 0;\n  }\n\n  /*\n   * Usage-row overrides. Placed after the base rules they refine rather than up beside\n   * .settings-usage-row itself, because stylelint's no-descending-specificity rejects a\n   * compound selector appearing before the plain one it overrides.\n   */\n\n  /* Sized by its content; the buckets take the rest, since four cells need the width. */\n  .settings-usage-row > .settings-build-stat {\n    flex: 0 1 auto;\n  }\n\n  .settings-usage-row .settings-token-breakdown {\n    flex: 1 1 auto;\n\n    /* The row owns the spacing now; this centres the column against the taller cost box. */\n    justify-content: center;\n    margin-bottom: 0;\n  }\n\n  /*\n   * Basis auto, not 0: a zero basis splits the row into four equal columns, so CACHE WRITE is\n   * squeezed exactly as hard as INPUT despite being twice the label. Sizing from content gives the\n   * long labels the room their text needs and lets the short ones concede it, which is what makes\n   * white-space: nowrap above safe — every column starts at least as wide as its own content,\n   * then shares the slack. Still grows and shrinks, so the four stay flush edge to edge.\n   */\n  .settings-usage-row .settings-token-bucket {\n    flex: 1 1 auto;\n  }\n\n  .settings-model-tags {\n    display: flex;\n    flex-wrap: wrap;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-model-tag {\n    font-size: 11px;\n    font-weight: 600;\n    padding: 3px 9px;\n    border-radius: 20px;\n    font-family: ui-monospace, monospace;\n    border: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-model-tag,\n  .settings-cost-history-icon {\n    --model-tag-color: var(--neutral-foreground-rest);\n\n    background: color-mix(\n      in srgb,\n      var(--model-tag-color) var(--ai-tier-badge-bg-mix),\n      var(--neutral-layer-1)\n    );\n    border-color: color-mix(in srgb, var(--model-tag-color) 20%, var(--neutral-layer-1));\n    color: color-mix(in srgb, var(--model-tag-color), white var(--ai-tier-badge-text-lighten));\n  }\n\n  .settings-cost-history-title {\n    font-size: 11px;\n    text-transform: uppercase;\n    letter-spacing: 0.08em;\n    color: var(--neutral-foreground-hint);\n    font-weight: 600;\n    margin: calc(var(--design-unit) * 4px) 0 calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * The heading labels the lifetime card as well as the rows, so the card gives up its own top\n   * margin and the gap becomes the heading's alone. Adjacent siblings collapse to the LARGER of\n   * the two margins, so leaving both would space the caps 3 units off the block they label while\n   * the rows below sit at 2 — reading as though the heading belonged to neither.\n   */\n  .settings-cost-history-title + .settings-lifetime-usage {\n    margin-top: 0;\n  }\n\n  .settings-cost-history {\n    display: flex;\n    flex-direction: column;\n    gap: calc(var(--design-unit) * 2px);\n    padding-bottom: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-cost-history-icon {\n    flex: 0 0 auto;\n    width: 36px;\n    height: 36px;\n    border-radius: calc(var(--control-corner-radius) * 1px);\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    font-size: 16px;\n    font-weight: 700;\n    border: 1px solid var(--neutral-stroke-rest);\n  }\n\n  .settings-cost-history-row {\n    display: flex;\n    flex-direction: column;\n    background: var(--neutral-layer-1);\n    border: 1px solid var(--neutral-stroke-rest);\n    border-radius: calc(var(--control-corner-radius) * 1.5px);\n    padding: calc(var(--design-unit) * 4px);\n  }\n\n  .settings-cost-history-row-content {\n    display: flex;\n    align-items: flex-start;\n    gap: calc(var(--design-unit) * 2px);\n  }\n\n  /*\n   * All of these carry a ?hidden binding, and all declare display: flex — which silently beat the\n   * UA [hidden] { display: none } rule, because author-origin declarations outrank user-agent\n   * origin whatever the specificity. Without this, showTokens: false still rendered the full\n   * breakdown in the lifetime block, the live block and every history row, and an empty row list\n   * still occupied its padding under the lifetime total. Sibling elements that hide correctly do\n   * so only by declaring no display at all. Same treatment as .settings-modal-tab-panel[hidden]\n   * near the top of this file.\n   */\n  .settings-usage-row-tokens[hidden],\n  .settings-cost-history[hidden],\n  .settings-cost-history-row-content[hidden] {\n    display: none !important;\n  }\n\n  /*\n   * The buckets inside a history row drop the panel treatment they carry in the summary\n   * blocks — the row is already a bordered card, and a second box inside it reads as a\n   * nested panel. The adjacent-sibling rule above supplies the separator instead.\n   */\n  .settings-cost-history-row-breakdown .settings-token-breakdown {\n    flex: 1 1 auto;\n    margin-bottom: 0;\n    padding: 0;\n    background: none;\n    border: none;\n  }\n\n  .settings-cost-history-row-content + .settings-cost-history-row-content {\n    border-top: 1px solid var(--neutral-stroke-rest);\n    margin-top: calc(var(--design-unit) * 2px);\n    padding-top: calc(var(--design-unit) * 2px);\n  }\n\n  .settings-cost-history-row-body {\n    flex: 1 1 auto;\n    min-width: 0;\n    display: flex;\n    gap: calc(var(--design-unit) * 2px);\n    justify-content: space-between;\n  }\n\n  /*\n   * Holds the cost and the delete button as one centred pair. The button used to be a sibling\n   * of the whole row body, kept in place by a -2px nudge tuned for when the metrics column had\n   * two lines (cost plus a merged token total). Dropping that second line left the nudge\n   * compensating for nothing. Centring the two against each other needs no magic number and\n   * cannot drift again if the metrics content changes.\n   *\n   * NB this rule previously set align-items with no display:flex, so it had no effect at all.\n   */\n  .settings-cost-history-row-right {\n    display: flex;\n    align-items: center;\n    gap: calc(var(--design-unit) * 1px);\n    flex: 0 0 auto;\n  }\n\n  .settings-cost-history-row-cost,\n  .settings-cost-history-row-title {\n    font-size: 14px;\n    font-weight: 600;\n    color: var(--neutral-foreground-rest);\n    min-width: 0;\n  }\n\n  .settings-cost-history-row-metrics {\n    display: flex;\n    flex-direction: column;\n    flex: 0 0 auto;\n    font-size: 13px;\n    font-family: ui-monospace, monospace;\n    color: var(--neutral-foreground-rest);\n    white-space: nowrap;\n  }\n\n  .settings-cost-history-row-date {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-cost-history-delete {\n    flex: 0 0 auto;\n    color: var(--neutral-foreground-hint);\n  }\n\n  .settings-cost-history-delete:hover {\n    color: var(--error-color);\n  }\n\n  .settings-cost-history ::slotted(*) {\n    display: block;\n  }\n\n  .settings-modal-footer {\n    width: 100%;\n  }\n\n  .settings-done-button {\n    margin-left: auto;\n  }\n\n  .settings-modal-footer-actions {\n    display: flex;\n    align-items: center;\n    justify-content: space-between;\n    gap: calc(var(--design-unit) * 2px);\n    width: 100%;\n  }\n\n  .settings-disclaimer {\n    font-size: 12px;\n    color: var(--neutral-foreground-hint);\n    max-width: 60%;\n    line-height: 1.4;\n  }\n\n  /*\n   * Inline spinner shown in the \"Download agent log\" button while the log builds\n   * (GENC-1351 §5.8) — the lifetime-stitch path is an async provider round-trip.\n   * Sized to the button label and tinted with currentColor so it tracks the\n   * button's text colour in every appearance / theme.\n   */\n  [part='download-button'] .download-spinner {\n    display: inline-block;\n    width: 12px;\n    height: 12px;\n    margin-right: calc(var(--design-unit) * 1px);\n    vertical-align: -1px;\n    border: 2px solid currentColor;\n    border-right-color: transparent;\n    border-radius: 50%;\n    animation: download-spin 0.6s linear infinite;\n  }\n\n  @keyframes download-spin {\n    to {\n      transform: rotate(360deg);\n    }\n  }\n`",
-          "description": "Styles for the assistant settings modal (tabs, sections, toggles, cost summary)."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "settingsModalStyles",
-          "declaration": {
-            "name": "settingsModalStyles",
-            "module": "src/components/settings-modal/settings-modal.styles.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/components/settings-modal/settings-modal.template.ts",
-      "declarations": [
-        {
-          "kind": "function",
-          "name": "SettingsModalTemplate",
-          "return": {
-            "type": {
-              "text": "ViewTemplate<FoundationAiAssistant>"
-            }
-          },
-          "parameters": [
-            {
-              "name": "designSystemPrefix",
-              "type": {
-                "text": "string"
-              }
-            }
-          ],
-          "description": "Modal shell for assistant settings — Configuration and Usage tabs, section slots for\napp-specific UI, and built-in chat-bot toggles."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "SettingsModalTemplate",
-          "declaration": {
-            "name": "SettingsModalTemplate",
-            "module": "src/components/settings-modal/settings-modal.template.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/state/persistence/build-timeline-entries.ts",
-      "declarations": [
-        {
-          "kind": "function",
-          "name": "buildTimelineEntries",
-          "return": {
-            "type": {
-              "text": "DiagnosticEntry[]"
-            }
-          },
-          "parameters": [
-            {
-              "name": "input",
+              "name": "input",
               "type": {
                 "text": "{\n  turnSnapshots: readonly TurnSnapshotLike[];\n  messages: readonly ChatMessage[];\n  metaEvents: readonly MetaEvent[];\n}"
               }
@@ -10602,7 +10436,31 @@
               }
             }
           ],
-          "description": "Reassemble diagnostic entries into the `{ readme, timeline, meta }` debug-log\nshape (GENC-1351 §5.8). `timeline` = the `message`/`turn`/`event` entries sorted\nby ISO `timestamp` (kind-rank tie-break). `meta` = the **newest** `meta-snapshot`'s\nblock only — a \"state at export\" photo, matching the single-page log. The older\nsnapshots are intentionally dropped: the per-turn evolution they would show is\nalready in the timeline (`turn.agentSnapshot` + `context.updated` events), so\nkeeping them would just repeat the bulky, near-static `agentSummary`. `readme` =\nthe passed (current) constant. Pure — reused for both the live current-page log\nand the reassembled lifetime log stitched from the persisted stream, so both\ncome out shape-identical."
+          "description": "Reassemble diagnostic entries into the `{ readme, sessionUsage, timeline, meta }`\ndebug-log shape (GENC-1351 §5.8). `timeline` = the `message`/`turn`/`event` entries sorted\nby ISO `timestamp` (kind-rank tie-break). `meta` = the **newest** `meta-snapshot`'s\nblock only — a \"state at export\" photo, matching the single-page log. The older\nsnapshots are intentionally dropped: the per-turn evolution they would show is\nalready in the timeline (`turn.agentSnapshot` + `context.updated` events), so\nkeeping them would just repeat the bulky, near-static `agentSummary`. `readme` =\nthe passed (current) constant. `sessionUsage` = that same newest snapshot's\n`meta.context.sessionUsage`, lifted to the top level. Pure — reused for both the\nlive current-page log and the reassembled lifetime log stitched from the persisted\nstream, so both come out shape-identical.\n\nNOTE for a caller stitching a STORED stream (a headless consumer harvesting its own\nlifetime log, say): the newest stored `meta-snapshot` is frozen at the last\nconfig-signature change, so `meta` and `sessionUsage` are as old as that unless you\npass a fresh snapshot of your own — withFreshMetaSnapshot does exactly that,\nand the element's download path goes through it."
+        },
+        {
+          "kind": "function",
+          "name": "withFreshMetaSnapshot",
+          "return": {
+            "type": {
+              "text": "DiagnosticEntry[]"
+            }
+          },
+          "parameters": [
+            {
+              "name": "stored",
+              "type": {
+                "text": "readonly DiagnosticEntry[]"
+              }
+            },
+            {
+              "name": "fresh",
+              "type": {
+                "text": "DiagnosticEntry"
+              }
+            }
+          ],
+          "description": "A stored diagnostics stream with its `meta-snapshot`s replaced by `fresh` — what to\npass assembleDebugLog when reassembling a persisted stream for export.\n\nThe stored snapshots are dropped rather than out-timestamped. `assembleDebugLog` keeps\nwhichever claims the later time, and a stream written on another machine can carry a\nskewed clock; `fresh` is built from live state and so is the more current by\nconstruction. Only one snapshot ever survives reassembly, so the count is unchanged —\nthough a snapshot taken while the driver is unwired (mid-popout) can leave\n`activeFoldStack`/`activeDebugSnapshot` unset where a stored one had them. The figures\nthis exists for — the context block and `sessionUsage` — read the session store and\nelement props, which survive an unwire.\n\nPure, and separate from the element for that reason: the swap it performs is the fix\nfor a silent bug (a lifetime log reporting near-zero spend against a transcript full of\npriced messages), so it needs to be testable without mounting anything."
         }
       ],
       "exports": [
@@ -10613,6 +10471,14 @@
             "name": "assembleDebugLog",
             "module": "src/state/persistence/diagnostics.ts"
           }
+        },
+        {
+          "kind": "js",
+          "name": "withFreshMetaSnapshot",
+          "declaration": {
+            "name": "withFreshMetaSnapshot",
+            "module": "src/state/persistence/diagnostics.ts"
+          }
         }
       ]
     },
@@ -10677,6 +10543,14 @@
             "module": "./diagnostics"
           }
         },
+        {
+          "kind": "js",
+          "name": "withFreshMetaSnapshot",
+          "declaration": {
+            "name": "withFreshMetaSnapshot",
+            "module": "./diagnostics"
+          }
+        },
         {
           "kind": "js",
           "name": "DiagnosticEntry",
@@ -11035,6 +10909,225 @@
           }
         }
       ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/components/popout-manager/index.ts",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "package": "./popout-manager"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/components/popout-manager/popout-manager.ts",
+      "declarations": [
+        {
+          "kind": "class",
+          "description": "App-shell component that owns the pop-out/pop-in lifecycle for the AI assistant bubble.",
+          "name": "FoundationAiPopoutManager",
+          "members": [
+            {
+              "kind": "field",
+              "name": "canDock",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "True when a dock provider is registered — controls expand button visibility."
+            },
+            {
+              "kind": "field",
+              "name": "assistantEl",
+              "type": {
+                "text": "HTMLElement | null"
+              },
+              "privacy": "private",
+              "default": "null",
+              "description": "The single assistant element. Captured while it's in the bubble slot and held\nacross the move (it's the same instance whether docked or in the bubble), so\npop-in can re-home it even though it's no longer a child of this manager."
+            },
+            {
+              "kind": "field",
+              "name": "dockProvider",
+              "type": {
+                "text": "AiDockProvider | null"
+              },
+              "privacy": "private",
+              "default": "null"
+            },
+            {
+              "kind": "field",
+              "name": "isDocked",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false"
+            },
+            {
+              "kind": "field",
+              "name": "unsubBus",
+              "type": {
+                "text": "() => void | undefined"
+              },
+              "privacy": "private"
+            },
+            {
+              "kind": "method",
+              "name": "findAssistant",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HTMLElement | null"
+                }
+              },
+              "description": "Locate the assistant element currently slotted into the bubble."
+            },
+            {
+              "kind": "method",
+              "name": "adoptAssistant",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "el",
+                  "type": {
+                    "text": "HTMLElement"
+                  }
+                },
+                {
+                  "name": "docked",
+                  "type": {
+                    "text": "boolean"
+                  }
+                }
+              ],
+              "description": "Register an externally-created assistant element and its docked state. For\nsingle-element hosts that create the assistant directly in a layout pane (rather\nthan statically in the bubble), so the manager tracks the one element, whether it's\ncurrently docked (for pop-in re-homing), reflects the right `popout-mode` on it\n(drives the header button), and hides the empty bubble."
+            },
+            {
+              "kind": "method",
+              "name": "syncBubbleVisibility",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Hide the floating bubble unless it currently contains the assistant."
+            },
+            {
+              "kind": "method",
+              "name": "canDockChanged"
+            },
+            {
+              "kind": "method",
+              "name": "registerDockProvider",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "provider",
+                  "type": {
+                    "text": "AiDockProvider"
+                  }
+                }
+              ]
+            },
+            {
+              "kind": "method",
+              "name": "deregisterDockProvider",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              }
+            },
+            {
+              "kind": "method",
+              "name": "collapseIfDocked",
+              "return": {
+                "type": {
+                  "text": "Promise<void>"
+                }
+              },
+              "description": "If the assistant is currently docked, collapses it back into the bubble.\nAwait this in `onBeforeNavButtonClick` to ensure cleanup before navigation."
+            }
+          ],
+          "superclass": {
+            "name": "GenesisElement",
+            "package": "@genesislcap/web-core"
+          },
+          "tagName": "foundation-ai-popout-manager",
+          "customElement": true
+        },
+        {
+          "kind": "function",
+          "name": "isAiAssistantDocked",
+          "return": {
+            "type": {
+              "text": "boolean"
+            }
+          },
+          "description": "True when the assistant is active in the layout panel (docked) rather than the bubble."
+        },
+        {
+          "kind": "function",
+          "name": "getAiPopoutManager",
+          "return": {
+            "type": {
+              "text": "FoundationAiPopoutManager | undefined"
+            }
+          },
+          "description": "Returns the active `FoundationAiPopoutManager` instance, or `undefined` if none is mounted.\nImport this in pages to call `registerDockProvider` / `deregisterDockProvider`."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "FoundationAiPopoutManager",
+          "declaration": {
+            "name": "FoundationAiPopoutManager",
+            "module": "src/components/popout-manager/popout-manager.ts"
+          }
+        },
+        {
+          "kind": "custom-element-definition",
+          "name": "foundation-ai-popout-manager",
+          "declaration": {
+            "name": "FoundationAiPopoutManager",
+            "module": "src/components/popout-manager/popout-manager.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "isAiAssistantDocked",
+          "declaration": {
+            "name": "isAiAssistantDocked",
+            "module": "src/components/popout-manager/popout-manager.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "getAiPopoutManager",
+          "declaration": {
+            "name": "getAiPopoutManager",
+            "module": "src/components/popout-manager/popout-manager.ts"
+          }
+        }
+      ]
     }
   ]
 }