@integrity-labs/agt-cli 0.28.1129 → 0.28.1131

package/dist/mcp/index.js

@@ -26816,6 +26816,78 @@ var INTEGRATION_REGISTRY = [
     },
     docs_url: "https://www.framer.com/developers/server-api-quick-start"
   },
+  {
+    // ENG-11540: FlutterFlow, through FlutterFlow's own CLI (`flutterflow ai`).
+    //
+    // WHAT "FLUTTERFLOW MCP" ACTUALLY IS. Not a hosted MCP endpoint. `flutterflow
+    // ai init <dir>` creates a local workspace holding a vendored Dart SDK and an
+    // MCP server registered in a workspace-root `.mcp.json`. The agent's own
+    // `.mcp.json` is platform-rendered, so a workspace-local server is never seen
+    // by the agent's session. The agent drives the same commands over Bash
+    // instead, which is what FlutterFlow's own Claude Code plugin does
+    // (github.com/FlutterFlow/flutterflow-claude) and is the same project state.
+    //
+    // HEADLESS, VERIFIED by running flutterflow_cli 0.0.41 on 2026-10-15: `init`
+    // reads FF_API_KEY from the environment, takes the workspace positionally and
+    // the project as `--project`, and never prompts when stdin is not a TTY. With
+    // no key it fails fast ("API key is required") rather than hanging. A key
+    // from the environment is never written to the CLI's credential store.
+    // Neither `flutterflow --version` nor `flutterflow ai --version` works outside
+    // a workspace, which is why the probe is central HTTP (connectivity-probe.ts).
+    id: "flutterflow",
+    name: "FlutterFlow",
+    category: "code",
+    description: "Build and edit FlutterFlow apps with the FlutterFlow CLI. Start with `flutterflow ai init <dir> --project <project-id>` (the key is already in FF_API_KEY), work inside that folder, inspect and validate before you run, and never read the folder's .flutterflow/.env (it holds the key). Never pass --yes to native-file unlock or lock, and ask a person before publish-library.",
+    supported_auth_types: ["api_key"],
+    // flutterflow_cli is 0.0.x and the AI SDK it downloads is versioned server-side.
+    beta: true,
+    installable: { category: "Code", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "flutterflow:read-project",
+        name: "Read Project",
+        description: "Inspect, search and validate a FlutterFlow project: pages, components, resources, status and run history",
+        access: "read"
+      },
+      {
+        id: "flutterflow:edit-project",
+        name: "Edit Project",
+        description: "Push changes to a FlutterFlow project: pages, widgets, state, actions and theme",
+        access: "write"
+      },
+      {
+        id: "flutterflow:publish-library",
+        name: "Publish Library",
+        description: "Publish a new version of a FlutterFlow library that other projects depend on",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "flutterflow_cli",
+      binary: "flutterflow",
+      // `flutterflow ai` and the SDK it downloads both authenticate from this
+      // (the legacy FLUTTERFLOW_API_TOKEN feeds only export-code/deploy-firebase).
+      env_key: "FF_API_KEY",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). The CLI is a Dart pub package, and AL2023 has no Dart
+      // rpm, so this installs Google's official SDK zip into a private prefix
+      // (about 650 MB, which is why it is per-integration and not in the base
+      // image) and puts a wrapper, not pub's shim, at /usr/local/bin/flutterflow.
+      // pub's shim runs a bare `dart`, so a different Dart earlier on PATH would
+      // reject the 3.13.5 snapshot; the wrapper pins our Dart for the CLI AND for
+      // the `dart run` the downloaded SDK does. Re-runnable: a timed-out run
+      // (180s) resumes from whatever finished. The SDK is unzipped into a
+      // staging dir INSIDE the prefix and renamed into place last (CodeRabbit on
+      // #7007): a run killed mid-unzip must never leave a partial dart-sdk that
+      // passes the version check and then fails every retry. Staging on the same
+      // filesystem is what makes the final `mv` a rename rather than a copy.
+      // Versions pinned on purpose: bump
+      // them together, after re-running the headless check above.
+      script: `set -e; d=/usr/local/flutterflow; v=3.13.5; case "$(uname -m)" in x86_64) a=x64;; aarch64|arm64) a=arm64;; *) echo "flutterflow: unsupported architecture $(uname -m)" >&2; exit 1;; esac; if ! "$d/dart-sdk/bin/dart" --version 2>&1 | grep -q "version: $v "; then if ! command -v unzip >/dev/null 2>&1; then if command -v dnf >/dev/null 2>&1; then dnf install -y unzip; elif command -v apt-get >/dev/null 2>&1; then apt-get update && apt-get install -y unzip; else echo "flutterflow: unzip missing and no supported installer (need dnf or apt-get)" >&2; exit 1; fi; fi; mkdir -p "$d"; t=$(mktemp -d "$d/.stage.XXXXXX"); trap 'rm -rf "$t"' EXIT; curl -fsSL "https://storage.googleapis.com/dart-archive/channels/stable/release/$v/sdk/dartsdk-linux-$a-release.zip" -o "$t/dart.zip"; unzip -q "$t/dart.zip" -d "$t/x"; rm -rf "$d/dart-sdk"; mv "$t/x/dart-sdk" "$d/dart-sdk"; fi; PATH="$d/dart-sdk/bin:$PATH" PUB_CACHE="$d/pub-cache" "$d/dart-sdk/bin/dart" pub global activate flutterflow_cli 0.0.41; printf '#!/bin/sh\\nPATH="%s/dart-sdk/bin:$PATH" PUB_CACHE="%s/pub-cache" exec "%s/pub-cache/bin/flutterflow" "$@"\\n' "$d" "$d" "$d" > /usr/local/bin/flutterflow; chmod 755 /usr/local/bin/flutterflow`
+    },
+    docs_url: "https://docs.flutterflow.io/flutterflow-cli/build/"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",
@@ -30840,6 +30912,20 @@ var FLAG_REGISTRY = [
     // on for their own org. Only a platform admin can (PR #6522 review).
     platformAdminOnly: true
   },
