@agent-native/core 0.146.7 → 0.147.0

package/corpus/README.md

@@ -31,4 +31,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- template files: 7921
+- template files: 7926

package/corpus/templates/analytics/.agents/skills/turn-into-app/SKILL.md

@@ -3,8 +3,9 @@ name: turn-into-app
 description: >-
   Turn visible project context, a proven thread, skill, or workflow into a
   runnable Agent-Native app with simple buttons, visible agent steps, preview,
-  and deployment handoff. Use when a user invokes `/turn-into-app` or asks to
-  make a workflow into an app, including from Claude or ChatGPT on the web.
+  and deployment handoff. Use when a user invokes `/turn-into-app`,
+  `/make-into-app`, or asks to make a workflow into an app, including from
+  Claude or ChatGPT on the web.
 user-invocable: true
 scope: both
 metadata:
@@ -38,6 +39,15 @@ The build location depends on the host. Treat this as a hard routing rule:
   workspace, follow the local implementation steps below. The local agent may
   scaffold, edit, run, and verify the app there.
 
+Once the source brief is sufficient to identify a repeatable workflow, the
+handoff is non-interactive. Do not ask the user for visual, product, copy,
+layout, template, integration, or implementation choices that can be resolved
+from the source. Select the source's recommended option; otherwise choose the
+most direct conventional default and record the assumption for later review.
+Only stop for a genuine hard blocker such as missing authorization, a
+destructive external action, an ambiguous target workspace, or no identifiable
+workflow at all.
+
 ## Default behavior
 
 For a local code-agent runtime this is an end-to-end build skill, not a request
@@ -104,14 +114,16 @@ before creating the app. Read the host-provided context in this order:
 Record the brief with these headings before handoff: source and provenance,
 project goal, configuration and constraints, knowledge sources, repeatable
 workflow, inputs and outputs, judgment and review points, representative runs,
-integrations and permissions, and unknowns. This is the compact contract for
+integrations and permissions, and unknowns and assumptions. This is the compact contract for
 the app. It keeps the new app useful without pretending that hidden Project
 history was imported. See [the fresh Project reference](references/fresh-project.md)
 for the host setup and brief template.
 
-If the visible Project context has no concrete repeatable job, ask for one
-focused clarification or a representative artifact. Do not fall back to a
-generic “what app do you want to make?” builder.
+If the visible Project context has no concrete repeatable job and no primary
+goal can be inferred, ask for one focused clarification or a representative
+artifact. Otherwise use the project's primary goal and source conventions; do
+not ask a questionnaire and do not fall back to a generic “what app do you
+want to make?” builder.
 
 ## Source selection guard
 

package/corpus/templates/analytics/.agents/skills/turn-into-app/references/fresh-project.md

@@ -36,7 +36,7 @@ Inputs and outputs:
 Judgment and review points:
 Representative runs: none, or 1-3 selected examples
 Integrations and permissions:
-Unknowns and follow-up:
+Unknowns and assumptions:
 ```
 
 Keep source references bounded. Prefer a file name, URL, resource ID, or short
@@ -69,6 +69,13 @@ do not fall back to a local sandbox build. Claude Code and Codex Code are the
 local-agent exception and may follow the implementation steps in the main
 skill.
 
+The brief is an implementation authorization, not a questionnaire. After a
+repeatable workflow is identifiable, choose any source-recommended option
+automatically. For unresolved non-blocking choices, use the most direct
+conventional default, record it under assumptions, and continue. Ask only when
+there is no identifiable workflow, no authorized target workspace, or a
+destructive/credential boundary genuinely prevents the handoff.
+
 In a new Project chat, say:
 
 ```text

package/corpus/templates/analytics/DEVELOPING.md

@@ -183,6 +183,65 @@ Conventions:
 - Use `fatal()` for required arg validation
 - `helpers.ts` loads `dotenv/config` so env vars are available
 
