@integrity-labs/agt-cli 0.28.1083 → 0.28.1085

package/dist/mcp/direct-chat-channel.js

@@ -34190,6 +34190,136 @@ var INTEGRATION_REGISTRY = [
     // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
     // every host that installed the MCP variant.
   },
+  {
+    // Quiver (api.quiver.ai) — AI vector graphics: draw an SVG from a prompt,
+    // redraw one from an instruction, trace a raster, add animation.
+    //
+    // PREMIUM (ADR-0031, epic ENG-6920). Ninjafy holds ONE Quiver account whose
+    // key (`QUIVER_ACCOUNT_KEY`) every customer's drawing bills back to, so the
+    // credential is a single platform-held secret and never a per-install one.
+    // `auth_type: 'none'` on the catalog row and `credential_source:
+    // 'platform_env'` on every runtime scope, so `resolveBrokerToken` reads the
+    // env var and skips the install-row lookup entirely.
+    //
+    // Ships DARK: until the secret is set the resolver fails closed with
+    // `platform_credential_missing` and every drawing errors clearly.
+    // Installable but inert, by design — the same posture x-search shipped with.
+    //
+    // WHY IT STOPPED BEING BYO. It launched bring-your-own-key. Premium means WE
+    // pay the vendor, so a customer key would defeat the point: there would be
+    // nothing to meter and nothing to bill. The flip cost nothing because Quiver
+    // had never deployed — zero installs, so none of the origami free→premium
+    // grandfathering applies (there is no cohort whose `credential_source`
+    // default would misclassify them as billed and take the integration dark).
+    // A later BYO tier is possible (ADR-0055, the Firecrawl shape) and would
+    // need its own entitlement gate; it is deliberately not offered now, because
+    // offering two auth types renders a connect picker that does not check
+    // `plans.byo_credentials` (ENG-9236).
+    //
+    // WHY TWO METERS, when the vendor bills in one unit. `credits` is Quiver's
+    // own billing unit and the response carries it per call, so metering it
+    // makes our margin a constant multiple no matter which model an agent picks
+    // — `arrow-1.1-max` costs materially more than `arrow-1.1`, which a flat
+    // per-call price would silently eat. But `credits` is documented as
+    // "omitted for token-priced models, whose measured totals are returned in
+    // `usage`", so a credits-only meter bills those calls at ZERO: free to the
+    // customer, invisible to the budget gate, and with nothing in the ledger to
+    // notice it by. `svg_operation` is the floor that closes that hole — it
+    // fires ONLY when `credits` is absent, so the two can never double-bill the
+    // same call. See `lib/quiver-metering.ts`.
+    id: "quiver",
+    name: "Quiver",
+    category: "media",
+    description: "AI vector graphics \u2014 draw an SVG from a description, redraw an existing one, trace a photo or screenshot into vector shapes, and add animation. Ninjafy manages the Quiver account for you; there is no key to enter.",
+    supported_auth_types: ["none"],
+    docs_url: "https://docs.quiver.ai/developers",
+    capabilities: [
+      {
+        id: "quiver:create",
+        name: "Create and change vector graphics",
+        description: "Draw, redraw, trace and animate SVG artwork. Billed per Quiver credit consumed.",
+        access: "write"
+      },
+      {
+        id: "quiver:read",
+        name: "Read models",
+        description: "List the available drawing models and their per-call credit cost. Free.",
+        access: "read"
+      }
+    ],
+    beta: true,
+    // No `installable` on purpose: quiver is a seed integration
+    // (integration-definitions.json), so the seed catalog already makes it
+    // picker-visible. This entry exists to carry the `premium` descriptor that
+    // `isPremiumDefinition` reads — which arms the per-org opt-in gate, the
+    // priced acknowledgement modal and the admin pricing tab. Same reasoning as
+    // social-scraping above.
+    premium: {
+      pricing: "usage",
+      note: "Billed per Quiver credit consumed. Listing models is free; drawing, editing, tracing and animating each debit credits.",
+      meters: [
+        { event_type: "svg_credits", unit: "credit" },
+        { event_type: "svg_operation", unit: "operation" }
+      ]
+    }
+  },
+  {
+    // theSVG (thesvg.org) — 6,500+ REAL brand marks as SVG, so an agent building
+    // a page can use the actual Stripe/Slack/AWS logo instead of asking a
+    // drawing model for one. That distinction is the whole point of the
+    // integration: an AI-generated "Stripe logo" is a plausible fake, wrong in
+    // the way a customer notices and a trademark owner minds. Original artwork
+    // is Quiver's job; existing marks are this one's.
+    //
+    // WHY A LOCAL STDIO MCP AND NOT THE DIRECT-HTTP LANE. thesvg.org is a
+    // STATIC SITE — its own CLI says so in as many words ("there is no dynamic
+    // API"). The only two endpoints are `/api/registry.json`, the entire
+    // 2.97 MB / 6,523-entry manifest, and `/icons/{slug}/{variant}.svg`. Search
+    // is client-side filtering over that manifest, which the Direct-HTTP broker
+    // cannot do: it forwards the vendor's whole response body to the agent, so
+    // a `search_icons` descriptor would put 2.97 MB of registry into the
+    // agent's context on every call. The vendor's own MCP server bundles the
+    // registry and searches it in-process, which is precisely the shape the
+    // missing API leaves you needing.
+    //
+    // WHY THE VERSION IS PINNED and AWS's is `@latest`: this server's registry
+    // is baked in at BUILD time, so the pin is what decides which icons exist
+    // AND what markup lands on a customer's published page. Bumping it is a
+    // deliberate act that also refreshes the icon set — not a silent
+    // third-party update to artwork we are about to publish under a customer's
+    // domain.
+    //
+    // No credential anywhere: the registry and the jsDelivr CDN the server
+    // fetches SVG from are both public, so `auth_types: ['none']` is the honest
+    // classification rather than the ENG-8440 kind of lie Hard Rule 17 warns
+    // about — there genuinely is no key to enter and the install IS live
+    // immediately.
+    id: "thesvg",
+    name: "theSVG",
+    category: "media",
+    description: "Brand logos and icons as real SVG \u2014 search 6,500+ marks by name and pull the exact artwork, in mono, colour, light, dark or wordmark variants",
+    supported_auth_types: ["none"],
+    docs_url: "https://thesvg.org",
+    capabilities: [
+      {
+        id: "thesvg:read",
+        name: "Find and fetch brand icons",
+        description: "Search the icon library, list an icon's variants and categories, and fetch its SVG markup or CDN URL",
+        access: "read"
+      }
+    ],
+    installable: { category: "Media", authTypes: ["none"] },
+    beta: true,
+    // ENG-5815 data-driven path — no buildMcpJson edit, same as AWS.
+    nativeMcp: {
+      command: "npx",
+      args: ["-y", "@thesvg/mcp-server@0.8.2"],
+      env: {
+        PATH: "{{process_env.PATH}}",
+        HOME: "{{process_env.HOME}}"
+      }
+    }
+  },
   {
     id: "qmd",
     name: "QMD Memory Search",
@@ -35315,6 +35445,10 @@ var NOTICE_KIND_AUDIENCE = {
   // "Your `<verb>` approval request (`<uuid>`) EXPIRED at …" — in the report,
   // uuid and all.
   approval_expired: "agent",
+  // ENG-11334: canvas.publish_public approved / denied / approved-but-not-applied.
+  // Second-person instructions to the agent ("Tell the user...", "do not
+  // republish"); the user learns the outcome from the agent, not this row.
+  canvas_public_approval_resolved: "agent",
   // A routine fired; the agent picks the work up.
   routine_firing_result: "agent",
   // Live-advisor wake: "Call `live_read` with escalation_id …" — a literal tool
@@ -38126,7 +38260,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "approval-unified-authority",
-    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict and log approval_authority_would_reject (ingress, verb, org, reason) for every tap it would refuse, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
+    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict, including the verb's declared approver boundary (ENG-11337), and log approval_authority_would_reject (ingress, verb, org, reason, boundary) for every tap it would refuse and approval_authority_would_admit (ingress, verb, org, basis, boundary) for every tap it would admit, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
     flagType: "enum",
     allowedValues: ["off", "shadow", "enforce"],
     // Safe/default value is `off` (no computation, no extra reads on the tap path). A flag-DB read

package/dist/mcp/index.js

@@ -26693,6 +26693,136 @@ var INTEGRATION_REGISTRY = [
     // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
     // every host that installed the MCP variant.
   },
+  {
+    // Quiver (api.quiver.ai) — AI vector graphics: draw an SVG from a prompt,
+    // redraw one from an instruction, trace a raster, add animation.
+    //
+    // PREMIUM (ADR-0031, epic ENG-6920). Ninjafy holds ONE Quiver account whose
+    // key (`QUIVER_ACCOUNT_KEY`) every customer's drawing bills back to, so the
+    // credential is a single platform-held secret and never a per-install one.
+    // `auth_type: 'none'` on the catalog row and `credential_source:
+    // 'platform_env'` on every runtime scope, so `resolveBrokerToken` reads the
+    // env var and skips the install-row lookup entirely.
+    //
+    // Ships DARK: until the secret is set the resolver fails closed with
+    // `platform_credential_missing` and every drawing errors clearly.
+    // Installable but inert, by design — the same posture x-search shipped with.
+    //
+    // WHY IT STOPPED BEING BYO. It launched bring-your-own-key. Premium means WE
+    // pay the vendor, so a customer key would defeat the point: there would be
+    // nothing to meter and nothing to bill. The flip cost nothing because Quiver
+    // had never deployed — zero installs, so none of the origami free→premium
+    // grandfathering applies (there is no cohort whose `credential_source`
+    // default would misclassify them as billed and take the integration dark).
+    // A later BYO tier is possible (ADR-0055, the Firecrawl shape) and would
+    // need its own entitlement gate; it is deliberately not offered now, because
+    // offering two auth types renders a connect picker that does not check
+    // `plans.byo_credentials` (ENG-9236).
+    //
+    // WHY TWO METERS, when the vendor bills in one unit. `credits` is Quiver's
+    // own billing unit and the response carries it per call, so metering it
+    // makes our margin a constant multiple no matter which model an agent picks
+    // — `arrow-1.1-max` costs materially more than `arrow-1.1`, which a flat
+    // per-call price would silently eat. But `credits` is documented as
+    // "omitted for token-priced models, whose measured totals are returned in
+    // `usage`", so a credits-only meter bills those calls at ZERO: free to the
+    // customer, invisible to the budget gate, and with nothing in the ledger to
+    // notice it by. `svg_operation` is the floor that closes that hole — it
+    // fires ONLY when `credits` is absent, so the two can never double-bill the
+    // same call. See `lib/quiver-metering.ts`.
+    id: "quiver",
+    name: "Quiver",
+    category: "media",
+    description: "AI vector graphics \u2014 draw an SVG from a description, redraw an existing one, trace a photo or screenshot into vector shapes, and add animation. Ninjafy manages the Quiver account for you; there is no key to enter.",
+    supported_auth_types: ["none"],
+    docs_url: "https://docs.quiver.ai/developers",
+    capabilities: [
+      {
+        id: "quiver:create",
+        name: "Create and change vector graphics",
+        description: "Draw, redraw, trace and animate SVG artwork. Billed per Quiver credit consumed.",
+        access: "write"
+      },
+      {
+        id: "quiver:read",
+        name: "Read models",
+        description: "List the available drawing models and their per-call credit cost. Free.",
+        access: "read"
+      }
+    ],
+    beta: true,
+    // No `installable` on purpose: quiver is a seed integration
+    // (integration-definitions.json), so the seed catalog already makes it
+    // picker-visible. This entry exists to carry the `premium` descriptor that
+    // `isPremiumDefinition` reads — which arms the per-org opt-in gate, the
+    // priced acknowledgement modal and the admin pricing tab. Same reasoning as
+    // social-scraping above.
+    premium: {
+      pricing: "usage",
+      note: "Billed per Quiver credit consumed. Listing models is free; drawing, editing, tracing and animating each debit credits.",
+      meters: [
+        { event_type: "svg_credits", unit: "credit" },
+        { event_type: "svg_operation", unit: "operation" }
+      ]
+    }
+  },
+  {
+    // theSVG (thesvg.org) — 6,500+ REAL brand marks as SVG, so an agent building
+    // a page can use the actual Stripe/Slack/AWS logo instead of asking a
+    // drawing model for one. That distinction is the whole point of the
+    // integration: an AI-generated "Stripe logo" is a plausible fake, wrong in
+    // the way a customer notices and a trademark owner minds. Original artwork
+    // is Quiver's job; existing marks are this one's.
+    //
+    // WHY A LOCAL STDIO MCP AND NOT THE DIRECT-HTTP LANE. thesvg.org is a
+    // STATIC SITE — its own CLI says so in as many words ("there is no dynamic
+    // API"). The only two endpoints are `/api/registry.json`, the entire
+    // 2.97 MB / 6,523-entry manifest, and `/icons/{slug}/{variant}.svg`. Search
+    // is client-side filtering over that manifest, which the Direct-HTTP broker
+    // cannot do: it forwards the vendor's whole response body to the agent, so
+    // a `search_icons` descriptor would put 2.97 MB of registry into the
+    // agent's context on every call. The vendor's own MCP server bundles the
+    // registry and searches it in-process, which is precisely the shape the
+    // missing API leaves you needing.
+    //
+    // WHY THE VERSION IS PINNED and AWS's is `@latest`: this server's registry
+    // is baked in at BUILD time, so the pin is what decides which icons exist
+    // AND what markup lands on a customer's published page. Bumping it is a
+    // deliberate act that also refreshes the icon set — not a silent
+    // third-party update to artwork we are about to publish under a customer's
+    // domain.
+    //
+    // No credential anywhere: the registry and the jsDelivr CDN the server
+    // fetches SVG from are both public, so `auth_types: ['none']` is the honest
+    // classification rather than the ENG-8440 kind of lie Hard Rule 17 warns
+    // about — there genuinely is no key to enter and the install IS live
+    // immediately.
+    id: "thesvg",
+    name: "theSVG",
+    category: "media",
+    description: "Brand logos and icons as real SVG \u2014 search 6,500+ marks by name and pull the exact artwork, in mono, colour, light, dark or wordmark variants",
+    supported_auth_types: ["none"],
+    docs_url: "https://thesvg.org",
+    capabilities: [
+      {
+        id: "thesvg:read",
+        name: "Find and fetch brand icons",
+        description: "Search the icon library, list an icon's variants and categories, and fetch its SVG markup or CDN URL",
+        access: "read"
+      }
+    ],
+    installable: { category: "Media", authTypes: ["none"] },
+    beta: true,
+    // ENG-5815 data-driven path — no buildMcpJson edit, same as AWS.
+    nativeMcp: {
+      command: "npx",
+      args: ["-y", "@thesvg/mcp-server@0.8.2"],
+      env: {
+        PATH: "{{process_env.PATH}}",
+        HOME: "{{process_env.HOME}}"
+      }
+    }
+  },
   {
     id: "qmd",
     name: "QMD Memory Search",
@@ -27818,6 +27948,10 @@ var NOTICE_KIND_AUDIENCE = {
   // "Your `<verb>` approval request (`<uuid>`) EXPIRED at …" — in the report,
   // uuid and all.
   approval_expired: "agent",
+  // ENG-11334: canvas.publish_public approved / denied / approved-but-not-applied.
+  // Second-person instructions to the agent ("Tell the user...", "do not
+  // republish"); the user learns the outcome from the agent, not this row.
+  canvas_public_approval_resolved: "agent",
   // A routine fired; the agent picks the work up.
   routine_firing_result: "agent",
   // Live-advisor wake: "Call `live_read` with escalation_id …" — a literal tool
@@ -30344,7 +30478,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "approval-unified-authority",
-    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict and log approval_authority_would_reject (ingress, verb, org, reason) for every tap it would refuse, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
+    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict, including the verb's declared approver boundary (ENG-11337), and log approval_authority_would_reject (ingress, verb, org, reason, boundary) for every tap it would refuse and approval_authority_would_admit (ingress, verb, org, basis, boundary) for every tap it would admit, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
     flagType: "enum",
     allowedValues: ["off", "shadow", "enforce"],
     // Safe/default value is `off` (no computation, no extra reads on the tap path). A flag-DB read

package/dist/mcp/origami.js

@@ -40819,6 +40819,136 @@ var INTEGRATION_REGISTRY = [
     // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
     // every host that installed the MCP variant.
   },
+  {
+    // Quiver (api.quiver.ai) — AI vector graphics: draw an SVG from a prompt,
+    // redraw one from an instruction, trace a raster, add animation.
+    //
+    // PREMIUM (ADR-0031, epic ENG-6920). Ninjafy holds ONE Quiver account whose
+    // key (`QUIVER_ACCOUNT_KEY`) every customer's drawing bills back to, so the
+    // credential is a single platform-held secret and never a per-install one.
+    // `auth_type: 'none'` on the catalog row and `credential_source:
+    // 'platform_env'` on every runtime scope, so `resolveBrokerToken` reads the
+    // env var and skips the install-row lookup entirely.
+    //
+    // Ships DARK: until the secret is set the resolver fails closed with
+    // `platform_credential_missing` and every drawing errors clearly.
+    // Installable but inert, by design — the same posture x-search shipped with.
+    //
+    // WHY IT STOPPED BEING BYO. It launched bring-your-own-key. Premium means WE
+    // pay the vendor, so a customer key would defeat the point: there would be
+    // nothing to meter and nothing to bill. The flip cost nothing because Quiver
+    // had never deployed — zero installs, so none of the origami free→premium
+    // grandfathering applies (there is no cohort whose `credential_source`
+    // default would misclassify them as billed and take the integration dark).
+    // A later BYO tier is possible (ADR-0055, the Firecrawl shape) and would
+    // need its own entitlement gate; it is deliberately not offered now, because
+    // offering two auth types renders a connect picker that does not check
+    // `plans.byo_credentials` (ENG-9236).
+    //
+    // WHY TWO METERS, when the vendor bills in one unit. `credits` is Quiver's
+    // own billing unit and the response carries it per call, so metering it
+    // makes our margin a constant multiple no matter which model an agent picks
+    // — `arrow-1.1-max` costs materially more than `arrow-1.1`, which a flat
+    // per-call price would silently eat. But `credits` is documented as
+    // "omitted for token-priced models, whose measured totals are returned in
+    // `usage`", so a credits-only meter bills those calls at ZERO: free to the
+    // customer, invisible to the budget gate, and with nothing in the ledger to
+    // notice it by. `svg_operation` is the floor that closes that hole — it
+    // fires ONLY when `credits` is absent, so the two can never double-bill the
+    // same call. See `lib/quiver-metering.ts`.
+    id: "quiver",
+    name: "Quiver",
+    category: "media",
+    description: "AI vector graphics \u2014 draw an SVG from a description, redraw an existing one, trace a photo or screenshot into vector shapes, and add animation. Ninjafy manages the Quiver account for you; there is no key to enter.",
+    supported_auth_types: ["none"],
+    docs_url: "https://docs.quiver.ai/developers",
+    capabilities: [
+      {
+        id: "quiver:create",
+        name: "Create and change vector graphics",
+        description: "Draw, redraw, trace and animate SVG artwork. Billed per Quiver credit consumed.",
+        access: "write"
+      },
+      {
+        id: "quiver:read",
+        name: "Read models",
+        description: "List the available drawing models and their per-call credit cost. Free.",
+        access: "read"
+      }
+    ],
+    beta: true,
+    // No `installable` on purpose: quiver is a seed integration
+    // (integration-definitions.json), so the seed catalog already makes it
+    // picker-visible. This entry exists to carry the `premium` descriptor that
+    // `isPremiumDefinition` reads — which arms the per-org opt-in gate, the
+    // priced acknowledgement modal and the admin pricing tab. Same reasoning as
+    // social-scraping above.
+    premium: {
+      pricing: "usage",
+      note: "Billed per Quiver credit consumed. Listing models is free; drawing, editing, tracing and animating each debit credits.",
+      meters: [
+        { event_type: "svg_credits", unit: "credit" },
+        { event_type: "svg_operation", unit: "operation" }
+      ]
+    }
+  },
+  {
+    // theSVG (thesvg.org) — 6,500+ REAL brand marks as SVG, so an agent building
+    // a page can use the actual Stripe/Slack/AWS logo instead of asking a
+    // drawing model for one. That distinction is the whole point of the
+    // integration: an AI-generated "Stripe logo" is a plausible fake, wrong in
+    // the way a customer notices and a trademark owner minds. Original artwork
+    // is Quiver's job; existing marks are this one's.
+    //
+    // WHY A LOCAL STDIO MCP AND NOT THE DIRECT-HTTP LANE. thesvg.org is a
+    // STATIC SITE — its own CLI says so in as many words ("there is no dynamic
+    // API"). The only two endpoints are `/api/registry.json`, the entire
+    // 2.97 MB / 6,523-entry manifest, and `/icons/{slug}/{variant}.svg`. Search
+    // is client-side filtering over that manifest, which the Direct-HTTP broker
+    // cannot do: it forwards the vendor's whole response body to the agent, so
+    // a `search_icons` descriptor would put 2.97 MB of registry into the
+    // agent's context on every call. The vendor's own MCP server bundles the
+    // registry and searches it in-process, which is precisely the shape the
+    // missing API leaves you needing.
+    //
+    // WHY THE VERSION IS PINNED and AWS's is `@latest`: this server's registry
+    // is baked in at BUILD time, so the pin is what decides which icons exist
+    // AND what markup lands on a customer's published page. Bumping it is a
+    // deliberate act that also refreshes the icon set — not a silent
+    // third-party update to artwork we are about to publish under a customer's
+    // domain.
+    //
+    // No credential anywhere: the registry and the jsDelivr CDN the server
+    // fetches SVG from are both public, so `auth_types: ['none']` is the honest
+    // classification rather than the ENG-8440 kind of lie Hard Rule 17 warns
+    // about — there genuinely is no key to enter and the install IS live
+    // immediately.
+    id: "thesvg",
+    name: "theSVG",
+    category: "media",
+    description: "Brand logos and icons as real SVG \u2014 search 6,500+ marks by name and pull the exact artwork, in mono, colour, light, dark or wordmark variants",
+    supported_auth_types: ["none"],
+    docs_url: "https://thesvg.org",
+    capabilities: [
+      {
+        id: "thesvg:read",
+        name: "Find and fetch brand icons",
+        description: "Search the icon library, list an icon's variants and categories, and fetch its SVG markup or CDN URL",
+        access: "read"
+      }
+    ],
+    installable: { category: "Media", authTypes: ["none"] },
+    beta: true,
+    // ENG-5815 data-driven path — no buildMcpJson edit, same as AWS.
+    nativeMcp: {
+      command: "npx",
+      args: ["-y", "@thesvg/mcp-server@0.8.2"],
+      env: {
+        PATH: "{{process_env.PATH}}",
+        HOME: "{{process_env.HOME}}"
+      }
+    }
+  },
   {
     id: "qmd",
     name: "QMD Memory Search",
@@ -41944,6 +42074,10 @@ var NOTICE_KIND_AUDIENCE = {
   // "Your `<verb>` approval request (`<uuid>`) EXPIRED at …" — in the report,
   // uuid and all.
   approval_expired: "agent",
+  // ENG-11334: canvas.publish_public approved / denied / approved-but-not-applied.
+  // Second-person instructions to the agent ("Tell the user...", "do not
+  // republish"); the user learns the outcome from the agent, not this row.
+  canvas_public_approval_resolved: "agent",
   // A routine fired; the agent picks the work up.
   routine_firing_result: "agent",
   // Live-advisor wake: "Call `live_read` with escalation_id …" — a literal tool
@@ -44267,7 +44401,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "approval-unified-authority",
-    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict and log approval_authority_would_reject (ingress, verb, org, reason) for every tap it would refuse, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
+    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict, including the verb's declared approver boundary (ENG-11337), and log approval_authority_would_reject (ingress, verb, org, reason, boundary) for every tap it would refuse and approval_authority_would_admit (ingress, verb, org, basis, boundary) for every tap it would admit, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
     flagType: "enum",
     allowedValues: ["off", "shadow", "enforce"],
     // Safe/default value is `off` (no computation, no extra reads on the tap path). A flag-DB read

package/dist/mcp/slack-channel.js

@@ -35033,6 +35033,136 @@ var INTEGRATION_REGISTRY = [
     // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
     // every host that installed the MCP variant.
   },
+  {
+    // Quiver (api.quiver.ai) — AI vector graphics: draw an SVG from a prompt,
+    // redraw one from an instruction, trace a raster, add animation.
+    //
+    // PREMIUM (ADR-0031, epic ENG-6920). Ninjafy holds ONE Quiver account whose
+    // key (`QUIVER_ACCOUNT_KEY`) every customer's drawing bills back to, so the
+    // credential is a single platform-held secret and never a per-install one.
+    // `auth_type: 'none'` on the catalog row and `credential_source:
+    // 'platform_env'` on every runtime scope, so `resolveBrokerToken` reads the
+    // env var and skips the install-row lookup entirely.
+    //
+    // Ships DARK: until the secret is set the resolver fails closed with
+    // `platform_credential_missing` and every drawing errors clearly.
+    // Installable but inert, by design — the same posture x-search shipped with.
+    //
+    // WHY IT STOPPED BEING BYO. It launched bring-your-own-key. Premium means WE
+    // pay the vendor, so a customer key would defeat the point: there would be
+    // nothing to meter and nothing to bill. The flip cost nothing because Quiver
+    // had never deployed — zero installs, so none of the origami free→premium
+    // grandfathering applies (there is no cohort whose `credential_source`
+    // default would misclassify them as billed and take the integration dark).
+    // A later BYO tier is possible (ADR-0055, the Firecrawl shape) and would
+    // need its own entitlement gate; it is deliberately not offered now, because
+    // offering two auth types renders a connect picker that does not check
+    // `plans.byo_credentials` (ENG-9236).
+    //
+    // WHY TWO METERS, when the vendor bills in one unit. `credits` is Quiver's
+    // own billing unit and the response carries it per call, so metering it
+    // makes our margin a constant multiple no matter which model an agent picks
+    // — `arrow-1.1-max` costs materially more than `arrow-1.1`, which a flat
+    // per-call price would silently eat. But `credits` is documented as
+    // "omitted for token-priced models, whose measured totals are returned in
+    // `usage`", so a credits-only meter bills those calls at ZERO: free to the
+    // customer, invisible to the budget gate, and with nothing in the ledger to
+    // notice it by. `svg_operation` is the floor that closes that hole — it
+    // fires ONLY when `credits` is absent, so the two can never double-bill the
+    // same call. See `lib/quiver-metering.ts`.
+    id: "quiver",
+    name: "Quiver",
+    category: "media",
+    description: "AI vector graphics \u2014 draw an SVG from a description, redraw an existing one, trace a photo or screenshot into vector shapes, and add animation. Ninjafy manages the Quiver account for you; there is no key to enter.",
+    supported_auth_types: ["none"],
+    docs_url: "https://docs.quiver.ai/developers",
+    capabilities: [
+      {
+        id: "quiver:create",
+        name: "Create and change vector graphics",
+        description: "Draw, redraw, trace and animate SVG artwork. Billed per Quiver credit consumed.",
+        access: "write"
+      },
+      {
+        id: "quiver:read",
+        name: "Read models",
+        description: "List the available drawing models and their per-call credit cost. Free.",
+        access: "read"
+      }
+    ],
+    beta: true,
+    // No `installable` on purpose: quiver is a seed integration
+    // (integration-definitions.json), so the seed catalog already makes it
+    // picker-visible. This entry exists to carry the `premium` descriptor that
+    // `isPremiumDefinition` reads — which arms the per-org opt-in gate, the
+    // priced acknowledgement modal and the admin pricing tab. Same reasoning as
+    // social-scraping above.
+    premium: {
+      pricing: "usage",
+      note: "Billed per Quiver credit consumed. Listing models is free; drawing, editing, tracing and animating each debit credits.",
+      meters: [
+        { event_type: "svg_credits", unit: "credit" },
+        { event_type: "svg_operation", unit: "operation" }
+      ]
+    }
+  },
+  {
+    // theSVG (thesvg.org) — 6,500+ REAL brand marks as SVG, so an agent building
+    // a page can use the actual Stripe/Slack/AWS logo instead of asking a
+    // drawing model for one. That distinction is the whole point of the
+    // integration: an AI-generated "Stripe logo" is a plausible fake, wrong in
+    // the way a customer notices and a trademark owner minds. Original artwork
+    // is Quiver's job; existing marks are this one's.
+    //
+    // WHY A LOCAL STDIO MCP AND NOT THE DIRECT-HTTP LANE. thesvg.org is a
+    // STATIC SITE — its own CLI says so in as many words ("there is no dynamic
+    // API"). The only two endpoints are `/api/registry.json`, the entire
+    // 2.97 MB / 6,523-entry manifest, and `/icons/{slug}/{variant}.svg`. Search
+    // is client-side filtering over that manifest, which the Direct-HTTP broker
+    // cannot do: it forwards the vendor's whole response body to the agent, so
+    // a `search_icons` descriptor would put 2.97 MB of registry into the
+    // agent's context on every call. The vendor's own MCP server bundles the
+    // registry and searches it in-process, which is precisely the shape the
+    // missing API leaves you needing.
+    //
+    // WHY THE VERSION IS PINNED and AWS's is `@latest`: this server's registry
+    // is baked in at BUILD time, so the pin is what decides which icons exist
+    // AND what markup lands on a customer's published page. Bumping it is a
+    // deliberate act that also refreshes the icon set — not a silent
+    // third-party update to artwork we are about to publish under a customer's
+    // domain.
+    //
+    // No credential anywhere: the registry and the jsDelivr CDN the server
+    // fetches SVG from are both public, so `auth_types: ['none']` is the honest
+    // classification rather than the ENG-8440 kind of lie Hard Rule 17 warns
+    // about — there genuinely is no key to enter and the install IS live
+    // immediately.
+    id: "thesvg",
+    name: "theSVG",
+    category: "media",
+    description: "Brand logos and icons as real SVG \u2014 search 6,500+ marks by name and pull the exact artwork, in mono, colour, light, dark or wordmark variants",
+    supported_auth_types: ["none"],
+    docs_url: "https://thesvg.org",
+    capabilities: [
+      {
+        id: "thesvg:read",
+        name: "Find and fetch brand icons",
+        description: "Search the icon library, list an icon's variants and categories, and fetch its SVG markup or CDN URL",
+        access: "read"
+      }
+    ],
+    installable: { category: "Media", authTypes: ["none"] },
+    beta: true,
+    // ENG-5815 data-driven path — no buildMcpJson edit, same as AWS.
+    nativeMcp: {
+      command: "npx",
+      args: ["-y", "@thesvg/mcp-server@0.8.2"],
+      env: {
+        PATH: "{{process_env.PATH}}",
+        HOME: "{{process_env.HOME}}"
+      }
+    }
+  },
   {
     id: "qmd",
     name: "QMD Memory Search",
@@ -36161,6 +36291,10 @@ var NOTICE_KIND_AUDIENCE = {
   // "Your `<verb>` approval request (`<uuid>`) EXPIRED at …" — in the report,
   // uuid and all.
   approval_expired: "agent",
+  // ENG-11334: canvas.publish_public approved / denied / approved-but-not-applied.
+  // Second-person instructions to the agent ("Tell the user...", "do not
+  // republish"); the user learns the outcome from the agent, not this row.
+  canvas_public_approval_resolved: "agent",
   // A routine fired; the agent picks the work up.
   routine_firing_result: "agent",
   // Live-advisor wake: "Call `live_read` with escalation_id …" — a literal tool
@@ -38897,7 +39031,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "approval-unified-authority",
-    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict and log approval_authority_would_reject (ingress, verb, org, reason) for every tap it would refuse, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
+    description: "One authority check for every approval ingress (ENG-11207, ADR-0124 Phase 0b): canDecide() runs inside tryDispatchApprovalCore for console, Slack (channel, alerts, Socket Mode, which also carries Telegram) and Direct Chat taps alike. off = not computed. shadow = compute the verdict, including the verb's declared approver boundary (ENG-11337), and log approval_authority_would_reject (ingress, verb, org, reason, boundary) for every tap it would refuse and approval_authority_would_admit (ingress, verb, org, basis, boundary) for every tap it would admit, then decide exactly as today. enforce = reserved for the per-(org, verb) allowlist slice; until that ships it behaves as shadow. Evaluated per-org. Ships dark.",
     flagType: "enum",
     allowedValues: ["off", "shadow", "enforce"],
     // Safe/default value is `off` (no computation, no extra reads on the tap path). A flag-DB read