+  {
+    key: "direct-chat-voice",
+    description: "Show the microphone (voice) button in the web Direct Chat composer - the Direct Chat drawer and the agent-screen chat dock (ENG-11542). Off by default: voice set expectations it does not yet meet for customers, but the team still needs it for testing, so it is enabled per org rather than removed. Does not gate the mobile PWA voice switch or the server voice-session routes.",
+    flagType: "boolean",
+    // PUBLIC (ADR-0022 §2): read in the browser via usePublicBooleanFlag, so it
+    // must be in the GET /flags map. No env override (UI rollout, not an
+    // operator gate). Ships dark (default false).
+    public: true,
+    defaultValue: false,
+    // Platform admin only: the point of the flag is keeping a not-ready feature
+    // away from customers, so a customer org admin must not be able to switch
+    // it back on for their own org.
+    platformAdminOnly: true
+  },
   {
     key: "platform-maintenance-mode",
     description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',

package/dist/mcp/origami.js

@@ -40948,6 +40948,78 @@ var INTEGRATION_REGISTRY = [
     },
     docs_url: "https://www.framer.com/developers/server-api-quick-start"
   },
+  {
+    // ENG-11540: FlutterFlow, through FlutterFlow's own CLI (`flutterflow ai`).
+    //
+    // WHAT "FLUTTERFLOW MCP" ACTUALLY IS. Not a hosted MCP endpoint. `flutterflow
+    // ai init <dir>` creates a local workspace holding a vendored Dart SDK and an
+    // MCP server registered in a workspace-root `.mcp.json`. The agent's own
+    // `.mcp.json` is platform-rendered, so a workspace-local server is never seen
+    // by the agent's session. The agent drives the same commands over Bash
+    // instead, which is what FlutterFlow's own Claude Code plugin does
+    // (github.com/FlutterFlow/flutterflow-claude) and is the same project state.
+    //
+    // HEADLESS, VERIFIED by running flutterflow_cli 0.0.41 on 2026-10-15: `init`
+    // reads FF_API_KEY from the environment, takes the workspace positionally and
+    // the project as `--project`, and never prompts when stdin is not a TTY. With
+    // no key it fails fast ("API key is required") rather than hanging. A key
+    // from the environment is never written to the CLI's credential store.
+    // Neither `flutterflow --version` nor `flutterflow ai --version` works outside
+    // a workspace, which is why the probe is central HTTP (connectivity-probe.ts).
+    id: "flutterflow",
+    name: "FlutterFlow",
+    category: "code",
+    description: "Build and edit FlutterFlow apps with the FlutterFlow CLI. Start with `flutterflow ai init <dir> --project <project-id>` (the key is already in FF_API_KEY), work inside that folder, inspect and validate before you run, and never read the folder's .flutterflow/.env (it holds the key). Never pass --yes to native-file unlock or lock, and ask a person before publish-library.",
+    supported_auth_types: ["api_key"],
+    // flutterflow_cli is 0.0.x and the AI SDK it downloads is versioned server-side.
+    beta: true,
+    installable: { category: "Code", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "flutterflow:read-project",
+        name: "Read Project",
+        description: "Inspect, search and validate a FlutterFlow project: pages, components, resources, status and run history",
+        access: "read"
+      },
+      {
+        id: "flutterflow:edit-project",
+        name: "Edit Project",
+        description: "Push changes to a FlutterFlow project: pages, widgets, state, actions and theme",
+        access: "write"
+      },
+      {
+        id: "flutterflow:publish-library",
+        name: "Publish Library",
+        description: "Publish a new version of a FlutterFlow library that other projects depend on",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "flutterflow_cli",
+      binary: "flutterflow",
+      // `flutterflow ai` and the SDK it downloads both authenticate from this
+      // (the legacy FLUTTERFLOW_API_TOKEN feeds only export-code/deploy-firebase).
+      env_key: "FF_API_KEY",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). The CLI is a Dart pub package, and AL2023 has no Dart
+      // rpm, so this installs Google's official SDK zip into a private prefix
+      // (about 650 MB, which is why it is per-integration and not in the base
+      // image) and puts a wrapper, not pub's shim, at /usr/local/bin/flutterflow.
+      // pub's shim runs a bare `dart`, so a different Dart earlier on PATH would
+      // reject the 3.13.5 snapshot; the wrapper pins our Dart for the CLI AND for
+      // the `dart run` the downloaded SDK does. Re-runnable: a timed-out run
+      // (180s) resumes from whatever finished. The SDK is unzipped into a
+      // staging dir INSIDE the prefix and renamed into place last (CodeRabbit on
+      // #7007): a run killed mid-unzip must never leave a partial dart-sdk that
+      // passes the version check and then fails every retry. Staging on the same
+      // filesystem is what makes the final `mv` a rename rather than a copy.
+      // Versions pinned on purpose: bump
+      // them together, after re-running the headless check above.
+      script: `set -e; d=/usr/local/flutterflow; v=3.13.5; case "$(uname -m)" in x86_64) a=x64;; aarch64|arm64) a=arm64;; *) echo "flutterflow: unsupported architecture $(uname -m)" >&2; exit 1;; esac; if ! "$d/dart-sdk/bin/dart" --version 2>&1 | grep -q "version: $v "; then if ! command -v unzip >/dev/null 2>&1; then if command -v dnf >/dev/null 2>&1; then dnf install -y unzip; elif command -v apt-get >/dev/null 2>&1; then apt-get update && apt-get install -y unzip; else echo "flutterflow: unzip missing and no supported installer (need dnf or apt-get)" >&2; exit 1; fi; fi; mkdir -p "$d"; t=$(mktemp -d "$d/.stage.XXXXXX"); trap 'rm -rf "$t"' EXIT; curl -fsSL "https://storage.googleapis.com/dart-archive/channels/stable/release/$v/sdk/dartsdk-linux-$a-release.zip" -o "$t/dart.zip"; unzip -q "$t/dart.zip" -d "$t/x"; rm -rf "$d/dart-sdk"; mv "$t/x/dart-sdk" "$d/dart-sdk"; fi; PATH="$d/dart-sdk/bin:$PATH" PUB_CACHE="$d/pub-cache" "$d/dart-sdk/bin/dart" pub global activate flutterflow_cli 0.0.41; printf '#!/bin/sh\\nPATH="%s/dart-sdk/bin:$PATH" PUB_CACHE="%s/pub-cache" exec "%s/pub-cache/bin/flutterflow" "$@"\\n' "$d" "$d" "$d" > /usr/local/bin/flutterflow; chmod 755 /usr/local/bin/flutterflow`
+    },
+    docs_url: "https://docs.flutterflow.io/flutterflow-cli/build/"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",
@@ -44769,6 +44841,20 @@ var FLAG_REGISTRY = [
     // on for their own org. Only a platform admin can (PR #6522 review).
     platformAdminOnly: true
   },