+### Dedicated first-party Analytics backfill
+
+`backfill:first-party-bigquery` is a resumable, bounded Neon-to-BigQuery worker
+for an explicitly selected organization. It is dry-run by default. It uses the
+scoped credential resolver, fixed high-water marks, separate organization and
+legacy-owner cursors, atomic local checkpoints, a local lock, and a durable
+database lease shared with the shipped worker. The tuple-paging indexes are
+installed by the additive analytics migration. It does not change the Analytics
+sink or perform cutover.
+
+```bash
+pnpm backfill:first-party-bigquery \
+  --owner-email=<owner-email> \
+  --org-id=<org-id>
+```
+
+Production execution requires both `--execute` and the explicit
+`AGENT_NATIVE_ANALYTICS_BIGQUERY_BACKFILL_ALLOW=1` environment gate. Start with a bounded
+`--max-batches` budget and increase concurrency only after checking database
+health between runs. The dedicated worker claims the durable migration-job
+lease, so the shipped worker and another operator using a different checkpoint
+path cannot copy the same job concurrently. A crashed dedicated worker leaves
+that lease to expire before the shipped worker can resume it.
+
+```bash
+AGENT_NATIVE_ANALYTICS_BIGQUERY_BACKFILL_ALLOW=1 pnpm backfill:first-party-bigquery \
+  --execute \
+  --owner-email=<owner-email> \
+  --org-id=<org-id> \
+  --batch-size=1000 \
+  --concurrency=2 \
+  --max-batches=100
+```
+
+The checkpoint file contains cursors and counts, not event payloads or
+credentials. A short page triggers a fresh high-water check so rows written
+while the worker is running are included. A partial BigQuery acknowledgement
+does not advance the cursor; retry it promptly, or run an insertId-deduplication
+or `MERGE` pass on the target table before finalizing.
+
+Before finalization, quiesce the source event writes and verify the final
+high-water marks. The `--owner-email` and `--org-id` values are trusted operator
+inputs, so execution is limited to the approved production operator and the
+two explicit environment gates. Then use the separate `--finalize` command
+with both gates below. The command rechecks the source high-water marks before
+marking the durable job complete; the normal migration action's approval gate
+still controls cutover:
+
+```bash
+AGENT_NATIVE_ANALYTICS_BIGQUERY_BACKFILL_FINALIZE_ALLOW=1 \
+AGENT_NATIVE_ANALYTICS_BIGQUERY_BACKFILL_QUIESCENT=1 \
+pnpm backfill:first-party-bigquery \
+  --finalize \
+  --owner-email=<owner-email> \
+  --org-id=<org-id>
+```
+
+Do not delete a lock file until the owning process has been verified stopped.
+
 ## TypeScript Everywhere
 
 All code in this project must be TypeScript (`.ts`). Never create `.js`, `.cjs`, or `.mjs` files. Node 22+ runs `.ts` files natively, so no compilation step is needed for scripts. Use ESM imports (`import`), not CommonJS (`require`).

package/corpus/templates/analytics/app/routes/status.$slug.tsx

@@ -1,4 +1,5 @@
 import { useActionQuery } from "@agent-native/core/client/hooks";
+import { normalizeDocumentTitle } from "@agent-native/core/shared";
 import { IconActivity } from "@tabler/icons-react";
 import { useMemo } from "react";
 import { data, useLoaderData, useParams } from "react-router";
@@ -43,15 +44,16 @@ export const meta: MetaFunction<typeof loader> = ({ loaderData }) => {
       { name: "robots", content: "noindex" },
     ];
   }
+  const pageTitle = normalizeDocumentTitle(page.title, "Status page");
   const description =
     page.description ||
     (page.overall === "operational"
       ? "All systems operational."
       : "Current service status.");
   return [
-    { title: `${page.title} · Status` },
+    { title: `${pageTitle} · Status` },
     { name: "description", content: description },
-    { property: "og:title", content: `${page.title} · Status` },
+    { property: "og:title", content: `${pageTitle} · Status` },
     { property: "og:description", content: description },
     { property: "og:type", content: "website" },
   ];

package/corpus/templates/analytics/package.json

@@ -11,6 +11,7 @@
     "format.fix": "oxfmt --write .",
     "typecheck": "agent-native typecheck",
     "migrate:production": "tsx scripts/migrate-production.ts",
+    "backfill:first-party-bigquery": "tsx scripts/first-party-analytics-bigquery-backfill.ts",
     "action": "agent-native action",
     "script": "agent-native script"
   },