@aifabrix/builder 2.52.0 → 2.52.1

package/templates/applications/miso-controller/application.yaml

@@ -4,8 +4,7 @@ app:
   displayName: 'Miso Controller'
   description: 'Miso is the AI Fabrix in-tenant controller and portal layer for securely operating enterprise AI apps inside a customer’s Azure tenant. It provides Entra ID SSO, RBAC, audit logs, environment/app configuration via schemas, and safe secret handling via Key Vault references—ensuring governance, traceability, and predictable UX across portal, SDK, and CLI.'
   type: webapp
-  version: '2.0.20'
-
+  version: '2.0.29'
 # Image Configuration
 # Set tag to match your build (e.g. aifabrix build miso-controller -t 1.0.0 then tag: 1.0.0)
 # Registry is required so the controller can pull the image (avoids "docker: not found" on the controller host).
@@ -81,7 +80,7 @@ configuration:
   # Operations & Debugging
   # -------------------------------------------------------------------------
   - name: LOG_LEVEL
-    category: General
+    category: Operations & Debugging
     portalInput:
       field: select
       label: 'Log Level'
@@ -92,7 +91,7 @@ configuration:
         - error
 
   - name: ENABLE_API_DOCS
-    category: General
+    category: Operations & Debugging
     portalInput:
       field: select
       label: 'Enable API Documentation (Swagger/ReDoc)'
@@ -101,7 +100,7 @@ configuration:
         - 'false'
 
   - name: FAST_STARTUP
-    category: General
+    category: Operations & Debugging
     portalInput:
       field: select
       label: 'Fast Startup (skip non-critical init)'
@@ -110,7 +109,7 @@ configuration:
         - 'false'
 
   - name: LOG_TO_FILE
-    category: General
+    category: Operations & Debugging
     portalInput:
       field: select
       label: 'Log to File'
@@ -122,7 +121,7 @@ configuration:
   # Keycloak Events (feature flag)
   # -------------------------------------------------------------------------
   - name: KEYCLOAK_EVENTS_ENABLED
-    category: General
+    category: Keycloak Events
     portalInput:
       field: select
       label: 'Keycloak Events (sync users/groups)'
@@ -130,18 +129,33 @@ configuration:
         - 'true'
         - 'false'
 
+  # -------------------------------------------------------------------------
+  # Identity — local user password / invitation
+  # -------------------------------------------------------------------------
+  - name: IDENTITY_LOCAL_PASSWORD_MODE
+    category: Identity
+    portalInput:
+      field: select
+      label: 'Password setup for new local users'
+      placeholder: 'Choose how new users set their password'
+      options:
+        - label: 'Send invitation email (user sets their own password)'
+          value: email
+        - label: 'Show a one-time temporary password to the admin'
+          value: admin-reveal
+
   # -------------------------------------------------------------------------
   # Rate Limiting (tune for environment)
   # -------------------------------------------------------------------------
   - name: RATE_LIMIT_WINDOW_MS
-    category: General
+    category: Rate Limiting
     portalInput:
       field: text
       label: 'Rate Limit Window (milliseconds)'
       placeholder: '900000'
 
   - name: RATE_LIMIT_MAX
-    category: General
+    category: Rate Limiting
     portalInput:
       field: text
       label: 'Rate Limit Max Requests per Window'

package/templates/applications/miso-controller/env.template

@@ -74,8 +74,8 @@ ENABLE_API_DOCS=true
 # Rate Limiting Configuration (for local development)
 # Set DISABLE_RATE_LIMIT=true to disable rate limiting entirely (local development only)
 DISABLE_RATE_LIMIT=true
-# RATE_LIMIT_WINDOW_MS=600000  # 10 minutes in milliseconds (default: 600000)
-# RATE_LIMIT_MAX=100           # Max requests per window (default: 100)
+RATE_LIMIT_WINDOW_MS=600000
+RATE_LIMIT_MAX=100
 
 # Package Version (auto-set by npm/pnpm, optional override)
 # npm_package_version=1.0.0
@@ -142,6 +142,11 @@ KEYCLOAK_VERIFY_AUDIENCE=false
 KEYCLOAK_TOKEN_TIMEOUT=5000
 KEYCLOAK_DEFAULT_PASSWORD=kv://keycloak-default-passwordKeyVault
 