+  {
+    key: "direct-chat-voice",
+    description: "Show the microphone (voice) button in the web Direct Chat composer - the Direct Chat drawer and the agent-screen chat dock (ENG-11542). Off by default: voice set expectations it does not yet meet for customers, but the team still needs it for testing, so it is enabled per org rather than removed. Does not gate the mobile PWA voice switch or the server voice-session routes.",
+    flagType: "boolean",
+    // PUBLIC (ADR-0022 §2): read in the browser via usePublicBooleanFlag, so it
+    // must be in the GET /flags map. No env override (UI rollout, not an
+    // operator gate). Ships dark (default false).
+    public: true,
+    defaultValue: false,
+    // Platform admin only: the point of the flag is keeping a not-ready feature
+    // away from customers, so a customer org admin must not be able to switch
+    // it back on for their own org.
+    platformAdminOnly: true
+  },
   {
     key: "platform-maintenance-mode",
     description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',

package/dist/mcp/slack-channel.js

@@ -35335,6 +35335,78 @@ var INTEGRATION_REGISTRY = [
     },
     docs_url: "https://www.framer.com/developers/server-api-quick-start"
   },
+  {
+    // ENG-11540: FlutterFlow, through FlutterFlow's own CLI (`flutterflow ai`).
+    //
+    // WHAT "FLUTTERFLOW MCP" ACTUALLY IS. Not a hosted MCP endpoint. `flutterflow
+    // ai init <dir>` creates a local workspace holding a vendored Dart SDK and an
+    // MCP server registered in a workspace-root `.mcp.json`. The agent's own
+    // `.mcp.json` is platform-rendered, so a workspace-local server is never seen
+    // by the agent's session. The agent drives the same commands over Bash
+    // instead, which is what FlutterFlow's own Claude Code plugin does
+    // (github.com/FlutterFlow/flutterflow-claude) and is the same project state.
+    //
+    // HEADLESS, VERIFIED by running flutterflow_cli 0.0.41 on 2026-10-15: `init`
+    // reads FF_API_KEY from the environment, takes the workspace positionally and
+    // the project as `--project`, and never prompts when stdin is not a TTY. With
+    // no key it fails fast ("API key is required") rather than hanging. A key
+    // from the environment is never written to the CLI's credential store.
+    // Neither `flutterflow --version` nor `flutterflow ai --version` works outside
+    // a workspace, which is why the probe is central HTTP (connectivity-probe.ts).
+    id: "flutterflow",
+    name: "FlutterFlow",
+    category: "code",
+    description: "Build and edit FlutterFlow apps with the FlutterFlow CLI. Start with `flutterflow ai init <dir> --project <project-id>` (the key is already in FF_API_KEY), work inside that folder, inspect and validate before you run, and never read the folder's .flutterflow/.env (it holds the key). Never pass --yes to native-file unlock or lock, and ask a person before publish-library.",
+    supported_auth_types: ["api_key"],
+    // flutterflow_cli is 0.0.x and the AI SDK it downloads is versioned server-side.
+    beta: true,
+    installable: { category: "Code", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "flutterflow:read-project",
+        name: "Read Project",
+        description: "Inspect, search and validate a FlutterFlow project: pages, components, resources, status and run history",
+        access: "read"
+      },
+      {
+        id: "flutterflow:edit-project",
+        name: "Edit Project",
+        description: "Push changes to a FlutterFlow project: pages, widgets, state, actions and theme",
+        access: "write"
+      },
+      {
+        id: "flutterflow:publish-library",
+        name: "Publish Library",
+        description: "Publish a new version of a FlutterFlow library that other projects depend on",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "flutterflow_cli",
+      binary: "flutterflow",
+      // `flutterflow ai` and the SDK it downloads both authenticate from this
+      // (the legacy FLUTTERFLOW_API_TOKEN feeds only export-code/deploy-firebase).
+      env_key: "FF_API_KEY",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). The CLI is a Dart pub package, and AL2023 has no Dart
+      // rpm, so this installs Google's official SDK zip into a private prefix
+      // (about 650 MB, which is why it is per-integration and not in the base
+      // image) and puts a wrapper, not pub's shim, at /usr/local/bin/flutterflow.
+      // pub's shim runs a bare `dart`, so a different Dart earlier on PATH would
+      // reject the 3.13.5 snapshot; the wrapper pins our Dart for the CLI AND for
+      // the `dart run` the downloaded SDK does. Re-runnable: a timed-out run
+      // (180s) resumes from whatever finished. The SDK is unzipped into a
+      // staging dir INSIDE the prefix and renamed into place last (CodeRabbit on
+      // #7007): a run killed mid-unzip must never leave a partial dart-sdk that
+      // passes the version check and then fails every retry. Staging on the same
+      // filesystem is what makes the final `mv` a rename rather than a copy.
+      // Versions pinned on purpose: bump
+      // them together, after re-running the headless check above.
+      script: `set -e; d=/usr/local/flutterflow; v=3.13.5; case "$(uname -m)" in x86_64) a=x64;; aarch64|arm64) a=arm64;; *) echo "flutterflow: unsupported architecture $(uname -m)" >&2; exit 1;; esac; if ! "$d/dart-sdk/bin/dart" --version 2>&1 | grep -q "version: $v "; then if ! command -v unzip >/dev/null 2>&1; then if command -v dnf >/dev/null 2>&1; then dnf install -y unzip; elif command -v apt-get >/dev/null 2>&1; then apt-get update && apt-get install -y unzip; else echo "flutterflow: unzip missing and no supported installer (need dnf or apt-get)" >&2; exit 1; fi; fi; mkdir -p "$d"; t=$(mktemp -d "$d/.stage.XXXXXX"); trap 'rm -rf "$t"' EXIT; curl -fsSL "https://storage.googleapis.com/dart-archive/channels/stable/release/$v/sdk/dartsdk-linux-$a-release.zip" -o "$t/dart.zip"; unzip -q "$t/dart.zip" -d "$t/x"; rm -rf "$d/dart-sdk"; mv "$t/x/dart-sdk" "$d/dart-sdk"; fi; PATH="$d/dart-sdk/bin:$PATH" PUB_CACHE="$d/pub-cache" "$d/dart-sdk/bin/dart" pub global activate flutterflow_cli 0.0.41; printf '#!/bin/sh\\nPATH="%s/dart-sdk/bin:$PATH" PUB_CACHE="%s/pub-cache" exec "%s/pub-cache/bin/flutterflow" "$@"\\n' "$d" "$d" "$d" > /usr/local/bin/flutterflow; chmod 755 /usr/local/bin/flutterflow`
+    },
+    docs_url: "https://docs.flutterflow.io/flutterflow-cli/build/"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",
@@ -39578,6 +39650,20 @@ var FLAG_REGISTRY = [
     // on for their own org. Only a platform admin can (PR #6522 review).
     platformAdminOnly: true
   },
