@agent-native/core 0.87.0 → 0.90.1

package/corpus/templates/brain/.agents/skills/actions/SKILL.md

@@ -161,6 +161,18 @@ to find likely URLs, `web-request` or `provider-api-docs` with clean
 `webFetch()` when you need to grep, aggregate, or compare many pages before
 returning a small result.
 
+For LONG compute, `run-code` supports durable background executions: pass
+`background: true` and the code is enqueued to a `sandbox_executions` row and
+executed out-of-band with a generous budget (default 10 min), surviving the
+hosted agent run's ~40s soft timeout. The call returns
+`{ executionId, status: "queued" }` immediately with polling guidance; check
+progress with `run-code` `{ executionId }` (or the `get-code-execution` tool
+where registered) — results persist after completion. Use background for big
+cross-source joins, multi-page provider sweeps, and heavy analysis scripts;
+keep quick scripts in the default foreground mode. Agents should continue
+other work between polls, and on `failed`/`timed_out` split the computation or
+persist intermediate progress with `workspaceWrite` and re-run.
+
 ### The `http` Option
 
 Controls how the action is exposed as an HTTP endpoint:
@@ -205,6 +217,49 @@ run: async (args) => {
 }
 ```
 
+### Returning Images the Agent Can See (`_agentImages`)
+
+An action's return object may include the well-known optional field
+`_agentImages` to attach vision images (screenshots, chart previews, rendered
+designs) to the tool result. The agent literally sees them — enabling visual
+self-review loops — while the field itself is stripped from the JSON text the
+model reads.
+
+```ts
+run: async ({ dashboardId }) => {
+  const shot = await renderDashboardPng(dashboardId); // Buffer
+  return {
+    dashboardId,
+    panelCount: 6,
+    _agentImages: [
+      // Either a public https URL (preferred — the provider fetches it)…
+      { url: "https://cdn.example.com/previews/dash-1.png", label: "overview" },
+      // …or base64 without a data: prefix (mediaType required; a full
+      // data:image/png;base64,… URL in `data` is also accepted and parsed).
+      { data: shot.toString("base64"), mediaType: "image/png" },
+    ],
+  };
+},
+```
+
+Rules and limits:
+
+- Shape: `Array<{ url?: string; data?: string; mediaType?: string; label?: string }>`.
+  Each entry needs `url` (https only) **or** `data`. Supported media types:
+  `image/jpeg`, `image/png`, `image/gif`, `image/webp`.
+- Caps: max **4 images** per result; max **~2MB of base64** per image.
+  Over-cap or invalid entries never fail the call — they become text notes in
+  the result telling the model what was dropped and why.
+- Persistence: the run ledger stores only the string result plus compact
+  `[image: …]` notes (URLs verbatim; base64 as a byte-count placeholder) —
+  never the payload. Images are re-attached only for the live turn; replayed
+  history is text-only, so prefer stable `url` images the model can re-request.
+- Engine support: native Anthropic and vision-capable AI-SDK providers
+  (anthropic, openai, google, openrouter) receive real image blocks; other
+  paths (Builder gateway, non-vision providers) degrade to the text notes.
+- External MCP tools need no changes — standard MCP `image` content parts are
+  converted automatically under the same caps.
+
 ### Validating Return Values (`outputSchema`)
 
 `schema` validates inputs; `outputSchema` validates what the action **returns**. Pass any Standard Schema-compatible schema (Zod, Valibot, ArkType) and the framework validates the result _after_ `run()` resolves — input validated before `run`, output after.

package/corpus/templates/brain/.agents/skills/ask-across-everything/SKILL.md

@@ -25,7 +25,12 @@ metadata, not retrieved evidence.
    user asks a direct cited-memory question and wants an answer immediately.
 2. Read the Brain results and `federatedCoverage.scopeNote`.
 3. Inspect `federatedCoverage.delegationHints` and
-   `federatedCoverage.discoveredAgents.agents`.
+   `federatedCoverage.discoveredAgents.agents`. `delegationHints[].target` is
+   typed to exactly three values today: `"analytics"`, `"mail"`, `"dispatch"`
+   (`FederatedDelegationTarget` in `server/lib/search.ts`) — there is no
+   delegation hint for other templates yet, even if one is installed in the
+   workspace. Each hint also carries `matchedSignals` (which words in the
+   question triggered it) and a human-readable `reason`.
 4. If the user asked for live/app-owned data and a hint matches the request,
    call the specialist app agent with `call-agent`. Keep the prompt narrow and
    include the user question plus any Brain context needed for names, dates, or

package/corpus/templates/brain/.agents/skills/brain/SKILL.md

@@ -8,15 +8,73 @@ description: Work with the Brain institutional-memory template, including import
 Use Brain actions rather than raw SQL.
 
 1. Call `get-brain-settings` before answering, searching broadly, or distilling when current settings are not already in context. Apply the returned guidance for assistant name, company name, tone, source policy, citation requirements, publish tier, redaction, and distillation instructions.
-2. Import raw material with `import-capture` or `import-transcript`.
-3. Call `enqueue-distillation` when a capture needs distillation.
+2. Import raw material with `import-capture` (generic) or `import-transcript`
+   (meeting-shaped: participants, `sourceUrl`, tags). Both default
+   `enqueueDistillation: true` and auto-create a `manual` source when
+   `sourceId` is omitted — don't call `create-source` first just to import one
+   ad hoc capture.
+3. Call `enqueue-distillation` when a capture needs distillation. Re-running it
+   for a capture that's already queued/processing refreshes the handoff
+   instructions instead of creating a duplicate queue row.
 4. Before writing knowledge, call `get-capture` and copy short exact quotes.
-5. Call `write-knowledge` with `evidence` entries whose `quote` fields are exact capture substrings.
-6. If `write-knowledge` returns `mode: "proposal"`, leave it in review unless the user asks to approve.
+   `get-capture` redacts `title`/`content`/`metadata` by default; pass
+   `includeRawContent: true` (requires `editor` access on the source) to get
+   the real text needed for an exact-substring quote.
+5. Call `write-knowledge` with `evidence` entries whose `quote` fields are exact capture substrings — `validateEvidence` throws otherwise.
+6. If `write-knowledge` returns `mode: "proposal"`, leave it in review unless the user asks to approve. See AGENTS.md for the exact tier/confidence conditions that trigger a proposal.
 
-Search starts with `search-everything` when available and uses `search-knowledge` for distilled knowledge only; there is no vector index. Follow `sourcePolicy`: `strict` means reviewed knowledge only, `balanced` means raw captures are labeled fallback context, and `exploratory` means raw captures and sources can be labeled leads.
+## Capture Sanitization (Transcripts)
+
+Transcript-kind captures are sanitized **before storage** by default
+(`shouldSanitizeCaptureBeforeStorage` — true whenever `kind === "transcript"`,
+unless `captureSanitizationEnabled: false` in settings or a per-capture
+`metadata.sanitizeBeforeStorage` / source-config override says otherwise).
+Sanitization always strips, regardless of settings:
+
+- Recruiting/hiring/candidate-evaluation content (`RECRUITING_SIGNAL`).
+- Personal-life details, medical/family/compensation mentions
+  (`PERSONAL_SIGNAL`).
+- Slack mention/channel encoding, emails, phone numbers, API-key-shaped
+  strings, and bare URLs (deterministic regex pass, not model-dependent).
+- Raw transcript metadata keys (`raw`, `segments`, `transcript`, `messages`,
+  `utterances`, `attendees`, `participants`, `speaker(s)`, etc.) are dropped
+  from stored `metadata`, not just the text.
+
+Company-relevant signal (`COMPANY_SIGNAL`: product, decision, roadmap,
+pricing, incident, GTM, etc.) is what sanitization tries to retain. If nothing
+company-relevant survives, the stored content becomes the literal string "No
+company-relevant content retained from this capture." — treat that string as
+"this capture had nothing worth distilling," not as an error.
+
+## Search: Two Distinct Actions, No Vector Index
+
+- `search-knowledge` — SQL text match over `title`/`summary`/`body` of
+  **distilled knowledge only**. Use for "what does Brain officially know about
+  X."
+- `search-everything` — broader pass across knowledge, raw captures, and
+  sources in one call, plus `federatedCoverage` (delegation hints for other
+  apps). Use this as the default first search for an open-ended question;
+  narrow with `type: "knowledge" | "capture" | "source"` when you already know
+  which record type you need.
+- Neither uses embeddings/vector search — matching is deterministic SQL LIKE
+  scoring. Don't describe results as "semantically similar"; they matched on
+  literal term overlap.
+
+Follow `sourcePolicy` for how much of `search-everything`'s output an answer
+may lean on: `strict` means reviewed knowledge only, `balanced` means raw
+captures are labeled fallback context only when knowledge is thin, and
+`exploratory` means raw captures and sources can always be labeled leads. See
+AGENTS.md for the exact `rawCaptureFallback` behavior table.
 
 For "ask across everything" requests, follow the `ask-across-everything` skill:
 search Brain first, inspect `federatedCoverage`, delegate live/app-owned data
 requests with `call-agent`, and never claim Brain searched sibling app databases
 directly.
+
+## Related Skills
+
+- `ingestion-and-connectors` — source creation, health states, sync scheduling,
+  and credential resolution order.
+- `brain-runbook` — internal architecture and ops detail (Slack rollout,
+  distillation worker, scheduled sync cron, demo/eval seeding).
+- `ask-across-everything`, `security`, `sharing`.

package/corpus/templates/brain/.agents/skills/ingestion-and-connectors/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: ingestion-and-connectors
+description: >-
+  Create, sync, and diagnose Brain sources across all providers (manual,
+  generic, clips, slack, granola, github) — health states, sync scheduling,
+  and credential resolution. Use when adding a source, running or debugging a
+  sync, or the user asks why a source is stale, erroring, or not importing.
+---
+
+# Ingestion and Connectors
+
+For Slack-specific rollout steps (channel allow-lists, pilot runs, scope
+checklist), read `brain-runbook` instead — this skill covers the
+provider-agnostic source lifecycle.
+
+## Source Providers
+
+`create-source` accepts exactly `manual`, `generic`, `clips`, `slack`,
+`granola`, or `github` (`sourceProviderSchema`). There is no arbitrary/custom
+provider string — a generic webhook-fed source uses `provider: "generic"`
+with a `sourceKey` + minted `ingestToken`, not a made-up provider id.
+
+```bash
+pnpm --filter brain action create-source \
+  --title "Support call transcripts" \
+  --provider generic \
+  --sourceKey support-calls \
+  --visibility org
+```
+
+`create-source` returns `ingestToken` in the response **once** — it is stored
+only as a SHA-256 hash (`ingestTokenHash`) on the source row, so it cannot be
+retrieved again later. Surface it to the user immediately (e.g. for wiring
+into an external system's webhook config) rather than assuming you can read
+it back with `get-source`.
+
+## Source Health States
+
+`get-brain-health` (`readBrainHealth` in `server/lib/brain-health.ts`) is the
+single action to check before telling a user "your source is broken" or
+"nothing has synced yet." Each source gets one deterministic `health` value:
+
+| Health | Meaning |
+| --- | --- |
+| `error` | Source `status === "error"`, has `lastError`, or its latest sync run failed. |
+| `paused` | Source `status` is `paused` or `archived`. |
+| `needs_setup` | Slack source with no configured channel allow-list yet (`channelIds`/`channels`/`allowedChannels` all empty). |
+| `needs_sync` | Auto-sync-eligible provider (slack/granola/github) that has never completed a sync (`lastSyncedAt` is null). |
+| `stale` | Past its computed `nextSyncAt` by more than a 15-minute grace window. |
+| `healthy` | None of the above. |
+
+`get-brain-health` also reports `distillationQueue` counts (`pending`,
+`failed`, `stale` — a `processing` row untouched for 15+ minutes counts as
+stale), `proposals.pending`, `sources.attention` (every non-healthy source),
+and ordered `setup.nextSteps`. Read this before diagnosing a "why isn't X in
+Brain yet" question — it is cheaper and more reliable than inspecting
+individual sources by hand.
+
+## Running a Sync
+
+- `sync-source --sourceId=<id>` runs one source's connector immediately
+  (requires `editor` access on that source). Slack scans only its allow-listed
+  channels; Granola polls accessible notes; GitHub imports approved
+  repository issues/PRs.
+- `sync-due-sources` sweeps every accessible source whose `nextSyncAt` has
+  passed. Prefer this for "catch everything up" requests instead of listing
+  sources and calling `sync-source` in a loop.
+- Auto-sync only applies to `slack`, `granola`, and `github` sources, and only
+  when the source's own config doesn't explicitly set `autoSync: false`
+  (`sourceAutoSync` in `brain-health.ts`). `manual`, `generic`, and `clips`
+  sources are push/import-driven, not polled — there's no `nextSyncAt` to
+  wait on for those.
+
+## Credential Resolution Order
+
+Every provider-backed source resolves its credential in this order (never
+skip ahead or ask for a duplicate token if an earlier tier already has one):
+
+1. Granted `workspace_connections` / `workspace_connection_grants` for
+   `appId=brain` — a shared credential another app or Dispatch already
+   connected and granted to Brain.
+2. Backward-compatible Brain-local SQL credentials (legacy, pre-workspace-grant
+   sources).
+3. Registered vault secrets scoped to the same user/org/workspace.
+
+Brain source credentials **do not** fall back to raw deploy-level environment
+variables — `.env`/`.env.local` alone will not satisfy a source's credential
+check. `list-connection-providers` reports per-provider readiness
+(`connected`, `granted`, `needs_grant`, `not_connected`) plus credential
+health, so check that before telling a user to paste a new token — if a
+provider shows `needs_grant`, the fix is granting Brain access to the existing
+connection, not creating a new one.
+
+## Editing And Removing Sources
+
+- `update-source` edits title, config, or visibility on an existing source.
+- `delete-source` is a hard delete — there's no soft-archive alternative
+  exposed as an action; setting `status: "paused"` via `update-source` is the
+  reversible way to stop a source without losing its captures.
+- `list-sources --provider=<p> --includeArchived=<bool>` is scoped by
+  `accessFilter` — sharing/visibility rules apply the same way they do for
+  knowledge and proposals.
+
+## Related Skills
+
+- `brain` — distillation, retrieval, and publish-tier mechanics once a
+  capture exists.
+- `brain-runbook` — Slack rollout steps, distillation worker internals,
+  scheduled sync cron wiring, demo/eval seeding, and the generic ingest
+  webhook payload shape.
+- `sharing` — the `accessFilter`/`assertAccess` pattern used throughout source
+  and capture reads.

package/corpus/templates/brain/AGENTS.md

@@ -12,6 +12,10 @@ Detailed retrieval, capture, connector, and feature rules live in
 - Never hardcode API keys, tokens, webhook URLs, signing secrets, private Builder/internal data, customer data, or credential-looking literals. Use secrets/OAuth/runtime configuration and obvious placeholders in examples.
 - Use Brain actions for ingestion, search, retrieval, distillation, capture,
   review, and connector work. Do not bypass access checks or ownable scopes.
+- **Call `get-brain-settings` before answering, searching broadly, or
+  distilling** if settings aren't already in context. The returned guidance
+  encodes every retrieval and distillation rule below as concrete policy —
+  read `brain` for how `sourcePolicy` and publish-tier gating actually work.
 - Retrieval answers must be evidence-backed. Cite or summarize source context and
   clearly separate facts from inference.
 - Do not fabricate source contents, dates, people, permissions, or connector
@@ -21,32 +25,113 @@ Detailed retrieval, capture, connector, and feature rules live in
 - Use `view-screen` when the active source, review item, search, or collection is
   unclear.
 - For connector work, use existing workspace integration grants when available;
-  do not duplicate provider tokens into Brain.
+  do not duplicate provider tokens into Brain. `list-connection-providers`
+  shows readiness (`connected`, `granted`, `needs_grant`, `not_connected`) per
+  provider before you ask the user for another credential.
 - Source sync actions are convenience readers, not integration limits. For ad
   hoc provider analysis or questions that need an endpoint/filter/payload the
   source actions do not model, call `provider-api-catalog` /
   `provider-api-docs`, then `provider-api-request` against the provider's real
   HTTP API. Use `connectionId` for a specific shared grant and `accountId` for a
   specific OAuth account.
+- Sources support exactly five providers: `manual`, `generic`, `clips`,
+  `slack`, `granola`, `github` (`sourceProviderSchema` in `actions/_schemas.ts`).
+  `create-source` rejects anything else.
+- **Evidence quotes must be exact substrings.** `write-knowledge` calls
+  `validateEvidence`, which throws if `evidence[].quote` is not found verbatim
+  in the referenced capture's content. Copy the quote from `get-capture`
+  output — do not paraphrase, trim mid-sentence in a way that changes the
+  substring, or reconstruct it from memory.
+- `review-proposal` and `approve-proposal`/`reject-proposal` overlap:
+  `review-proposal` is the general one (`decision`: `approve` | `reject` |
+  `needs_changes`); `approve-proposal` and `reject-proposal` are narrower
+  single-purpose actions with the same underlying effect. Any of them is
+  correct; don't call more than one for the same proposal.
+
+## Action Map
+
+| Action                                                                                            | Purpose                                                                                                 |
+| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| `get-brain-settings`                                                                              | Identity, tone, `sourcePolicy`, citation, and distillation settings — read first.                       |
+| `search-everything`                                                                               | Broad search across knowledge + captures + sources, plus `federatedCoverage`.                           |
+| `search-knowledge`                                                                                | SQL text search over distilled knowledge only.                                                          |
+| `ask-brain`                                                                                       | Cited-answer endpoint: reviewed knowledge, capped raw-capture fallback, citations, `federatedCoverage`. |
+| `get-knowledge` / `list-knowledge`                                                                | Read one or list distilled knowledge records.                                                           |
+| `get-capture` / `list-captures`                                                                   | Read one or list raw captures (redacted by default; `includeRawContent` for exact quotes).              |
+| `import-capture` / `import-transcript`                                                            | Ingest a generic capture or a meeting transcript; auto-creates a `manual` source.                       |
+| `enqueue-distillation` / `mark-capture-distilled`                                                 | Queue a capture for distillation; close out the queue row when done.                                    |
+| `write-knowledge`                                                                                 | Write/update durable knowledge; may return a pending proposal — see Publish Tiers below.                |
+| `review-proposal` / `approve-proposal` / `reject-proposal` / `list-proposals` / `update-proposal` | Human-review workflow for gated writes.                                                                 |
+| `set-knowledge-canonical`                                                                         | Mirror/unmirror approved knowledge into `context/company-brain/...` workspace resources.                |
+| `create-source` / `update-source` / `delete-source` / `list-sources` / `get-source`               | Source lifecycle across the five providers.                                                             |
+| `sync-source` / `sync-due-sources`                                                                | Run one connector now, or sweep all due sources.                                                        |
+| `get-brain-health`                                                                                | Setup/source health, sync freshness, queue and proposal counts, next steps.                             |
+| `list-connection-providers`                                                                       | Per-provider workspace-connection readiness and credential health.                                      |
+| `test-slack-connection` / `run-slack-pilot`                                                       | Slack credential/channel validation and bounded first-sync report.                                      |
+| `provider-api-catalog` / `provider-api-docs` / `provider-api-request`                             | Raw provider HTTP calls beyond the source actions.                                                      |
+| `run-demo-eval` / `run-retrieval-eval` / `seed-demo-data`                                         | Demo corpus and offline eval checks (see `brain-runbook`).                                              |
 
 ## Application State
 
 - `navigation` exposes ask/search, sources, review, memory, connector, and
   selected item context.
-- `navigate` moves the UI to ask, source, review, and settings surfaces.
+- `navigate` moves the UI to a typed `view`: `home`, `ask`, `search`,
+  `sources`, `source`, `capture`, `knowledge`, `review`, `proposals`,
+  `extensions`, `ops`, or `settings`, with matching `sourceId` / `captureId` /
+  `knowledgeId` / `proposalId` / `extensionId` / `query` / `provider` /
+  `status` / `issue` params.
 - Use retrieval actions for full source context instead of ambient screen text.
 
+## Retrieval Policy Is Configurable — Read It, Don't Assume
+
+`sourcePolicy` (in Brain settings) changes what `ask-brain` and
+`search-everything` are allowed to answer from, and it is enforced in code,
+not just documented:
+
+| `sourcePolicy`       | `rawCaptureFallback` | Behavior                                                                                                                                                                      |
+| -------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `strict`             | `never-answer`       | Reviewed knowledge only. If knowledge is missing/thin, say so — never fall back to raw captures as answer support.                                                            |
+| `balanced` (default) | `thin-results`       | Prefer reviewed knowledge; fall back to raw captures only when knowledge is missing or combined summary+body text is under ~260 chars, and label them as raw capture matches. |
+| `exploratory`        | `allowed-leads`      | Always include accessible raw captures/sources alongside knowledge, clearly labeled as unreviewed leads.                                                                      |
+
+`requireCitations` (default true) additionally blocks `ask-brain` from
+returning an answer with no usable citation — it returns a policy-explanation
+message instead of a bare summary when that happens.
+
+## Publish Tiers And Proposal Gating
+
+`write-knowledge` writes at a `publishTier`: `private` (draft, private
+visibility), `team`, or `company` (published, org visibility) — default comes
+from `settings.defaultPublishTier`. A `company`-tier write becomes a
+**proposal** (`mode: "proposal"`, held for human review) instead of publishing
+immediately when ALL of:
+
+- `proposalMode !== "never"`, and
+- `tier === "company"`, and
+- `settings.requireApprovalForCompanyKnowledge` is true, and
+- it is NOT a high-confidence auto-publish (`confidence >= 90` AND it's a new
+  record, no `knowledgeId` AND nothing was redacted).
+
+Setting `proposalMode: "always"` forces a proposal regardless of tier/settings;
+`proposalMode: "never"` only works when the caller also has bypass access
+(e.g. `approve-proposal`/`review-proposal` set it internally). If
+`write-knowledge` returns `mode: "proposal"`, leave it in review unless the
+user explicitly asks to approve it now.
+
 ## Skills
 
 Read the relevant skill before deeper work:
 
-- `brain` for core ingestion, distillation, retrieval, and review flows.
-- `ask-across-everything` for cross-source answers.
+- `brain` for core ingestion, distillation, retrieval, and review flows —
+  including exact publish-tier/proposal mechanics and capture sanitization.
+- `ask-across-everything` for cross-source answers and `federatedCoverage`
+  delegation.
+- `ingestion-and-connectors` for source lifecycle, health states, Slack
+  backfill rollout, and provider credential resolution order.
 - `brain/RUNBOOK.md` (the `brain-runbook` skill) for internal architecture,
-  ops, and rollout detail: search layers, Slack backfill, distillation worker,
-  connection resolution, scheduled sync, demo/eval internals, and generic
-  ingest. (This material moved out of `AGENTS.md`; read it only when operating
-  or debugging Brain internals.)
+  ops, and rollout detail: search layers, distillation worker internals,
+  scheduled sync, demo/eval internals, and generic ingest payloads. Read it
+  only when operating or debugging Brain internals.
 - `adding-a-feature` for Brain feature changes.
 - `actions`, `real-time-sync`, `security`, `frontend-design`, and `shadcn-ui`
   for framework work. The `actions` skill includes the shared provider API

package/corpus/templates/brain/app/components/brain/CanonicalPreviewSheet.tsx

@@ -1,6 +1,8 @@
 import { useT } from "@agent-native/core/client";
-import { Badge } from "@agent-native/toolkit/ui/badge";
-import { Button } from "@agent-native/toolkit/ui/button";
+import { IconAlertTriangle, IconBook, IconFileText } from "@tabler/icons-react";
+
+import { Badge } from "@/components/ui/badge";
+import { Button } from "@/components/ui/button";
 import {
   Sheet,
   SheetContent,
@@ -8,9 +10,8 @@ import {
   SheetFooter,
   SheetHeader,
   SheetTitle,
-} from "@agent-native/toolkit/ui/sheet";
-import { Textarea } from "@agent-native/toolkit/ui/textarea";
-import { IconAlertTriangle, IconBook, IconFileText } from "@tabler/icons-react";
+} from "@/components/ui/sheet";
+import { Textarea } from "@/components/ui/textarea";
 
 export interface CanonicalPreviewData {
   source: "knowledge" | "proposal";

package/corpus/templates/brain/app/components/brain/Surface.tsx

@@ -1,11 +1,3 @@
-import { Badge } from "@agent-native/toolkit/ui/badge";
-import {
-  Card,
-  CardContent,
-  CardHeader,
-  CardTitle,
-} from "@agent-native/toolkit/ui/card";
-import { Skeleton } from "@agent-native/toolkit/ui/skeleton";
 import {
   IconAlertTriangle,
   IconCircleCheck,
@@ -14,6 +6,9 @@ import {
   IconInfoCircle,
 } from "@tabler/icons-react";
 
+import { Badge } from "@/components/ui/badge";
+import { Card, CardContent, CardHeader, CardTitle } from "@/components/ui/card";
+import { Skeleton } from "@/components/ui/skeleton";
 import { cn } from "@/lib/utils";
 
 export function PageHeader({

package/corpus/templates/brain/app/components/layout/Layout.tsx

@@ -6,18 +6,18 @@ import {
   useAgentChatHomeHandoffLinks,
   useT,
 } from "@agent-native/core/client";
-import { Button } from "@agent-native/toolkit/ui/button";
-import {
-  Sheet,
-  SheetContent,
-  SheetDescription,
-  SheetTitle,
-} from "@agent-native/toolkit/ui/sheet";
 import { IconMenu2 } from "@tabler/icons-react";
 import { useEffect, useState } from "react";
 import { useLocation, useNavigate } from "react-router";
 
 import { Sidebar } from "@/components/layout/Sidebar";
+import { Button } from "@/components/ui/button";
+import {
+  Sheet,
+  SheetContent,
+  SheetDescription,
+  SheetTitle,
+} from "@/components/ui/sheet";
 import { TAB_ID } from "@/lib/tab-id";
 
 const SIDEBAR_COLLAPSE_KEY = "brain.sidebar.collapsed";

package/corpus/templates/brain/app/components/layout/Sidebar.tsx

@@ -9,12 +9,6 @@ import {
 } from "@agent-native/core/client";
 import { ExtensionsSidebarSection } from "@agent-native/core/client/extensions";
 import { OrgSwitcher } from "@agent-native/core/client/org";
-import { Input } from "@agent-native/toolkit/ui/input";
-import {
-  Tooltip,
-  TooltipContent,
-  TooltipTrigger,
-} from "@agent-native/toolkit/ui/tooltip";
 import {
   IconArchive,
   IconDots,
@@ -34,6 +28,12 @@ import {
   DropdownMenuItem,
   DropdownMenuTrigger,
 } from "@/components/ui/dropdown-menu";
+import { Input } from "@/components/ui/input";
+import {
+  Tooltip,
+  TooltipContent,
+  TooltipTrigger,
+} from "@/components/ui/tooltip";
 import { navItems } from "@/lib/brain";
 import { cn } from "@/lib/utils";
 

package/corpus/templates/brain/app/components/ui/badge.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/badge";

package/corpus/templates/brain/app/components/ui/button.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/button";

package/corpus/templates/brain/app/components/ui/card.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/card";

package/corpus/templates/brain/app/components/ui/input.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/input";

package/corpus/templates/brain/app/components/ui/label.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/label";

package/corpus/templates/brain/app/components/ui/progress.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/progress";

package/corpus/templates/brain/app/components/ui/select.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/select";

package/corpus/templates/brain/app/components/ui/separator.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/separator";

package/corpus/templates/brain/app/components/ui/sheet.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/sheet";

package/corpus/templates/brain/app/components/ui/skeleton.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/skeleton";

package/corpus/templates/brain/app/components/ui/switch.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/switch";

package/corpus/templates/brain/app/components/ui/table.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/table";

package/corpus/templates/brain/app/components/ui/textarea.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/textarea";

package/corpus/templates/brain/app/components/ui/toolkit-provider.tsx

@@ -0,0 +1,12 @@
+import { ToolkitProvider, type ToolkitComponents } from "@agent-native/toolkit";
+import type { ReactNode } from "react";
+
+import { Button } from "@/components/ui/button";
+
+const components: ToolkitComponents = {
+  Button: Button as ToolkitComponents["Button"],
+};
+
+export function AppToolkitProvider({ children }: { children: ReactNode }) {
+  return <ToolkitProvider components={components}>{children}</ToolkitProvider>;
+}

package/corpus/templates/brain/app/components/ui/tooltip.tsx

@@ -0,0 +1 @@
+export * from "@agent-native/toolkit/ui/tooltip";

package/corpus/templates/brain/app/global.css

@@ -3,6 +3,7 @@
 
 @import "tailwindcss";
 @import "@agent-native/core/styles/agent-native.css";
+@import "@agent-native/toolkit/styles.css";
 
 @source "./**/*.{ts,tsx}";
 

package/corpus/templates/brain/app/hooks/use-distillation-bridge.ts

@@ -78,7 +78,6 @@ export function useDistillationBridge(): void {
     } as any,
     {
       refetchInterval: POLL_INTERVAL_MS,
-      refetchIntervalInBackground: true,
       retry: false,
     },
   );
@@ -154,12 +153,18 @@ export function useDistillationBridge(): void {
     }
 
     void tick();
-    const handle = setInterval(tick, POLL_INTERVAL_MS);
     return () => {
       cancelled = true;
-      clearInterval(handle);
     };
-  }, [capturesKey, dispatchableCaptures]);
+    // `capturesQuery.dataUpdatedAt` bumps on every completed refetch even when
+    // React Query's structural sharing keeps `capturesQuery.data` (and thus
+    // `dispatchableCaptures`/`capturesKey`) referentially/content-equal to the
+    // previous fetch. Keying on it (in addition to `capturesKey`) guarantees
+    // this effect re-runs on the query's `refetchInterval` cadence — not just
+    // when the queued-capture set actually changes — so already-fetched but
+    // not-yet-claimed/dispatched items keep getting re-evaluated on every
+    // poll instead of only on the tick they first appear.
+  }, [capturesKey, dispatchableCaptures, capturesQuery.dataUpdatedAt]);
 }
 
 function buildMessage(capture: BrainCaptureReviewItem) {