@agent-native/core 0.152.1 → 0.153.0

package/corpus/templates/factory/.agents/skills/turn-into-app/references/spreadsheet-source.md

@@ -0,0 +1,148 @@
+# Spreadsheet source review
+
+Use this reference after a workbook upload or Google Sheets link is supplied to
+`/turn-into-app`. It defines the bounded review contract before app creation.
+
+## 1. Establish the source boundary
+
+Record the source before interpreting it:
+
+| Field        | Record                                                                            |
+| ------------ | --------------------------------------------------------------------------------- |
+| Source kind  | `xlsx`, `xls`, `csv`, or Google Sheets URL                                        |
+| Provenance   | Original file name or spreadsheet ID and URL; never credentials or workbook bytes |
+| Access       | Upload preview, authenticated provider read, or unavailable                       |
+| Coverage     | Worksheet names, selected range(s), row/column bounds, and sample counts          |
+| Completeness | Complete within the requested bound, partial, truncated, unreadable, or empty     |
+| Refresh      | One-time snapshot or live refreshable source                                      |
+
+For an uploaded XLS/XLSX file, the framework preview contains worksheet names,
+dimensions, and representative displayed values within bounds. It does not
+currently preserve cell fills or font colors in that text preview. Treat the
+original workbook as the formatting authority only when a tool actually returns
+cell formatting metadata. Never describe a text-only upload as style-verified.
+
+For a Google Sheets URL:
+
+1. Parse the spreadsheet ID and preserve the original URL as provenance.
+2. Use the authenticated `google_drive` provider path. Inspect
+   `provider-api-catalog` first, use `provider-api-docs` if the endpoint or
+   fields are uncertain, and then call `provider-api-request`.
+3. Read spreadsheet metadata and only bounded worksheet/range data. Request
+   formatting metadata when the I/O decision depends on colors, including
+   `userEnteredFormat.backgroundColor` and
+   `userEnteredFormat.textFormat.foregroundColor` where the provider supports
+   it. Do not use a public export URL to bypass access.
+4. Preserve the spreadsheet ID, worksheet title, A1 range, account/connection
+   choice without secrets, row limits, and refresh behavior in the brief.
+
+Keep provider responses bounded. For large sheets, stage or save the response
+and reduce it with the available dataset/code tools. A failed page, truncated
+response, or unavailable connection is not an empty sheet.
+
+## 2. Infer cells and ranges, then show the evidence
+
+Classify source material into three separate buckets. Include representative
+cell addresses or ranges and the evidence behind each classification.
+
+| Bucket             | Default signal                                                                                                     | App treatment                                                          |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
+| Inputs             | Yellow cell background, editable assumptions, user-entered constants, or labels such as `assumption` / `driver`    | Editable controls or bounded source parameters                         |
+| Outputs            | Blue text, formula-derived result cells, summary blocks, or labels such as `forecast` / `recommendation`           | Read-only results, charts, recommendations, exports, or review actions |
+| Static historicals | Black text used intentionally for prior-period/source records, raw rows, or labels such as `actual` / `historical` | Read-only context; never turn into editable inputs by default          |
+
+These are conventions, not permission to guess. A default black font with no
+explicit style metadata is not enough to label a range as historical. Resolve
+conflicts using labels, formulas, neighboring headers, repeated patterns, and
+the user's stated goal. If the evidence still conflicts, lower confidence and
+ask the user to confirm the proposed mapping.
+
+Keep source cells and app behavior distinct:
+
+- `Source inputs` are the workbook cells or ranges the user is expected to
+  change or refresh.
+- `Source outputs` are the workbook cells or ranges the source already derives
+  or presents.
+- `Static historicals` are context the app may filter, compare, or summarize,
+  but should not edit.
+- `App outputs` are the new app's visible results, saved records, exports,
+  alerts, or downstream handoffs. Do not invent these until the repeatable job
+  or user confirmation makes them clear.
+
+## 3. Offer candidate apps, not a tab dump
+
+Group related worksheets into candidate repeatable jobs. A candidate should
+have a recognizable user, trigger, inputs, transformation or judgment, and
+outputs. Utility tabs such as lookups, raw imports, instructions, pivots, and
+calculation helpers can support a candidate without becoming destinations.
+
+Present a compact Q&A review with multi-select options. In generated app code,
+use `askUserQuestion` from `@agent-native/core/client/agent-chat` with
+`allowMultiple: true`, stable candidate IDs as option values, and
+`allowFreeText: true` for corrections. It renders inline in the agent panel;
+do not build a custom modal. Each option should fit in a scannable row or
+choice card:
+
+```text
+Candidate: Pipeline forecast
+Uses: Assumptions, Historical Pipeline, Forecast
+Inputs: yellow assumptions in Assumptions!B4:B12 (high confidence)
+Outputs: blue forecast summary in Forecast!B3:H10 (medium confidence)
+Historical context: Historical Pipeline!A1:K500
+Question: Confirm that forecast assumptions should be editable?
+```
+
+Mark the strongest recommendation with `recommended: true`, but do not silently
+select it. Let the user select none, one, or several candidates, correct a
+proposed tab/range, or answer the unresolved question. Keep each question to
+2-4 grouped candidate jobs; for a larger workbook, group related tabs into
+jobs rather than showing a tab dump or asking a separate question for every
+worksheet. If there is only one high-confidence candidate, keep the review
+compact and ask for confirmation only when the I/O mapping or source access is
+unclear.
+
+When several candidates are selected, pass a stable candidate ID, display name,
+source worksheet/ranges, I/O mapping, confidence, and confirmation status for
+each. The generated app should expose them as separate named left-navigation
+destinations or tabs, not merge them into an opaque dashboard and not create a
+separate workspace app for every worksheet.
+
+## 4. Confirm before building or publishing
+
+The confirmation view is a source-integrity checkpoint, not a product-design
+questionnaire. Show:
+
+- the source file or spreadsheet ID and snapshot/live choice;
+- selected candidate destinations and their source tabs/ranges;
+- editable inputs, read-only outputs, and static historical context;
+- the evidence and confidence for each mapping;
+- truncation, unreadable, missing-connection, and refresh limitations;
+- the app outputs/actions that will be created.
+
+Use clear actions such as `Confirm and build`, `Edit mapping`, and `Use a
+different source`. If the host has a structured question or multi-select UI,
+use it. Otherwise, ask one concise assistant message that presents the same
+options and requires an explicit confirmation/correction before handoff.
+
+After confirmation, the online host may call
+`start-workspace-app-creation`; the Builder run itself remains autonomous and
+must record any remaining non-blocking assumptions. In a local generated app,
+persist the confirmation state in SQL/application state and keep the user on
+the review surface while the agent builds. Never claim a full import, live
+refresh, or output write until the corresponding source/action has succeeded.
+
+## 5. Failure and recovery states
+
+Keep these states distinct in the review and in the handoff:
+
+- `unreadable` - parser/provider could not read the source;
+- `partial` - only some worksheets, ranges, rows, or pages were read;
+- `truncated` - the bounded preview ended before full coverage;
+- `empty` - the requested readable range contains no values;
+- `not-connected` - authenticated Google access is required but unavailable;
+- `confirmed` - the user approved the candidate and I/O mapping.
+
+For unreadable or not-connected sources, request a CSV/XLSX export or the
+required connection. For partial or truncated sources, continue only with a
+clearly bounded snapshot or ask for a narrower range. Do not coerce any of
+these states into a successful empty source.