+  {
+    key: "direct-chat-voice",
+    description: "Show the microphone (voice) button in the web Direct Chat composer - the Direct Chat drawer and the agent-screen chat dock (ENG-11542). Off by default: voice set expectations it does not yet meet for customers, but the team still needs it for testing, so it is enabled per org rather than removed. Does not gate the mobile PWA voice switch or the server voice-session routes.",
+    flagType: "boolean",
+    // PUBLIC (ADR-0022 §2): read in the browser via usePublicBooleanFlag, so it
+    // must be in the GET /flags map. No env override (UI rollout, not an
+    // operator gate). Ships dark (default false).
+    public: true,
+    defaultValue: false,
+    // Platform admin only: the point of the flag is keeping a not-ready feature
+    // away from customers, so a customer org admin must not be able to switch
+    // it back on for their own org.
+    platformAdminOnly: true
+  },
   {
     key: "platform-maintenance-mode",
     description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',

package/dist/mcp/telegram-channel.js

@@ -35569,6 +35569,78 @@ var INTEGRATION_REGISTRY = [
     },
     docs_url: "https://www.framer.com/developers/server-api-quick-start"
   },
+  {
+    // ENG-11540: FlutterFlow, through FlutterFlow's own CLI (`flutterflow ai`).
+    //
+    // WHAT "FLUTTERFLOW MCP" ACTUALLY IS. Not a hosted MCP endpoint. `flutterflow
+    // ai init <dir>` creates a local workspace holding a vendored Dart SDK and an
+    // MCP server registered in a workspace-root `.mcp.json`. The agent's own
+    // `.mcp.json` is platform-rendered, so a workspace-local server is never seen
+    // by the agent's session. The agent drives the same commands over Bash
+    // instead, which is what FlutterFlow's own Claude Code plugin does
+    // (github.com/FlutterFlow/flutterflow-claude) and is the same project state.
+    //
+    // HEADLESS, VERIFIED by running flutterflow_cli 0.0.41 on 2026-10-15: `init`
+    // reads FF_API_KEY from the environment, takes the workspace positionally and
+    // the project as `--project`, and never prompts when stdin is not a TTY. With
+    // no key it fails fast ("API key is required") rather than hanging. A key
+    // from the environment is never written to the CLI's credential store.
+    // Neither `flutterflow --version` nor `flutterflow ai --version` works outside
+    // a workspace, which is why the probe is central HTTP (connectivity-probe.ts).
+    id: "flutterflow",
+    name: "FlutterFlow",
+    category: "code",
+    description: "Build and edit FlutterFlow apps with the FlutterFlow CLI. Start with `flutterflow ai init <dir> --project <project-id>` (the key is already in FF_API_KEY), work inside that folder, inspect and validate before you run, and never read the folder's .flutterflow/.env (it holds the key). Never pass --yes to native-file unlock or lock, and ask a person before publish-library.",
+    supported_auth_types: ["api_key"],
+    // flutterflow_cli is 0.0.x and the AI SDK it downloads is versioned server-side.
+    beta: true,
+    installable: { category: "Code", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "flutterflow:read-project",
+        name: "Read Project",
+        description: "Inspect, search and validate a FlutterFlow project: pages, components, resources, status and run history",
+        access: "read"
+      },
+      {
+        id: "flutterflow:edit-project",
+        name: "Edit Project",
+        description: "Push changes to a FlutterFlow project: pages, widgets, state, actions and theme",
+        access: "write"
+      },
+      {
+        id: "flutterflow:publish-library",
+        name: "Publish Library",
+        description: "Publish a new version of a FlutterFlow library that other projects depend on",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "flutterflow_cli",
+      binary: "flutterflow",
+      // `flutterflow ai` and the SDK it downloads both authenticate from this
+      // (the legacy FLUTTERFLOW_API_TOKEN feeds only export-code/deploy-firebase).
+      env_key: "FF_API_KEY",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). The CLI is a Dart pub package, and AL2023 has no Dart
+      // rpm, so this installs Google's official SDK zip into a private prefix
+      // (about 650 MB, which is why it is per-integration and not in the base
+      // image) and puts a wrapper, not pub's shim, at /usr/local/bin/flutterflow.
+      // pub's shim runs a bare `dart`, so a different Dart earlier on PATH would
+      // reject the 3.13.5 snapshot; the wrapper pins our Dart for the CLI AND for
+      // the `dart run` the downloaded SDK does. Re-runnable: a timed-out run
+      // (180s) resumes from whatever finished. The SDK is unzipped into a
+      // staging dir INSIDE the prefix and renamed into place last (CodeRabbit on
+      // #7007): a run killed mid-unzip must never leave a partial dart-sdk that
+      // passes the version check and then fails every retry. Staging on the same
+      // filesystem is what makes the final `mv` a rename rather than a copy.
+      // Versions pinned on purpose: bump
+      // them together, after re-running the headless check above.
+      script: `set -e; d=/usr/local/flutterflow; v=3.13.5; case "$(uname -m)" in x86_64) a=x64;; aarch64|arm64) a=arm64;; *) echo "flutterflow: unsupported architecture $(uname -m)" >&2; exit 1;; esac; if ! "$d/dart-sdk/bin/dart" --version 2>&1 | grep -q "version: $v "; then if ! command -v unzip >/dev/null 2>&1; then if command -v dnf >/dev/null 2>&1; then dnf install -y unzip; elif command -v apt-get >/dev/null 2>&1; then apt-get update && apt-get install -y unzip; else echo "flutterflow: unzip missing and no supported installer (need dnf or apt-get)" >&2; exit 1; fi; fi; mkdir -p "$d"; t=$(mktemp -d "$d/.stage.XXXXXX"); trap 'rm -rf "$t"' EXIT; curl -fsSL "https://storage.googleapis.com/dart-archive/channels/stable/release/$v/sdk/dartsdk-linux-$a-release.zip" -o "$t/dart.zip"; unzip -q "$t/dart.zip" -d "$t/x"; rm -rf "$d/dart-sdk"; mv "$t/x/dart-sdk" "$d/dart-sdk"; fi; PATH="$d/dart-sdk/bin:$PATH" PUB_CACHE="$d/pub-cache" "$d/dart-sdk/bin/dart" pub global activate flutterflow_cli 0.0.41; printf '#!/bin/sh\\nPATH="%s/dart-sdk/bin:$PATH" PUB_CACHE="%s/pub-cache" exec "%s/pub-cache/bin/flutterflow" "$@"\\n' "$d" "$d" "$d" > /usr/local/bin/flutterflow; chmod 755 /usr/local/bin/flutterflow`
+    },
+    docs_url: "https://docs.flutterflow.io/flutterflow-cli/build/"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",
@@ -39806,6 +39878,20 @@ var FLAG_REGISTRY = [
     // on for their own org. Only a platform admin can (PR #6522 review).
     platformAdminOnly: true
   },
