@agent-native/core 0.107.1 → 0.108.0

package/corpus/templates/clips/shared/feature-flags.ts

@@ -1,41 +1,34 @@
+import {
+  defineFeatureFlag,
+  defineFeatureFlags,
+} from "@agent-native/core/feature-flags";
+
 /**
- * Server-controlled feature flags, readable from the action surface so
- * behavior can change without a redeploy. Stored under one global `settings`
- * key (not per-user/org) — these gate app-wide rollout decisions, not
- * individual preferences.
- *
- * Add new flags here as they're needed; `get-feature-flags` stays generic
- * and doesn't need to change.
+ * Desktop app: use the custom ScreenCaptureKit (SCK) capture pipeline
+ * (fragmented MP4 writer + live audio mixer) instead of Apple's stock
+ * `SCRecordingOutput`. See `desktop/src-tauri/src/native_screen/custom_capture.rs`.
  */
+export const USE_CUSTOM_SCK_PIPELINE_FLAG = defineFeatureFlag({
+  key: "useCustomSCKPipeline",
+  displayName: "Custom ScreenCaptureKit pipeline",
+  description:
+    "Use the fragmented MP4 writer and live audio mixer for desktop capture.",
+});
 
-export const FEATURE_FLAGS_KEY = "feature-flags";
-
-export type FeatureFlags = {
-  /**
-   * Desktop app: use the custom ScreenCaptureKit (SCK) capture pipeline
-   * (fragmented MP4 writer + live audio mixer) instead of Apple's stock
-   * `SCRecordingOutput`. See `desktop/src-tauri/src/native_screen/custom_capture.rs`.
-   */
-  useCustomSCKPipeline?: boolean;
-  /**
-   * Desktop app: stream the recording to the server in chunks while it is
-   * being recorded, instead of uploading the whole file after Stop. Only
-   * effective when `useCustomSCKPipeline` is also on. See
-   * `desktop/src-tauri/src/native_screen/live_upload.rs`.
-   */
-  customSCKPipelineLiveUploadEnabled?: boolean;
-};
-
-export const FEATURE_FLAG_DEFAULTS: Required<FeatureFlags> = {
-  useCustomSCKPipeline: false,
-  customSCKPipelineLiveUploadEnabled: false,
-};
+/**
+ * Desktop app: stream the recording to the server in chunks while it is
+ * being recorded, instead of uploading the whole file after Stop. Only
+ * effective when the custom SCK pipeline is also on. See
+ * `desktop/src-tauri/src/native_screen/live_upload.rs`.
+ */
+export const CUSTOM_SCK_LIVE_UPLOAD_FLAG = defineFeatureFlag({
+  key: "customSCKPipelineLiveUploadEnabled",
+  displayName: "Live capture upload",
+  description:
+    "Upload recording chunks while capture is still in progress. Requires the custom ScreenCaptureKit pipeline.",
+});
 
-export function withFeatureFlagDefaults(
-  flags: FeatureFlags | Record<string, unknown> | null | undefined,
-): Required<FeatureFlags> {
-  return {
-    ...FEATURE_FLAG_DEFAULTS,
-    ...(flags as FeatureFlags | undefined),
-  };
-}
+export const CLIPS_FEATURE_FLAGS = defineFeatureFlags([
+  USE_CUSTOM_SCK_PIPELINE_FLAG,
+  CUSTOM_SCK_LIVE_UPLOAD_FLAG,
+]);

package/corpus/templates/content/.agents/skills/feature-flags/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: feature-flags
+description: >-
+  Declare, evaluate, manage, and remove framework feature flags. Use when
+  shipping a capability gradually, targeting users or organizations, or
+  replacing a compile-time rollout switch with a production-safe runtime flag.
+scope: dev
+metadata:
+  internal: true
+---
+
+# Feature Flags
+
+A feature flag is a boolean declared in app code, evaluated locally by Core,
+and managed from the Analytics fleet control plane. Code owns whether a flag
+exists. Runtime settings own only its rollout state.
+
+Flags let an app deploy dormant code and turn it on in the real environment
+without another deployment. They are not experiments: do not add variants,
+hypotheses, conversion metrics, exposure tracking, or lifecycle states.
+
+## When to use one
+
+Use a flag for a reversible rollout of a user-facing capability whose dormant
+code is safe to deploy. Flags are useful for production dogfooding, exact-user
+or organization pilots, and deterministic percentage rollouts.
+
+Do not use a flag for authentication, authorization, secrets, audit enablement,
+SSR cache behavior, or another security boundary. Client hiding is presentation
+only; every guarded server action must evaluate the same registered flag.
+
+## Agent workflow
+
+### 1. Declare
+
+Keep definitions in a shared TypeScript module so server and client code use the
+same stable key. Flags are boolean and default-off.
+
+```ts
+import { defineFeatureFlag } from "@agent-native/core/feature-flags";
+
+export const FULL_APP_BUILDING = defineFeatureFlag({
+  key: "full-app-building",
+  displayName: "Full app building",
+  description: "Create and edit Fusion-backed applications.",
+});
+```
+
+Keys are immutable, never reused, and contain only letters, numbers, dots,
+underscores, or hyphens. Prefer a concise app-owned name. Do not create flag
+definitions or rollout rows from Analytics.
+
+### 2. Register
+
+Register app definitions from a Nitro plugin before actions are discovered.
+Do not add app-specific flags to a Core registry.
+
+```ts
+import { createFeatureFlagsPlugin } from "@agent-native/core/server";
+
+import { FULL_APP_BUILDING } from "../../shared/feature-flags.js";
+
+export default createFeatureFlagsPlugin({ flags: [FULL_APP_BUILDING] });
+```
+
+### 3. Guard server and client
+
+The server action is the enforcement boundary:
+
+```ts
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
+
+run: async (args, ctx) => {
+  if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
+    throw new Error("Full app building is not enabled for this account.");
+  }
+  // guarded operation
+}
+```
+
+Use the client hook only to hide or reveal hydrated UI:
+
+```tsx
+import { useFeatureFlag } from "@agent-native/core/client";
+
+const enabled = useFeatureFlag(FULL_APP_BUILDING.key);
+return enabled ? <FullAppOption /> : null;
+```
+
+The client hook intentionally returns false while loading or for an unknown
+flag. Never replace that fail-closed behavior with app-local bucketing or a
+compile-time fallback. Never evaluate personalized flags in the public SSR
+shell; it is shared and cached for every visitor.
+
+### 4. Verify and roll out
+
+1. Verify the off path before changing rollout state.
+2. Confirm the registered flag appears in **Analytics → Feature flags** for the
+   app and is Off by default.
+3. Use **Enable for me** for initial production dogfood.
+4. Expand to exact emails, organization IDs, or a percentage only from
+   Analytics.
+5. Confirm the client presentation and authoritative server action agree.
+
+## Management contract
+
+Core mounts three actions in registered apps:
+
+| Action | Purpose |
+| --- | --- |
+| `get-feature-flags` | Return the current caller's evaluated boolean values. |
+| `list-feature-flags` | Return definitions and rollout metadata to an authorized operator. |
+| `set-feature-flag` | Atomically turn a flag off, enable it for the operator, or replace targeting rules. |
+
+Analytics calls the app-local operator actions through narrowly scoped A2A
+delegation. Tokens require an exact audience, organization, scope, operator
+role, and audit correlation id. Management is permission-checked and audited
+by the target app. Never manage flags through generic settings routes, raw SQL,
+or per-app toggle UIs.
+
+## Rollout semantics
+
+The operator modes are **Off**, **Targeted**, and **Everyone**. Core stores them
+as `off`, `rules`, and `on`.
+
+Targeted rules combine exact normalized emails, exact organization IDs, and a
+percentage with OR semantics. Exact matches are checked first. Percentage
+buckets use Core's stable hash of the flag key and authenticated user identity;
+anonymous callers fail closed. Raising a percentage preserves the users already
+included at a lower percentage. Do not implement bucketing in app code.
+
+Unknown definitions, missing state, malformed state, storage errors, and
+evaluation errors all return the code default (`false` in v1). Explicit Off
+wins over every target; Everyone enables every authenticated caller.
+
+## Remove a flag
+
+After a rollout is permanent:
+
+1. Replace guarded branches with the chosen behavior.
+2. Delete the server and client gates.
+3. Delete the definition and registration entry.
+4. Verify the flag disappears from the Analytics fleet.
+5. Remove stale tests and rollout instructions.
+
+A permanent flag is just an if statement with a pension plan.
+
+## Verification checklist
+
+- Unknown and unregistered keys evaluate false.
+- UI hiding and server enforcement use the same registered key.
+- Exact-user, organization, deterministic percentage, Everyone, and Off paths
+  have focused tests.
+- Increasing a percentage is monotonic; anonymous percentage evaluation is off.
+- Unauthorized callers cannot list targeting details or mutate flags.
+- Mutations are atomic, read back stored state, emit refresh, and appear in the
+  audit log with the flag key.
+- Analytics represents ready, no-definition, unsupported, forbidden, legacy,
+  and unreachable directory apps honestly.
+- Future agents can find this skill from root `AGENTS.md`, and
+  `pnpm guard:workspace-skills` passes after syncing generated copies.
+
+## Related skills
+
+- **adding-a-feature** — preserve UI/action/instruction/application-state parity
+- **actions** — define and call guarded app operations
+- **audit-log** — inspect automatic action mutation history
+- **reliable-mutations** — make rollout changes atomic and provable
+- **security** — keep security controls out of feature flags

package/corpus/templates/design/.agents/skills/feature-flags/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: feature-flags
+description: >-
+  Declare, evaluate, manage, and remove framework feature flags. Use when
+  shipping a capability gradually, targeting users or organizations, or
+  replacing a compile-time rollout switch with a production-safe runtime flag.
+scope: dev
+metadata:
+  internal: true
+---
+
+# Feature Flags
+
+A feature flag is a boolean declared in app code, evaluated locally by Core,
+and managed from the Analytics fleet control plane. Code owns whether a flag
+exists. Runtime settings own only its rollout state.
+
+Flags let an app deploy dormant code and turn it on in the real environment
+without another deployment. They are not experiments: do not add variants,
+hypotheses, conversion metrics, exposure tracking, or lifecycle states.
+
+## When to use one
+
+Use a flag for a reversible rollout of a user-facing capability whose dormant
+code is safe to deploy. Flags are useful for production dogfooding, exact-user
+or organization pilots, and deterministic percentage rollouts.
+
+Do not use a flag for authentication, authorization, secrets, audit enablement,
+SSR cache behavior, or another security boundary. Client hiding is presentation
+only; every guarded server action must evaluate the same registered flag.
+
+## Agent workflow
+
+### 1. Declare
+
+Keep definitions in a shared TypeScript module so server and client code use the
+same stable key. Flags are boolean and default-off.
+
+```ts
+import { defineFeatureFlag } from "@agent-native/core/feature-flags";
+
+export const FULL_APP_BUILDING = defineFeatureFlag({
+  key: "full-app-building",
+  displayName: "Full app building",
+  description: "Create and edit Fusion-backed applications.",
+});
+```
+
+Keys are immutable, never reused, and contain only letters, numbers, dots,
+underscores, or hyphens. Prefer a concise app-owned name. Do not create flag
+definitions or rollout rows from Analytics.
+
+### 2. Register
+
+Register app definitions from a Nitro plugin before actions are discovered.
+Do not add app-specific flags to a Core registry.
+
+```ts
+import { createFeatureFlagsPlugin } from "@agent-native/core/server";
+
+import { FULL_APP_BUILDING } from "../../shared/feature-flags.js";
+
+export default createFeatureFlagsPlugin({ flags: [FULL_APP_BUILDING] });
+```
+
+### 3. Guard server and client
+
+The server action is the enforcement boundary:
+
+```ts
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
+
+run: async (args, ctx) => {
+  if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
+    throw new Error("Full app building is not enabled for this account.");
+  }
+  // guarded operation
+}
+```
+
+Use the client hook only to hide or reveal hydrated UI:
+
+```tsx
+import { useFeatureFlag } from "@agent-native/core/client";
+
+const enabled = useFeatureFlag(FULL_APP_BUILDING.key);
+return enabled ? <FullAppOption /> : null;
+```
+
+The client hook intentionally returns false while loading or for an unknown
+flag. Never replace that fail-closed behavior with app-local bucketing or a
+compile-time fallback. Never evaluate personalized flags in the public SSR
+shell; it is shared and cached for every visitor.
+
+### 4. Verify and roll out
+
+1. Verify the off path before changing rollout state.
+2. Confirm the registered flag appears in **Analytics → Feature flags** for the
+   app and is Off by default.
+3. Use **Enable for me** for initial production dogfood.
+4. Expand to exact emails, organization IDs, or a percentage only from
+   Analytics.
+5. Confirm the client presentation and authoritative server action agree.
+
+## Management contract
+
+Core mounts three actions in registered apps:
+
+| Action | Purpose |
+| --- | --- |
+| `get-feature-flags` | Return the current caller's evaluated boolean values. |
+| `list-feature-flags` | Return definitions and rollout metadata to an authorized operator. |
+| `set-feature-flag` | Atomically turn a flag off, enable it for the operator, or replace targeting rules. |
+
+Analytics calls the app-local operator actions through narrowly scoped A2A
+delegation. Tokens require an exact audience, organization, scope, operator
+role, and audit correlation id. Management is permission-checked and audited
+by the target app. Never manage flags through generic settings routes, raw SQL,
+or per-app toggle UIs.
+
+## Rollout semantics
+
+The operator modes are **Off**, **Targeted**, and **Everyone**. Core stores them
+as `off`, `rules`, and `on`.
+
+Targeted rules combine exact normalized emails, exact organization IDs, and a
+percentage with OR semantics. Exact matches are checked first. Percentage
+buckets use Core's stable hash of the flag key and authenticated user identity;
+anonymous callers fail closed. Raising a percentage preserves the users already
+included at a lower percentage. Do not implement bucketing in app code.
+
+Unknown definitions, missing state, malformed state, storage errors, and
+evaluation errors all return the code default (`false` in v1). Explicit Off
+wins over every target; Everyone enables every authenticated caller.
+
+## Remove a flag
+
+After a rollout is permanent:
+
+1. Replace guarded branches with the chosen behavior.
+2. Delete the server and client gates.
+3. Delete the definition and registration entry.
+4. Verify the flag disappears from the Analytics fleet.
+5. Remove stale tests and rollout instructions.
+
+A permanent flag is just an if statement with a pension plan.
+
+## Verification checklist
+
+- Unknown and unregistered keys evaluate false.
+- UI hiding and server enforcement use the same registered key.
+- Exact-user, organization, deterministic percentage, Everyone, and Off paths
+  have focused tests.
+- Increasing a percentage is monotonic; anonymous percentage evaluation is off.
+- Unauthorized callers cannot list targeting details or mutate flags.
+- Mutations are atomic, read back stored state, emit refresh, and appear in the
+  audit log with the flag key.
+- Analytics represents ready, no-definition, unsupported, forbidden, legacy,
+  and unreachable directory apps honestly.
+- Future agents can find this skill from root `AGENTS.md`, and
+  `pnpm guard:workspace-skills` passes after syncing generated copies.
+
+## Related skills
+
+- **adding-a-feature** — preserve UI/action/instruction/application-state parity
+- **actions** — define and call guarded app operations
+- **audit-log** — inspect automatic action mutation history
+- **reliable-mutations** — make rollout changes atomic and provable
+- **security** — keep security controls out of feature flags

package/corpus/templates/design/AGENTS.md

@@ -261,7 +261,8 @@ patterns live in `.agents/skills/`.
   `connect-localhost`; list them with `list-localhost-connections` before
   creating or resolving local-code artboards. Fusion designs are full-app
   designs backed by a running Builder Fusion container, created via
-  `create-fusion-app` when `FULL_APP_BUILDING_ENABLED` is on; preserve the
+  `create-fusion-app` when the `full-app-building` feature flag is enabled;
+  preserve the
   design's `fusionApp` linkage data whenever present and never invent it.
 - Localhost route manifests are scaffolding for URL-backed Flow Canvas
   artboards. Use `add-localhost-screens` to place routes or path/query states as
@@ -431,8 +432,9 @@ patterns live in `.agents/skills/`.
 
 ## Full App Building
 
-Flag-gated (`FULL_APP_BUILDING_ENABLED` in `shared/full-app.ts`, default off)
-and requires Builder connected. See `full-app-build` skill for the full flow.
+Flag-gated by `FULL_APP_BUILDING` in `shared/full-app.ts` (key
+`full-app-building`, default off) and requires Builder connected. See
+`full-app-build` skill for the full flow.
 
 - `create-fusion-app`: creates the app branch via the Builder cloud agent; one
   branch per design; returns existing linkage if already created.

package/corpus/templates/design/actions/add-fusion-screens.ts

@@ -8,6 +8,7 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import { assertAccess } from "@agent-native/core/sharing";
 import { z } from "zod";
 
@@ -18,10 +19,7 @@ import {
   DEFAULT_FUSION_SCREEN_WIDTH,
   upsertFusionScreens,
 } from "../server/lib/fusion-screens.js";
-import {
-  FULL_APP_BUILDING_ENABLED,
-  readFusionApp,
-} from "../shared/full-app.js";
+import { FULL_APP_BUILDING, readFusionApp } from "../shared/full-app.js";
 
 export default defineAction({
   description:
@@ -49,8 +47,8 @@ export default defineAction({
       .optional()
       .describe("Iframe viewport height. Defaults to 900."),
   }),
-  run: async ({ designId, paths, width, height }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, paths, width, height }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/apply-fusion-edits.ts

@@ -10,6 +10,7 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import { sendFusionBranchMessage } from "@agent-native/core/server";
 import { getRequestUserEmail } from "@agent-native/core/server/request-context";
 import { assertAccess } from "@agent-native/core/sharing";
@@ -19,10 +20,7 @@ import { z } from "zod";
 
 import { getDb, schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
-import {
-  FULL_APP_BUILDING_ENABLED,
-  readFusionApp,
-} from "../shared/full-app.js";
+import { FULL_APP_BUILDING, readFusionApp } from "../shared/full-app.js";
 
 function parseTarget(raw: string | null): Record<string, unknown> | null {
   if (!raw) return null;
@@ -72,8 +70,8 @@ export default defineAction({
           "Omit to apply all pending edits for this design.",
       ),
   }),
-  run: async ({ designId, editIds }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, editIds }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/create-fusion-app.ts

@@ -7,13 +7,14 @@
  * necessarily ready immediately — call `sync-fusion-app` to poll the
  * container and pick up the preview URL once it boots.
  *
- * Gated behind `FULL_APP_BUILDING_ENABLED`. When Builder is not configured
+ * Gated behind the full-app-building runtime feature flag. When Builder is not configured
  * (no credentials or no branch project ID), returns the same graceful
  * `{ status: "not-configured", cta, message }` shape as
  * `migrate-inline-design-to-app` instead of throwing.
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import {
   runBuilderAgent,
   resolveBuilderBranchProjectId,
@@ -27,7 +28,7 @@ import "../server/db/index.js"; // ensure registerShareableResource runs
 import { mutateDesignData } from "../server/lib/design-data-mutation.js";
 import { resolveBuilderStatus } from "../shared/builder-app.js";
 import {
-  FULL_APP_BUILDING_ENABLED,
+  FULL_APP_BUILDING,
   readFusionApp,
   writeFusionApp,
 } from "../shared/full-app.js";
@@ -73,8 +74,8 @@ export default defineAction({
         "Optional branch name for the Builder agent to use. If omitted, Builder generates one.",
       ),
   }),
-  run: async ({ designId, prompt, branchName }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, prompt, branchName }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/deploy-fusion-app.ts

@@ -11,6 +11,7 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import {
   deployFusionProject,
   getFusionHostingUrl,
@@ -23,7 +24,7 @@ import { schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
 import { mutateDesignData } from "../server/lib/design-data-mutation.js";
 import {
-  FULL_APP_BUILDING_ENABLED,
+  FULL_APP_BUILDING,
   readFusionApp,
   writeFusionApp,
 } from "../shared/full-app.js";
@@ -58,8 +59,8 @@ export default defineAction({
           "use the design's already-reserved slug, or derive one from the title.",
       ),
   }),
-  run: async ({ designId, slug }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, slug }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/get-fusion-deploy-status.ts

@@ -6,6 +6,7 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import { getFusionDeploys } from "@agent-native/core/server";
 import { accessFilter } from "@agent-native/core/sharing";
 import { and, eq } from "drizzle-orm";
@@ -13,10 +14,7 @@ import { z } from "zod";
 
 import { getDb, schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
-import {
-  FULL_APP_BUILDING_ENABLED,
-  readFusionApp,
-} from "../shared/full-app.js";
+import { FULL_APP_BUILDING, readFusionApp } from "../shared/full-app.js";
 
 function asString(value: unknown): string | undefined {
   return typeof value === "string" && value.trim() ? value.trim() : undefined;
@@ -33,8 +31,8 @@ export default defineAction({
   }),
   readOnly: true,
   http: { method: "GET" },
-  run: async ({ designId }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/list-fusion-edits.ts

@@ -8,13 +8,14 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import { accessFilter } from "@agent-native/core/sharing";
 import { and, asc, eq } from "drizzle-orm";
 import { z } from "zod";
 
 import { getDb, schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
-import { FULL_APP_BUILDING_ENABLED } from "../shared/full-app.js";
+import { FULL_APP_BUILDING } from "../shared/full-app.js";
 
 function parseTarget(raw: string | null): Record<string, unknown> | null {
   if (!raw) return null;
@@ -43,8 +44,8 @@ export default defineAction({
   }),
   readOnly: true,
   http: { method: "GET" },
-  run: async ({ designId, status }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, status }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/push-fusion-app.ts

@@ -7,16 +7,14 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import { pushFusionBranch } from "@agent-native/core/server";
 import { assertAccess } from "@agent-native/core/sharing";
 import { z } from "zod";
 
 import { schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
-import {
-  FULL_APP_BUILDING_ENABLED,
-  readFusionApp,
-} from "../shared/full-app.js";
+import { FULL_APP_BUILDING, readFusionApp } from "../shared/full-app.js";
 
 function asString(value: unknown): string | undefined {
   return typeof value === "string" && value.trim() ? value.trim() : undefined;
@@ -31,8 +29,8 @@ export default defineAction({
   schema: z.object({
     designId: z.string().describe("Design project ID backed by a fusion app."),
   }),
-  run: async ({ designId }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }
 

package/corpus/templates/design/actions/queue-fusion-edit.ts

@@ -10,6 +10,7 @@
  */
 
 import { defineAction } from "@agent-native/core";
+import { isFeatureFlagEnabled } from "@agent-native/core/feature-flags";
 import {
   getRequestOrgId,
   getRequestUserEmail,
@@ -21,7 +22,7 @@ import { z } from "zod";
 
 import { getDb, schema } from "../server/db/index.js";
 import "../server/db/index.js"; // ensure registerShareableResource runs
-import { FULL_APP_BUILDING_ENABLED } from "../shared/full-app.js";
+import { FULL_APP_BUILDING } from "../shared/full-app.js";
 
 const targetSchema = z.object({
   selector: z
@@ -63,8 +64,8 @@ export default defineAction({
       .optional()
       .describe("Optional target context for the element/screen being edited."),
   }),
-  run: async ({ designId, instruction, screenFileId, target }) => {
-    if (!FULL_APP_BUILDING_ENABLED) {
+  run: async ({ designId, instruction, screenFileId, target }, ctx) => {
+    if (!(await isFeatureFlagEnabled(FULL_APP_BUILDING, ctx))) {
       throw new Error("Full app building is not enabled");
     }