+# Password setup for new local users (plan 209.0)
+# email = send invitation email so the user sets their own password (default)
+# admin-reveal = show a one-time temporary password to the admin (labs / no mail)
+IDENTITY_LOCAL_PASSWORD_MODE=admin-reveal
+
 # Keycloak Events Configuration
 KEYCLOAK_EVENTS_ENABLED=true
 KEYCLOAK_EVENTS_VERIFY_SIGNATURE=true
@@ -317,6 +322,7 @@ MORI_PASSWORD=kv://mori-controller-basic-passwordKeyVault
 # LOG_FILE_PATH=/mnt/data/logs via deploy JSON and ensure the directory exists.
 
 LOG_TO_FILE=true
+LOG_LEVEL=info
 LOG_FILE_PATH=./logs
 
 # =============================================================================

package/templates/channels/README.md

@@ -1,6 +1,6 @@
 # Channel integration templates
 
-Published copies of communication external-system manifests for `aifabrix channel scaffold <target>`.
+Published copies of communication external-system manifests for `aifabrix channel scaffold <target>` (also used automatically by `aifabrix channel add`).
 
 ## SSOT
 
@@ -13,6 +13,16 @@ Published copies of communication external-system manifests for `aifabrix channe
 
 Do **not** hardcode manifests in `lib/channels/*.js`.
 
+## Brand icons (`brand/`)
+
+Default AI Fabrix app icons for channel packages (from product icon pack).
+
+| File / folder | Use |
+| --- | --- |
+| `color-192.png` | Microsoft Copilot / Teams `color.png` (192×192) |
+| `outline-32.png` | Microsoft Copilot / Teams `outline.png` (32×32 mono) |
+| `light/`, `dark/`, `mono-white/` | Size variants 32–512 for overrides / other surfaces |
+
 ## Slack App manifest (install)
 
 `manifest.template.json.hbs` and `install.template.md.hbs` are for `aifabrix channel add slack` (Slack developer portal), separate from the external-system integration tree above.

package/templates/channels/chatgpt/install.template.md.hbs

@@ -54,7 +54,7 @@ Before ChatGPT can connect successfully, the MCP deployment must meet all of the
 
 If this development endpoint is deliberately anonymous, select **No authentication** instead and declare `noauth` on the applicable tools. Do not describe the app as “OAuth or API key”; the selected mechanism must match the behavior advertised by the MCP server.
 
-## Expected Runtime Layer B tools
+## Expected governed tools
 
 ChatGPT should discover the following tools from the live MCP server during **Scan tools**:
 
@@ -62,12 +62,14 @@ ChatGPT should discover the following tools from the live MCP server during **Sc
 - `{{this}}`
 {{/each}}
 
-The live server response is authoritative. This list is an expected deployment contract, not a substitute for MCP tool discovery.
+{{#if installReady}}Install ready: yes{{else}}Install ready: no{{#if discoveryBlocker}} ({{discoveryBlocker}}){{/if}}{{/if}}
+
+The live server response is authoritative. This list is an expected deployment contract from External AI Discovery, not a substitute for MCP tool discovery.
 
 ## Runtime and Role Assistant boundaries
 
 - Runtime resolves assistants dynamically for the current user from `{{{assistantCatalogUrl}}}`.
-- ChatGPT's top-level tool surface remains limited to the Runtime Layer B tools listed above.
+- ChatGPT's top-level tool surface remains limited to the governed tools listed above.
 - Evidence authoring remains an internal Business Transformation Assistant capability. It is reached through `ChatGPT → runtime-orchestration → Business Transformation Assistant → internal evidence capabilities` and is not exposed as a top-level ChatGPT tool.
 - One authenticated Runtime connection can support multiple Role Assistants, subject to the current user's authorization.
 
@@ -90,7 +92,7 @@ Then run the AI Fabrix probe:
 aifabrix channel add {{channelTarget}} --name "{{baseName}}" --probe
 ```
 
-The probe should validate Runtime through the first-party MCP gateway, including Layer B discovery and BTA Evidence-authoring reachability. A successful AI Fabrix probe does not replace ChatGPT's own **Scan tools**, OAuth, and workspace publication checks.
+The probe should validate Runtime through the first-party MCP gateway, including governed tool discovery and BTA Evidence-authoring reachability. A successful AI Fabrix probe does not replace ChatGPT's own **Scan tools**, OAuth, and workspace publication checks.
 
 Use `--force` only to regenerate artifacts and patch channel metadata. It does not rotate credentials.
 

package/templates/channels/chatgpt/integration/README.md

@@ -5,11 +5,10 @@ Generated by `aifabrix channel scaffold chatgpt`.
 Recommended flow:
 
 ```bash
-aifabrix upload chatgpt --force
 aifabrix channel add chatgpt --name "Your Assistant" --probe
 ```
 
-The `channel add` step generates `dist/channels/chatgpt/channel-chatgpt.json` and
-`INSTALL.md`. Those files are deployment references for workspace admins: ChatGPT
-connects to the remote Runtime MCP URL (OAuth) and discovers tools; it does not
-install the JSON as a plugin archive.
+`channel add` scaffolds (if needed), uploads when missing (always with `--force`), then
+generates `dist/channels/chatgpt/channel-chatgpt.json` and `INSTALL.md`. Those files are
+deployment references for workspace admins: ChatGPT connects to the remote Runtime MCP URL
+(OAuth) and discovers tools; it does not install the JSON as a plugin archive.

package/templates/channels/chatgpt/integration/chatgpt-system.json

@@ -6,22 +6,7 @@
   "systemKind": "communication",
   "enabled": true,
   "authentication": {
-    "authType": "credential",
-    "credential": {
-      "credentialKey": "chatgpt-channel",
-      "displayName": "ChatGPT custom MCP app channel",
-      "method": "apikey",
-      "writeOnce": true,
-      "variables": {
-        "baseUrl": "https://api.openai.com/v1"
-      },
-      "security": {
-        "apiKey": "kv://chatgpt/apiKey"
-      },
-      "formFields": [
-        { "name": "apiKey", "required": true }
-      ]
-    }
+    "authType": "system"
   },
   "configuration": [],
   "dataSources": [],

package/templates/channels/microsoft-copilot/ai-plugin.template.json.hbs

@@ -1,28 +1,22 @@
 {
   "$schema": "https://developer.microsoft.com/json-schemas/copilot/plugin/v2.4/schema.json",
   "schema_version": "v2.4",
-  "name_for_human": "{{appName}}",
-  "name_for_model": "aifabrix_runtime_orchestration",
-  "description_for_human": "{{appDescription}}",
-  "description_for_model": "Runtime orchestration tools for governed enterprise work.",
+  "name_for_human": "{{pluginNameForHuman}}",
+  "description_for_human": "{{pluginDescriptionForHuman}}",
+  "description_for_model": "Governed enterprise work tools for Role Assistants. Prefer discovery tool names only; resolve Role Assistants dynamically for the signed-in user.",
+  "namespace": "{{pluginNamespace}}",
+  "privacy_policy_url": "{{{dataplaneBaseUrl}}}/privacy",
+  "legal_info_url": "{{{dataplaneBaseUrl}}}/terms",
   "runtimes": [
     {
       "type": "RemoteMCPServer",
       "spec": {
-        "url": "{{mcpUrl}}"
+        "url": "{{{mcpUrl}}}"
       },
       "auth": {
-        "type": "oauth",
-        "scopes": {{{scopesJson}}}
+        "type": "OAuthPluginVault",
+        "reference_id": "{{oauthPluginVaultReferenceId}}"
       }
     }
-  ],
-  "mcp_tool_description": {
-    "mode": "dynamic",
-    "layerBToolNames": [
-{{#each layerBToolNames}}
-      "{{this}}"{{#unless @last}},{{/unless}}
-{{/each}}
-    ]
-  }
+  ]
 }

package/templates/channels/microsoft-copilot/declarative-agent.template.json.hbs

@@ -1,8 +1,10 @@
 {
+  "$schema": "https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.4/schema.json",
+  "version": "v1.4",
   "id": "{{packageAppId}}-agent",
-  "name": "{{appName}}",
-  "description": "{{appDescription}}",
-  "instructions": "Use Runtime Layer B tools only. Resolve Role Assistants dynamically and keep business reasoning inside authorized Role Assistant boundaries.",
+  "name": "{{fullName}}",
+  "description": "{{fullDescription}}",
+  "instructions": "Use governed enterprise work tools only. Resolve Role Assistants dynamically and keep business reasoning inside authorized Role Assistant boundaries.",
   "conversation_starters": [
     {
       "title": "Show my role assistants",

package/templates/channels/microsoft-copilot/entra-sso-registration.template.md.hbs

@@ -0,0 +1,27 @@
+## Microsoft Entra SSO registration (Teams Developer Portal)
+
+Direct URL:
+
+{{{entraSsoRegistrationUrl}}}
+
+Open **Tools → Microsoft Entra SSO client ID registration → Register client ID** (or New).
+
+### Values to paste into the form
+
+| Field | Value |
+| --- | --- |
+| Registration name | `{{appName}}` |
+| Base URL | {{#if entraSsoBaseUrl}}`{{{entraSsoBaseUrl}}}`{{else}}*(missing — dataplane URL not resolved)*{{/if}} |
+| Restrict usage by organization | My organization only (DEV) |
+| Restrict usage by Teams app | Any Teams app (until the Teams app id is stable) |
+| Client (application) ID | {{#if entraSsoClientId}}`{{entraSsoClientId}}`{{else}}*(missing — Entra SSO enterprise app (client) id from controller Keycloak status `entraIdentityProvider.enterpriseAppId`; complete Entra onboarding if empty)*{{/if}} |
+| Scope | {{#if entraSsoScope}}`{{entraSsoScope}}`{{else}}*(missing — set Runtime MCP delegated scopes on Trust source `microsoft-entra-id` `allowedScopes`; not openid/profile alone)*{{/if}} |
+
+### Related (for your records)
+
+{{#if mcpUrl}}- **Remote MCP URL (package):** `{{{mcpUrl}}}`{{/if}}
+{{#if entraIssuer}}- **Entra issuer (Trust source):** `{{{entraIssuer}}}`{{/if}}
+{{#if entraTenantId}}- **Tenant id:** `{{entraTenantId}}`{{/if}}
+{{#if entraEnterpriseAppId}}- **Enterprise app id (Keycloak):** `{{entraEnterpriseAppId}}`{{/if}}
+
+After Save, copy the **Microsoft Entra SSO registration ID** (auth config id). That value is `--oauth-plugin-vault-reference-id`.

package/templates/channels/microsoft-copilot/install.template.md.hbs

@@ -2,9 +2,11 @@
 
 {{appDescription}}
 
-Environment: **{{environment}}** · Credential key: `{{credentialKey}}`
+Environment: **{{environment}}**
 
-This channel output is a Microsoft 365 Copilot app package:
+This channel uses **Microsoft Entra SSO** (trustedIssuer). Users already signed into
+Microsoft 365 do **not** complete a separate AI Fabrix sign-in. Admin consent may still
+apply for the Runtime MCP delegated scope.
 
 ```text
 dist/channels/microsoft-copilot/source/manifest.json
@@ -13,42 +15,59 @@ dist/channels/microsoft-copilot/source/ai-plugin.json
 dist/channels/microsoft-copilot/build/appPackage.{{environment}}.zip
 ```
 
-## Microsoft admin workflow (manual)
+## Install in Microsoft Teams
 
-1. Sign in to [Microsoft 365 admin](https://admin.cloud.microsoft.com/) or Copilot Studio as a tenant admin.
-2. Upload or sideload `appPackage.{{environment}}.zip` to your organization app catalog.
-3. Review the declarative agent + Remote MCP plugin metadata and approve tenant distribution.
-4. Configure workspace authentication and consent according to your Entra/OAuth policy.
-5. Store credential references in AI Fabrix authentication settings: [Authentication settings]({{credentialPortalUrl}})
-6. Assign the app to users/groups and complete first-user sign-in.
+1. Open Microsoft Teams using your target Microsoft 365 account.
+2. Select **Apps → Manage your apps**.
+3. Select **Upload an app → Upload a custom app**.
+4. Upload `appPackage.{{environment}}.zip`.
+5. Review the requested permissions and select **Add**.
+6. Open **{{appName}}** from your installed apps.
+7. If prompted, complete **Entra / admin consent** for the Runtime MCP resource (not an AI Fabrix OAuth client login).
+
+Upload only the ZIP package. Do not upload individual manifest files or `channel-microsoft-copilot.json`.
+
+If **Upload a custom app** is unavailable, a Teams administrator must enable custom app uploads for your account in the Teams admin center or deploy the package centrally.
+
+Do **not** configure AI Fabrix OAuth client secrets in Connected Systems → Authentication for this flow. Entra SSO uses the Teams OAuthPluginVault auth-config id.
 
 ## Runtime connection contract
 
 - **Runtime system key:** `{{runtimeSystemKey}}`
-- **Remote MCP URL:** `{{mcpUrl}}`
+- **Remote MCP URL:** `{{{mcpUrl}}}`
 - **Transport:** `{{runtimeTransport}}`
-- **Auth mode:** `{{runtimeAuthMode}}`
-- **Layer B tools expected:**
+- **Auth mode:** `{{runtimeAuthMode}}` (Entra SSO / trustedIssuer; controller exchanges the Microsoft user token)
+- **Plugin auth:** `OAuthPluginVault` · Teams auth-config reference id `{{oauthPluginVaultReferenceId}}`
+{{#if entraIssuer}}- **Entra issuer (from Trust source):** `{{{entraIssuer}}}`{{/if}}
+- **Delegated scopes:** {{#each scopes}}`{{this}}` {{else}}*(missing — package not install-ready)*{{/each}}
+- **Install ready:** {{#if installReady}}yes{{else}}no{{#if discoveryBlocker}} ({{discoveryBlocker}}){{/if}}{{/if}}
+- **Governed tools expected:**
 {{#each layerBToolNames}}
   - `{{this}}`
 {{/each}}
 
+{{> entraSsoRegistration}}
+
+## Package links
+
+- README / install guide: `INSTALL.md`
+- Package ZIP: `build/appPackage.{{environment}}.zip`
 ## Assistant catalog
 
-Runtime lists **assistants** available to each user from:
+Runtime lists the assistants available to the signed-in user from:
 
-{{assistantCatalogUrl}}
+{{{assistantCatalogUrl}}}
 
 ## Probe truthfulness
 
-- `builderValidated` means package files, ZIP, hashes, and secret checks passed.
-- `runtimeValidated` means Runtime MCP is reachable and tool boundary checks pass.
-- `requiresMicrosoftAdmin` remains true until tenant upload/approval/assignment is complete.
+- `builderValidated` means package files, ZIP structure, hashes, and secret checks passed.
+- `runtimeValidated` means Runtime MCP is reachable and its tool boundary checks passed.
+- `requiresMicrosoftAdmin` means Microsoft-side installation or approval remains incomplete. A user may install the package directly when their Teams custom-app policy permits it; otherwise, Teams administrator action is required.
 
-## Validate after admin setup
+## Validate after Teams installation
 
 ```bash
-aifabrix channel add {{channelTarget}} --name "{{baseName}}" --probe
+aifabrix channel add {{channelTarget}} --name "{{baseName}}" --oauth-plugin-vault-reference-id "{{oauthPluginVaultReferenceId}}" --probe
 ```
 
-`--force` regenerates artifacts but does not rotate credentials.
+`--force` regenerates the package artifacts. microsoft-copilot does not create Fabrix oauth2 channel credentials for Entra SSO.

package/templates/channels/microsoft-copilot/integration/README.md

@@ -5,9 +5,8 @@ Generated by `aifabrix channel scaffold microsoft-copilot`.
 Recommended flow:
 
 ```bash
-aifabrix upload microsoft-copilot --force
 aifabrix channel add microsoft-copilot --name "Your Assistant" --probe
 ```
 
-`channel add` generates package artifacts under
-`dist/channels/microsoft-copilot/` for Microsoft 365 tenant admins.
+`channel add` scaffolds (if needed), uploads when missing (always with `--force`), then
+generates package artifacts under `dist/channels/microsoft-copilot/` for Microsoft 365 tenant admins.

package/templates/channels/microsoft-copilot/integration/microsoft-copilot-system.json

@@ -6,28 +6,7 @@
   "systemKind": "communication",
   "enabled": true,
   "authentication": {
-    "authType": "credential",
-    "credential": {
-      "credentialKey": "microsoft-copilot-channel",
-      "displayName": "Microsoft Copilot package channel",
-      "method": "oauth2",
-      "writeOnce": true,
-      "variables": {
-        "baseUrl": "https://login.microsoftonline.com",
-        "authorizationUrl": "https://login.microsoftonline.com/common/oauth2/v2.0/authorize",
-        "tokenUrl": "https://login.microsoftonline.com/common/oauth2/v2.0/token",
-        "grantType": "authorization_code",
-        "scope": "openid profile offline_access"
-      },
-      "security": {
-        "clientId": "kv://microsoft-copilot/clientId",
-        "clientSecret": "kv://microsoft-copilot/clientSecret"
-      },
-      "formFields": [
-        { "name": "clientId", "required": true },
-        { "name": "clientSecret", "required": true }
-      ]
-    }
+    "authType": "system"
   },
   "configuration": [],
   "dataSources": [],

package/templates/channels/microsoft-copilot/manifest.template.json.hbs

@@ -4,18 +4,18 @@
   "version": "{{packageVersion}}",
   "id": "{{packageAppId}}",
   "name": {
-    "short": "{{baseName}}",
-    "full": "{{appName}}"
+    "short": "{{shortName}}",
+    "full": "{{fullName}}"
   },
   "description": {
-    "short": "{{appDescription}}",
-    "full": "{{appDescription}}"
+    "short": "{{shortDescription}}",
+    "full": "{{fullDescription}}"
   },
   "developer": {
     "name": "AI Fabrix",
-    "websiteUrl": "{{dataplaneBaseUrl}}",
-    "privacyUrl": "{{dataplaneBaseUrl}}/privacy",
-    "termsOfUseUrl": "{{dataplaneBaseUrl}}/terms"
+    "websiteUrl": "{{{dataplaneBaseUrl}}}",
+    "privacyUrl": "{{{dataplaneBaseUrl}}}/privacy",
+    "termsOfUseUrl": "{{{dataplaneBaseUrl}}}/terms"
   },
   "icons": {
     "color": "color.png",

package/templates/channels/microsoft-copilot/oauth-plugin-vault-required.template.md.hbs

@@ -0,0 +1,11 @@
+microsoft-copilot packaging requires `--oauth-plugin-vault-reference-id` with the Teams Entra SSO auth-config id.
+
+Register Entra SSO in the Teams Developer Portal **before** packaging (no ZIP needed first), paste the values below, Save, then re-run with the registration id.
+
+{{> entraSsoRegistration}}
+
+Then:
+
+```bash
+aifabrix channel add microsoft-copilot --name "{{baseName}}" --oauth-plugin-vault-reference-id "<Teams-Entra-SSO-registration-id>"
+```

package/templates/channels/slack/integration/README.md

@@ -30,9 +30,7 @@ Registered at `/api/v1/external/systems/slack/`:
 ## Workflow
 
 ```bash
-aifabrix channel scaffold slack   # or use this folder as SSOT
-aifabrix upload slack --force
-aifabrix channel add slack --name "Your Assistant"
+aifabrix channel add slack --name "Your Assistant" --probe
 ```
 
-Publish template changes: `make sync-json` in dataplane → `aifabrix-builder/templates/channels/slack/integration/`.
+Optional low-level: `channel scaffold` / `upload`. Publish template changes: `make sync-json` in dataplane → `aifabrix-builder/templates/channels/slack/integration/`.

package/templates/channels/teams-bot/install.template.md.hbs

@@ -44,6 +44,10 @@ Users message the bot with:
 
 Review cards use **Approve**, **Reject**, and **Edit metadata** actions on the **Bot messages** endpoint. Proactive review notifications use the **Notifications** URL.
 
+## Authentication
+
+Teams bot authentication uses a **Microsoft token**. AI Fabrix controller performs token exchange — generated package and INSTALL files carry public connection specs only (no secrets).
+
 ## Assistant catalog
 
 Runtime lists **assistants** available to each user from:

package/templates/channels/teams-bot/integration/README.md

@@ -8,11 +8,9 @@ SSOT for Teams Bot Framework communication channel — **Role Assistants** and *
 - **Document approval:** `documents`, `document`, `approve`, `help` bot commands; review Adaptive Cards; proactive `/notifications`
 
 ```bash
-cd aifabrix-dataplane
-aifabrix validate teams-bot
-aifabrix upload teams-bot --probe
-aifabrix deploy teams-bot
-aifabrix channel add teams-bot --name "Your Assistant"
+aifabrix channel add teams-bot --name "Your Assistant" --probe
 ```
 
+Optional low-level (dataplane fixture tree): `validate` / `upload` / `deploy` before add.
+
 Authentication: oidc — prefilled discovery settings; operators add Microsoft App ID + client secret on Connected Systems → Authentication.

package/templates/channels/web-embed/integration/web-embed-system.json

@@ -6,22 +6,7 @@
   "systemKind": "communication",
   "enabled": true,
   "authentication": {
-    "authType": "credential",
-    "credential": {
-      "credentialKey": "web-embed-channel",
-      "displayName": "Web embed assistant channel",
-      "method": "apikey",
-      "writeOnce": true,
-      "variables": {
-        "baseUrl": "https://embed.aifabrix.dev"
-      },
-      "security": {
-        "apiKey": "kv://web-embed/apiKey"
-      },
-      "formFields": [
-        { "name": "apiKey", "required": true }
-      ]
-    }
+    "authType": "system"
   },
   "configuration": [],
   "dataSources": [],