package/corpus/templates/factory/.agents/skills/workspace-conventions/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: workspace-conventions
+description: >-
+  Shared conventions for a multi-app Agent Native workspace: finding
+  version-matched framework docs and source, shared vs app-owned code, file and
+  blob storage, env and secrets, agent scratch files, and Dispatch Resources.
+  Use when working across workspace apps, storing files or credentials, or
+  looking up framework APIs.
+scope: dev
+---
+
+# Workspace Conventions
+
+The long-form detail behind the workspace `AGENTS.md` core rules. Read this
+before adding shared code, storing files or secrets, creating workspace
+resources, or looking up framework APIs.
+
+## Framework Docs Lookup
+
+Read `agent-native-docs` for the lookup workflow (`framework-search` first, then
+the focused `docs-search` / `source-search` readers, and the `rg` fallback).
+
+The workspace-specific slugs it does not list are `workspace` and
+`multi-app-workspace`. Feature flags and other specialized workflows are
+optional; read their skill only when the app uses them. Use package docs for framework APIs,
+the package corpus for reusable framework/template patterns, and this
+`AGENTS.md` plus `.agents/skills/` for workspace-specific conventions.
+
+Before building common workspace or agent UI, read `agent-native-toolkit` to
+inventory existing public kits and installed package seams. Read
+`customizing-agent-native` before adapting shared UI. Use the supported
+ladder: configure → compose → eject the smallest unit → propose a shared seam.
+Preview before `--apply`, commit `agent-native.ejections.json`, and never edit
+`node_modules` or eject protected runtime contracts.
+
+## Shared Conventions
+
+- All AI/LLM behavior goes through the app's agent chat. UI and server code
+  must not call model providers, AI SDK `generateText()` / `streamText()`, or
+  other inline LLM APIs directly. Use `sendToAgentChat()` for local app-agent
+  work, including hidden `context` and `submit: false` prefill/review flows.
+  Keep actions deterministic and focused. If a workflow is framed as research,
+  analysis, generation, recommendation, or synthesis, let the agent
+  orchestrate provider/data actions in the open AgentSidebar instead of hiding
+  the work in one opaque action or a separate follow-up textbox.
+  Only use `useAgentChatContext`, `setAgentChatContextItem`,
+  `listAgentChatContext`, `removeAgentChatContextItem`, and
+  `clearAgentChatContext` when UI needs two-way sync with staged context chips.
+  Read `.agents/skills/delegate-to-agent/SKILL.md` before building agent-driven
+  UI or "AI" features.
+- Put shared code in `packages/shared` only when multiple apps need it.
+- Keep app-specific screens, actions, state, and skills inside `apps/<app>`.
+- SQL is for structured records, metadata, references, and searchable text. Store
+  large files/blob payloads (base64, `data:` URLs, images, video/audio, PDFs,
+  ZIPs, screenshots, thumbnails, session replay chunks) in configured file/blob
+  storage and persist only URLs, ids, or handles.
+- Store shared runtime configuration in the workspace root `.env`; use
+  `apps/<app>/.env` only for app-specific overrides. Never hardcode API keys,
+  tokens, webhook URLs, signing secrets, private Builder/internal data, customer
+  data, or credential-looking literals in source, docs, prompts, fixtures,
+  application state, action responses, or generated app content. Use
+  secrets/OAuth/runtime configuration and obvious placeholders in examples.
+- Each app deploys its own `/*` page function, and that function ships whatever
+  the app's server bundle depends on — including a dependency only a background
+  job uses. Before an app takes on a heavy runtime (headless browser, ffmpeg,
+  media processing, ML), read `.agents/skills/performance/SKILL.md` §9 and keep
+  that work in a background function or job. A dependency belonging to one app
+  does not belong in `packages/shared`.
+- Prefer framework defaults until the workspace has a real custom rule,
+  component, plugin, action, or skill to share.
+- Keep the Workspace files view for user-authored or user-requested resources.
+  Agents may create hidden `agent_scratch` resources for temporary working
+  notes, scripts, task plans, or intermediate outputs, but should promote them
+  to normal workspace visibility only when the user explicitly asks to keep or
+  manage the file.
+- Runtime-editable global resources can be managed from Dispatch Resources.
+  Use `AGENTS.md` or `instructions/<slug>.md` for always-on guardrails,
+  `skills/<slug>/SKILL.md` for workspace skills, `context/<slug>.md` for
+  personas/positioning/messaging/company facts/brand guidelines, and
+  `agents/<slug>.md` for custom agent profiles. Scope them to All apps when
+  every workspace app should inherit them. All-app resources are inherited at
+  runtime; do not copy or sync them into individual apps.
+
+## Related Skills
+
+- **adding-workspace-apps** — Creating and mounting a new app under `apps/`.
+- **agent-native-docs** — The full docs and source-corpus lookup workflow.
+- **agent-native-toolkit** — Inventory of shared workspace and agent UI.
+- **customizing-agent-native** — The configure → compose → eject ladder.
+- **delegate-to-agent** — Routing every AI feature through the agent chat.
+- **performance** — Load cost, and (§9) cold-start artifact size per app.
+- **secrets** — Registering API keys and service credentials.
+- **storing-data** — Where structured data and large payloads belong.