+  {
+    key: "direct-chat-voice",
+    description: "Show the microphone (voice) button in the web Direct Chat composer - the Direct Chat drawer and the agent-screen chat dock (ENG-11542). Off by default: voice set expectations it does not yet meet for customers, but the team still needs it for testing, so it is enabled per org rather than removed. Does not gate the mobile PWA voice switch or the server voice-session routes.",
+    flagType: "boolean",
+    // PUBLIC (ADR-0022 §2): read in the browser via usePublicBooleanFlag, so it
+    // must be in the GET /flags map. No env override (UI rollout, not an
+    // operator gate). Ships dark (default false).
+    public: true,
+    defaultValue: false,
+    // Platform admin only: the point of the flag is keeping a not-ready feature
+    // away from customers, so a customer org admin must not be able to switch
+    // it back on for their own org.
+    platformAdminOnly: true
+  },
   {
     key: "platform-maintenance-mode",
     description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',

package/dist/{persistent-session-QSE66QYT.js → persistent-session-F2LRKDFL.js}

@@ -68,8 +68,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-23GMWGOP.js";
-import "./chunk-JFABPA3Z.js";
+} from "./chunk-KG4IEJEF.js";
+import "./chunk-TKBGHAN3.js";
 import "./chunk-B6UYVEMD.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -145,4 +145,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-QSE66QYT.js.map
+//# sourceMappingURL=persistent-session-F2LRKDFL.js.map

package/dist/{responsiveness-probe-NC4A3FCR.js → responsiveness-probe-SM6XFJJ6.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-23GMWGOP.js";
-import "./chunk-JFABPA3Z.js";
+} from "./chunk-KG4IEJEF.js";
+import "./chunk-TKBGHAN3.js";
 import "./chunk-B6UYVEMD.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -802,4 +802,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-NC4A3FCR.js.map
+//# sourceMappingURL=responsiveness-probe-SM6XFJJ6.js.map

package/dist/{session-auth-dead-23ERZN4N.js → session-auth-dead-KNTFHDWV.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-JFABPA3Z.js";
+} from "./chunk-TKBGHAN3.js";
 import "./chunk-DGUM43GV.js";
 
 // src/lib/session-auth-dead.ts
@@ -204,4 +204,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-23ERZN4N.js.map
+//# sourceMappingURL=session-auth-dead-KNTFHDWV.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.1129",
+  "version": "0.28.1131",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {