@agent-native/core 0.146.8 → 0.147.0

package/corpus/templates/factory/app/routes/factory.tsx

@@ -589,11 +589,6 @@ function AutomationsView({
     "list-factory-automations",
     { factoryId },
   );
-  const healthQuery = useActionQuery<FactoryAutomationHealth>(
-    "get-factory-automation-health",
-    {},
-    { refetchInterval: 60_000 },
-  );
   const saveMutation = useActionMutation("save-factory-automation");
   const runMutation = useActionMutation("run-factory-automation");
   const {
@@ -684,85 +679,17 @@ function AutomationsView({
       schedule: draft.schedule ?? "",
       enabled: draft.enabled,
     });
-    await Promise.all([automationsQuery.refetch(), healthQuery.refetch()]);
+    await automationsQuery.refetch();
   }
 
   async function runAutomation() {
     if (!draft) return;
     await runMutation.mutateAsync({ factoryId, automationId: draft.id });
-    await Promise.all([automationsQuery.refetch(), healthQuery.refetch()]);
+    await automationsQuery.refetch();
   }
 
-  const health = healthQuery.data;
-  const healthLabel = health
-    ? {
-        healthy: t("factoryRoute.automationHealthHealthy"),
-        stale: t("factoryRoute.automationHealthStale"),
-        error: t("factoryRoute.automationHealthError"),
-        "no-data": t("factoryRoute.automationHealthNoData"),
-      }[health.status]
-    : t("factoryRoute.automationHealthNoData");
-
   return (
     <div className="space-y-4 p-4 lg:p-6">
-      <Card>
-        <CardHeader className="pb-3">
-          <CardTitle className="text-base">
-            {t("factoryRoute.automationHealthTitle")}
-          </CardTitle>
-          <p className="text-sm text-muted-foreground">
-            {t("factoryRoute.automationHealthDescription")}
-          </p>
-        </CardHeader>
-        <CardContent className="space-y-2 pt-0 text-sm">
-          <div className="flex flex-wrap items-center gap-2">
-            <span className="rounded-full border px-2 py-1 font-medium">
-              {healthLabel}
-            </span>
-            {health?.lastCheckedAt && (
-              <span className="text-muted-foreground">
-                {t("factoryRoute.automationLastCheck")}:{" "}
-                {formatAutomationDate(health.lastCheckedAt)}
-              </span>
-            )}
-            {health?.lastDispatchedAt && (
-              <span className="text-muted-foreground">
-                {t("factoryRoute.automationLastDispatch")}:{" "}
-                {formatAutomationDate(health.lastDispatchedAt)}
-              </span>
-            )}
-            {health?.runtime && (
-              <span className="text-muted-foreground">
-                {t("factoryRoute.automationRuntime")}: {health.runtime}
-              </span>
-            )}
-          </div>
-          {!health?.lastCheckedAt && (
-            <p className="text-muted-foreground">
-              {t("factoryRoute.automationHealthNoDataHint")}
-            </p>
-          )}
-          {health?.status === "stale" && (
-            <p className="text-destructive">
-              {t("factoryRoute.automationHealthStaleHint")}
-            </p>
-          )}
-          {health?.lastError && (
-            <p className="text-destructive">
-              {t("factoryRoute.automationHealthErrorDetail")}:{" "}
-              {health.lastError}
-            </p>
-          )}
-          {healthQuery.isError && (
-            <p className="text-destructive">
-              {t("factoryRoute.automationDiagnosticsLoadError")}{" "}
-              {healthQuery.error instanceof Error
-                ? healthQuery.error.message
-                : String(healthQuery.error)}
-            </p>
-          )}
-        </CardContent>
-      </Card>
       <div className="grid gap-4 lg:grid-cols-[minmax(220px,.35fr)_minmax(0,1fr)]">
         <Card>
           <CardHeader>
@@ -1407,6 +1334,11 @@ function SettingsView({ t }: { t: ReturnType<typeof useT> }) {
   const [automationFailureAlertEmail, setAutomationFailureAlertEmail] =
     useState("");
   const query = useActionQuery("get-triage-config", {});
+  const schedulerHealthQuery = useActionQuery<FactoryAutomationHealth>(
+    "get-factory-automation-health",
+    {},
+    { refetchInterval: 60_000 },
+  );
   const mutation = useActionMutation("save-triage-config");
   useEffect(() => {
     const data = query.data as TriageConfig | undefined;
@@ -1427,7 +1359,7 @@ function SettingsView({ t }: { t: ReturnType<typeof useT> }) {
     setAutomationFailureAlertEmail(data.automationFailureAlertEmail ?? "");
   }, [query.data]);
   return (
-    <div className="max-w-4xl p-4 lg:p-6">
+    <div className="max-w-4xl space-y-4 p-4 lg:p-6">
       <Card>
         <CardHeader>
           <CardTitle className="text-base">
@@ -1621,10 +1553,110 @@ function SettingsView({ t }: { t: ReturnType<typeof useT> }) {
           </div>
         </CardContent>
       </Card>
+      <SchedulerHealthStatus
+        health={schedulerHealthQuery.data}
+        isError={schedulerHealthQuery.isError}
+        error={schedulerHealthQuery.error}
+        t={t}
+      />
     </div>
   );
 }
 
+function SchedulerHealthStatus({
+  health,
+  isError,
+  error,
+  t,
+}: {
+  health?: FactoryAutomationHealth;
+  isError: boolean;
+  error: unknown;
+  t: ReturnType<typeof useT>;
+}) {
+  const healthLabel = isError
+    ? t("factoryRoute.automationHealthError")
+    : health
+      ? {
+          healthy: t("factoryRoute.automationHealthHealthy"),
+          stale: t("factoryRoute.automationHealthStale"),
+          error: t("factoryRoute.automationHealthError"),
+          "no-data": t("factoryRoute.automationHealthNoData"),
+        }[health.status]
+      : t("factoryRoute.automationHealthNoData");
+  const hasNoHeartbeat =
+    !isError &&
+    (!health || health.status === "no-data") &&
+    !health?.lastCheckedAt;
+  const hasDiagnostics =
+    isError ||
+    hasNoHeartbeat ||
+    health?.status === "stale" ||
+    health?.status === "error" ||
+    Boolean(health?.lastError);
+
+  return (
+    <section
+      aria-labelledby="factory-scheduler-health"
+      className="border-t px-1 pt-4"
+    >
+      <div className="flex flex-wrap items-center justify-between gap-x-4 gap-y-2">
+        <div className="flex flex-wrap items-center gap-2">
+          <h2
+            id="factory-scheduler-health"
+            className="text-sm font-medium text-muted-foreground"
+          >
+            {t("factoryRoute.automationHealthTitle")}
+          </h2>
+          <span className="rounded-full border px-2 py-0.5 text-xs font-medium">
+            {healthLabel}
+          </span>
+        </div>
+        <div className="flex flex-wrap gap-x-4 gap-y-1 text-xs text-muted-foreground">
+          {health?.lastCheckedAt && (
+            <span>
+              {t("factoryRoute.automationLastCheck")}:{" "}
+              {formatAutomationDate(health.lastCheckedAt)}
+            </span>
+          )}
+          {health?.lastDispatchedAt && (
+            <span>
+              {t("factoryRoute.automationLastDispatch")}:{" "}
+              {formatAutomationDate(health.lastDispatchedAt)}
+            </span>
+          )}
+        </div>
+      </div>
+      {hasDiagnostics && (
+        <div className="mt-2 grid gap-1 text-xs">
+          {hasNoHeartbeat && (
+            <p className="text-muted-foreground">
+              {t("factoryRoute.automationHealthNoDataHint")}
+            </p>
+          )}
+          {health?.status === "stale" && (
+            <p className="text-destructive">
+              {t("factoryRoute.automationHealthStaleHint")}
+            </p>
+          )}
+          {health?.lastError && (
+            <p className="text-destructive">
+              {t("factoryRoute.automationHealthErrorDetail")}:{" "}
+              {health.lastError}
+            </p>
+          )}
+          {isError && (
+            <p className="text-destructive">
+              {t("factoryRoute.automationDiagnosticsLoadError")}{" "}
+              {error instanceof Error ? error.message : String(error)}
+            </p>
+          )}
+        </div>
+      )}
+    </section>
+  );
+}
+
 function ErrorState({
   message,
   onRetry,

package/corpus/templates/factory/changelog/2026-08-08-scheduler-health-moves-to-settings.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-08-08
+---
+
+Scheduler health now stays in Settings until diagnostics are needed.

package/corpus/templates/forms/.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/forms/.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/macros/.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/macros/.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/mail/.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/mail/.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/plan/.agents/skills/adding-a-feature/SKILL.md

@@ -81,6 +81,13 @@ or other file-like payloads, design the upload path in the same change:
 provider upload first, then URL/id/blob handle in SQL. Do not add base64/binary
 columns or stuff files into `application_state`.
 
+If the feature adds a server-side dependency carrying a native binary or heavy
+runtime — headless browser, ffmpeg, image/video processing, ML runtime — read
+the `performance` skill §9 before adding it. A deployed app has one `/*` page
+function that every visitor's cache miss wakes, and it ships whatever the server
+bundle depends on. Run that work from a background function or a job so the page
+function never carries the weight.
+
 **If the action produces or lists a navigable resource**, add a `link` builder that returns `{ url: buildDeepLink({ app, view, params }), label }`. External coding agents and MCP hosts (Claude / ChatGPT / Claude Code / Cowork / Codex, over MCP/A2A) then surface an "Open in … →" deep link that drops the user back into the running UI focused on the record — for free. If a compatible MCP host should render an inline review/edit surface, also add `mcpApp` with `embedApp()` so the action embeds the real React app route instead of a one-off HTML UI. The `link` builder and `mcpApp` metadata must be pure and synchronous (no I/O). Any external-agent read/ingest action must be `http: { method: "GET" }` + `readOnly: true` + `publicAgent: { expose: true, readOnly: true, requiresAuth: true }`. See the `external-agents` skill.
 
 ### 3. Skills / Instructions
@@ -195,4 +202,6 @@ TL;DR: declare the vocabulary once with `defineAppRoles({ appId, roles, defaultR
 - **create-skill** — How to create skills for new patterns (area 3 in detail)
 - **storing-data** — Where to store the feature's data
 - **real-time-sync** — How the UI stays in sync when the agent writes data
+- **performance** — Query/load cost, and (§9) cold-start artifact size when a
+  feature adds a server-side dependency
 - **internationalization** — How to update localized UI copy and catalogs

package/corpus/templates/plan/.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/plan/.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/plan/app/lib/plan-document-title.ts

@@ -1,6 +1,8 @@
+import { normalizeDocumentTitle } from "@agent-native/core/shared";
+
 export function planDocumentTitle(
   planTitle: string | null | undefined,
   fallbackTitle: string,
 ): string {
-  return planTitle?.trim() || fallbackTitle;
+  return normalizeDocumentTitle(planTitle, fallbackTitle);
 }

package/corpus/templates/plan/app/root.tsx

@@ -241,6 +241,7 @@ export default function Root() {
       <AppProviders
         queryClient={queryClient}
         sessionBypass={sessionBypass}
+        documentTitleFallback={APP_TITLE}
         toaster={<Toaster richColors position="bottom-left" />}
         i18n={{ catalog: i18nCatalog }}
       >

package/corpus/templates/slides/.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/slides/.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