package/corpus/templates/factory/AGENTS.md

@@ -29,6 +29,9 @@ decisions, feedback, agent runs, and provider audit records.
   also requires a verified Factory Builder run.
 - Graph edits create immutable blueprint versions. AI proposes with `source=ai`;
   a person reviews and publishes through the same action surface.
+- Provider credentials belong to Dispatch/shared workspace integrations, never
+  to a Factory or Factory graph. Agents use shared provider APIs and connected
+  MCP tools through the workspace grant boundary.
 
 ## Application state
 
@@ -45,7 +48,7 @@ decisions, feedback, agent runs, and provider audit records.
 
 | Action | Purpose |
 | --- | --- |
-| `list-triage-items` / `get-triage-item` | Inspect queue and evidence. |
+| `list-triage-items` / `get-triage-item` | Inspect queue and evidence; scheduled reviewers must pass `needsReview: true` with a bounded `source` and `limit`. |
 | `poll-slack-channel` | Observe Slack history; never writes to Slack. |
 | `get-slack-feedback-context` | Read the bounded full Slack thread before classification. |
 | `poll-github-sources` / `poll-sentry-errors` | Observe bounded GitHub and Sentry source queues. |
@@ -64,6 +67,7 @@ decisions, feedback, agent runs, and provider audit records.
 | `list-factories` / `get-factory-graph` | Inspect Factory definitions, graph versions, and live evidence metrics. |
 | `save-factory-graph` | Create or version a complete visual graph; never starts provider work. |
 | `list-factory-comments` / `add-factory-comment` | Read or attach comments to a canvas, node, or edge. |
+| `provider-api-catalog` / `provider-api-docs` / `provider-api-request` | Discover and use connected provider APIs with shared workspace credentials; never request raw keys. |
 
 Rules start in shadow mode; hard guards always apply. Organization automations
 execute stored prompts, and every external mutation needs a durable run,
@@ -72,6 +76,11 @@ automations are seeded. Use the visual editor for graph changes and agent chat
 for proposals; persist complete graphs with `save-factory-graph`. Change rules
 through triage rule actions, never graph JSON.
 
+The Slack, GitHub, and Sentry pollers are bounded ingestion adapters for the
+legacy default triage queue. They do not define the complete tool surface.
+Interactive and scheduled agents may discover additional connected provider or
+MCP tools through the shared workspace context.
+
 ## Source Changes
 
 Before building common workspace or agent UI, read `agent-native-toolkit`; read

package/corpus/templates/factory/README.md

@@ -35,17 +35,28 @@ finds that existing organization and seeds its organization-owned automations.
 If Dispatch synced the vault into a different organization, set
 `AGENT_VAULT_ORG_ID` to that existing org id instead of creating a new org.
 
-Connect Slack in Dispatch or in Settings -> Integrations. Factory resolves
-Slack, GitHub, Sentry, and Builder credentials from the shared workspace vault
-and only uses matching deployment env vars as a last-resort fallback. All apps
-that read shared `app_secrets` rows must use the same
+Connect providers in Dispatch or in Settings -> Integrations. Factory resolves
+Slack, GitHub, Sentry, Builder, and other supported provider credentials from
+the shared workspace vault and only uses matching deployment env vars as a
+last-resort fallback. Factory never stores keys per factory. All apps that read
+shared `app_secrets` rows must use the same
 `WORKSPACE_SECRETS_ENCRYPTION_KEY` (or the workspace's existing shared
 encryption fallback). Never copy raw tokens between apps or add a second
 env-only read in a provider client.
 
-In Factory, set the Slack workspace, channel ID, channel name, repository, and
-polling switch. The default scheduler polls once per minute, evaluates a
-bounded page, and preserves errors for reconciliation.
+Factory's default observer still keeps organization-scoped source metadata -
+such as a Slack channel, repository, or Sentry project - for its normalized
+queue adapters. That metadata is not a credential or a per-factory integration
+setup. GitHub issue polling defaults to hourly; Slack and pull-request checks
+use shorter bounded cadences because those sources can need faster feedback.
+Every poll preserves errors for reconciliation.
+
+Factory agents can discover connected provider APIs with
+`provider-api-catalog`, inspect their docs with `provider-api-docs`, and call
+them through `provider-api-request`. Scheduled Factory runs also receive the
+workspace's connected MCP tools, subject to the same workspace and request
+scope gates. The three normalized pollers are compatibility adapters for the
+default triage queue, not the agent's capability limit.
 
 The generic Slack bot is wired to Factory. Mention `@agent-native` in a feedback
 thread to inspect the linked item, explain its decision, tune a rule, or say

package/corpus/templates/factory/actions/list-triage-items.ts

@@ -1,5 +1,5 @@
 import { defineAction } from "@agent-native/core/action";
-import { and, desc, eq } from "drizzle-orm";
+import { and, desc, eq, inArray } from "drizzle-orm";
 import { z } from "zod";
 
 import { getDb } from "../server/db/index.js";
@@ -16,26 +16,32 @@ import {
 
 export default defineAction({
   description:
-    "List the Factory observation queue. Results are scoped to the active workspace and include the latest shadow decision summary.",
+    "List the Factory observation queue. Results are scoped to the active workspace and include the latest shadow decision summary. Scheduled reviewers must pass needsReview true with a bounded source and limit so unchanged items are not re-reviewed.",
   schema: z.object({
     status: triageItemStatusSchema.optional(),
     source: triageSourceSchema.optional(),
+    needsReview: z.boolean().default(false),
     limit: z.coerce.number().int().min(1).max(100).default(50),
   }),
   http: { method: "GET" },
   readOnly: true,
-  run: async ({ status, source, limit }, context) => {
+  run: async ({ status, source, needsReview, limit }, context) => {
     const { userEmail, orgId } = await requireWorkspaceMember(
       workspaceMemberIdentityFromContext(context),
     );
     const db = getDb();
+    const reviewStatuses = source === "github" ? ["pr_observed"] : ["received"];
     const items = await db
       .select()
       .from(triageItems)
       .where(
         and(
           eq(triageItems.orgId, orgId),
-          status ? eq(triageItems.status, status) : undefined,
+          needsReview
+            ? inArray(triageItems.status, reviewStatuses)
+            : status
+              ? eq(triageItems.status, status)
+              : undefined,
           source ? eq(triageItems.source, source) : undefined,
         ),
       )

package/corpus/templates/factory/actions/poll-github-sources.ts

@@ -13,6 +13,10 @@ import { recordFactoryAudit } from "../server/triage/audit.js";
 import { createGitHubClient } from "../server/triage/github-client.js";
 import { itemDedupeKey } from "../server/triage/ids.js";
 import { mergeTriageMetadata } from "../server/triage/metadata.js";
+import {
+  hasTriageSourceChanged,
+  statusAfterTriageSourceUpdate,
+} from "../server/triage/review-state.js";
 
 function parseRepository(value: string): { owner: string; repo: string } {
   const match = /^([^/\s]+)\/([^/\s]+)$/.exec(value.trim());
@@ -94,6 +98,22 @@ export default defineAction({
             .join("\n\n"),
           updatedAt: issue.updatedAt,
         });
+        const summary = issue.body?.slice(0, 4_000) ?? null;
+        const sourceChanged = hasTriageSourceChanged(existing, {
+          sourceUrl: issue.htmlUrl,
+          title: issue.title,
+          summary,
+          lastSeenAt: issue.updatedAt,
+        });
+        const status = statusAfterTriageSourceUpdate(
+          existing?.status,
+          sourceChanged,
+          "received",
+        );
+        const updatedAt = sourceChanged ? now : (existing?.updatedAt ?? now);
+        const lastSeenAt = sourceChanged
+          ? issue.updatedAt
+          : (existing?.lastSeenAt ?? issue.updatedAt);
         await tx
           .insert(triageItems)
           .values({
@@ -102,15 +122,15 @@ export default defineAction({
             externalId: `${repositoryName}#${issue.number}`,
             sourceUrl: issue.htmlUrl,
             title: issue.title,
-            summary: issue.body?.slice(0, 4_000) ?? null,
-            status: existing?.status ?? "received",
+            summary,
+            status,
             risk: existing?.risk ?? "unknown",
             coverage: existing?.coverage ?? "complete",
             dedupeKey: id,
             metadataJson: metadata,
-            lastSeenAt: issue.updatedAt,
+            lastSeenAt,
             createdAt: existing?.createdAt ?? now,
-            updatedAt: now,
+            updatedAt,
             ownerEmail: existing?.ownerEmail ?? userEmail,
             orgId,
           })
@@ -119,10 +139,11 @@ export default defineAction({
             set: {
               sourceUrl: issue.htmlUrl,
               title: issue.title,
-              summary: issue.body?.slice(0, 4_000) ?? null,
+              summary,
+              status,
               metadataJson: metadata,
-              lastSeenAt: issue.updatedAt,
-              updatedAt: now,
+              lastSeenAt,
+              updatedAt,
             },
           });
         issueCount += 1;
@@ -153,6 +174,23 @@ export default defineAction({
           draft: pullRequest.draft,
           updatedAt: pullRequest.updatedAt,
         });
+        const summary = pullRequest.body?.slice(0, 4_000) ?? null;
+        const sourceChanged = hasTriageSourceChanged(existing, {
+          sourceUrl: pullRequest.htmlUrl,
+          title: pullRequest.title,
+          summary,
+          lastSeenAt: pullRequest.updatedAt,
+          headSha: pullRequest.headSha,
+        });
+        const status = statusAfterTriageSourceUpdate(
+          existing?.status,
+          sourceChanged,
+          "pr_observed",
+        );
+        const updatedAt = sourceChanged ? now : (existing?.updatedAt ?? now);
+        const lastSeenAt = sourceChanged
+          ? pullRequest.updatedAt
+          : (existing?.lastSeenAt ?? pullRequest.updatedAt);
         await tx
           .insert(triageItems)
           .values({
@@ -161,8 +199,8 @@ export default defineAction({
             externalId: `${repositoryName}#${pullRequest.number}`,
             sourceUrl: pullRequest.htmlUrl,
             title: pullRequest.title,
-            summary: pullRequest.body?.slice(0, 4_000) ?? null,
-            status: existing?.status ?? "pr_observed",
+            summary,
+            status,
             risk: existing?.risk ?? "unknown",
             repository: repositoryName,
             pullRequestNumber: pullRequest.number,
@@ -170,9 +208,9 @@ export default defineAction({
             coverage: existing?.coverage ?? "partial",
             dedupeKey: id,
             metadataJson: metadata,
-            lastSeenAt: pullRequest.updatedAt,
+            lastSeenAt,
             createdAt: existing?.createdAt ?? now,
-            updatedAt: now,
+            updatedAt,
             ownerEmail: existing?.ownerEmail ?? userEmail,
             orgId,
           })
@@ -181,13 +219,14 @@ export default defineAction({
             set: {
               sourceUrl: pullRequest.htmlUrl,
               title: pullRequest.title,
-              summary: pullRequest.body?.slice(0, 4_000) ?? null,
+              summary,
+              status,
               repository: repositoryName,
               pullRequestNumber: pullRequest.number,
               headSha: pullRequest.headSha,
               metadataJson: metadata,
-              lastSeenAt: pullRequest.updatedAt,
-              updatedAt: now,
+              lastSeenAt,
+              updatedAt,
             },
           });
         pullRequestCount += 1;

package/corpus/templates/factory/actions/poll-sentry-errors.ts

@@ -12,6 +12,10 @@ import {
 import { recordFactoryAudit } from "../server/triage/audit.js";
 import { itemDedupeKey } from "../server/triage/ids.js";
 import { mergeTriageMetadata } from "../server/triage/metadata.js";
+import {
+  hasTriageSourceChanged,
+  statusAfterTriageSourceUpdate,
+} from "../server/triage/review-state.js";
 import { createSentryClient } from "../server/triage/sentry-client.js";
 
 export default defineAction({
@@ -98,6 +102,25 @@ export default defineAction({
           firstSeen: issue.firstSeen,
           lastSeen: issue.lastSeen,
         });
+        const summary = [issue.culprit, `${issue.count} events`, issue.level]
+          .filter(Boolean)
+          .join(" · ")
+          .slice(0, 4_000);
+        const sourceChanged = hasTriageSourceChanged(existing, {
+          sourceUrl: issue.permalink,
+          title: issue.title,
+          summary,
+          lastSeenAt: issue.lastSeen,
+        });
+        const status = statusAfterTriageSourceUpdate(
+          existing?.status,
+          sourceChanged,
+          "received",
+        );
+        const updatedAt = sourceChanged ? now : (existing?.updatedAt ?? now);
+        const lastSeenAt = sourceChanged
+          ? issue.lastSeen
+          : (existing?.lastSeenAt ?? issue.lastSeen);
         await tx
           .insert(triageItems)
           .values({
@@ -106,18 +129,15 @@ export default defineAction({
             externalId: issue.id,
             sourceUrl: issue.permalink,
             title: issue.title,
-            summary: [issue.culprit, `${issue.count} events`, issue.level]
-              .filter(Boolean)
-              .join(" · ")
-              .slice(0, 4_000),
-            status: existing?.status ?? "received",
+            summary,
+            status,
             risk: existing?.risk ?? "unknown",
             coverage: existing?.coverage ?? "complete",
             dedupeKey: id,
             metadataJson: metadata,
-            lastSeenAt: issue.lastSeen,
+            lastSeenAt,
             createdAt: existing?.createdAt ?? now,
-            updatedAt: now,
+            updatedAt,
             ownerEmail: existing?.ownerEmail ?? userEmail,
             orgId,
           })
@@ -126,13 +146,11 @@ export default defineAction({
             set: {
               sourceUrl: issue.permalink,
               title: issue.title,
-              summary: [issue.culprit, `${issue.count} events`, issue.level]
-                .filter(Boolean)
-                .join(" · ")
-                .slice(0, 4_000),
+              summary,
+              status,
               metadataJson: metadata,
-              lastSeenAt: issue.lastSeen,
-              updatedAt: now,
+              lastSeenAt,
+              updatedAt,
             },
           });
       }

package/corpus/templates/factory/actions/poll-slack-channel.ts

@@ -11,6 +11,10 @@ import {
 } from "../server/lib/require-workspace-member.js";
 import { recordFactoryAudit } from "../server/triage/audit.js";
 import { itemDedupeKey } from "../server/triage/ids.js";
+import {
+  hasTriageSourceChanged,
+  statusAfterTriageSourceUpdate,
+} from "../server/triage/review-state.js";
 import { pollSlackChannel } from "../server/triage/slack-poller.js";
 
 export default defineAction({
@@ -59,6 +63,36 @@ export default defineAction({
     await db.transaction(async (tx) => {
       for (const envelope of result.envelopes) {
         const id = itemDedupeKey(envelope, orgId);
+        const existing = (
+          await tx
+            .select()
+            .from(triageItems)
+            .where(and(eq(triageItems.id, id), eq(triageItems.orgId, orgId)))
+            .limit(1)
+        )[0];
+        const sourceChanged = hasTriageSourceChanged(existing, {
+          title: envelope.title,
+          summary: envelope.summary ?? null,
+          sourceUrl: envelope.sourceUrl ?? null,
+          coverage: envelope.coverage,
+          lastSeenAt:
+            typeof envelope.metadata?.messageTs === "string"
+              ? envelope.metadata.messageTs
+              : undefined,
+        });
+        const status = statusAfterTriageSourceUpdate(
+          existing?.status,
+          sourceChanged,
+          "received",
+        );
+        const updatedAt = sourceChanged ? now : (existing?.updatedAt ?? now);
+        const sourceLastSeenAt =
+          typeof envelope.metadata?.messageTs === "string"
+            ? envelope.metadata.messageTs
+            : now;
+        const lastSeenAt = sourceChanged
+          ? sourceLastSeenAt
+          : (existing?.lastSeenAt ?? now);
         await tx
           .insert(triageItems)
           .values({
@@ -68,7 +102,7 @@ export default defineAction({
             sourceUrl: envelope.sourceUrl ?? null,
             title: envelope.title,
             summary: envelope.summary ?? null,
-            status: "received",
+            status,
             risk: "unknown",
             channelId: envelope.channelId ?? null,
             threadTs: envelope.threadTs ?? null,
@@ -78,9 +112,9 @@ export default defineAction({
             coverage: envelope.coverage,
             dedupeKey: id,
             metadataJson: JSON.stringify(envelope.metadata ?? {}),
-            lastSeenAt: now,
+            lastSeenAt,
             createdAt: now,
-            updatedAt: now,
+            updatedAt,
             ownerEmail: userEmail,
             orgId,
           })
@@ -93,8 +127,10 @@ export default defineAction({
               channelId: envelope.channelId ?? null,
               threadTs: envelope.threadTs ?? null,
               coverage: envelope.coverage,
-              lastSeenAt: now,
-              updatedAt: now,
+              metadataJson: JSON.stringify(envelope.metadata ?? {}),
+              status,
+              lastSeenAt,
+              updatedAt,
             },
           });
       }

package/corpus/templates/factory/actions/provider-api-catalog.ts

@@ -0,0 +1,13 @@
+import { createProviderApiCatalogAction } from "@agent-native/core/provider-api/actions/provider-api";
+
+import { listProviderApiCatalog } from "../server/lib/provider-api.js";
+
+export default createProviderApiCatalogAction(
+  { listCatalog: listProviderApiCatalog },
+  {
+    description:
+      "List the provider APIs available through shared workspace integrations. Use this to discover connected capabilities and connection metadata without exposing secret values.",
+    guidance:
+      "Factory does not own provider keys. Use the workspace integrations configured in Dispatch or the shared app settings. Provider-specific Factory actions are compatibility adapters; use provider-api-docs and provider-api-request for other connected providers or endpoints.",
+  },
+);