@aifabrix/builder 2.51.1 → 2.52.1

package/templates/applications/dataplane/env.template

@@ -44,7 +44,7 @@ API_KEY_BYPASS_ROLES=full-access
 
 # API Configuration
 API_V1_STR=/api/v1
-VERSION=2.0.15
+VERSION=2.0.26
 # Minimum supported aifabrix-builder CLI semver (advertised on /health and /api/v1/health; empty = no gate)
 # MIN_BUILDER_CLI_VERSION=2.45.0
 MIN_BUILDER_CLI_VERSION=2.45.5
@@ -155,11 +155,10 @@ MISO_PIPELINE_ENV_KEY=
 
 # LLM: chat/embed route through governed enterprise-llm only. Provider credentials
 # live on LLM provider external systems + dataplane secret store (not product .env).
-# When ≥2 LLM providers are published under enterprise-llm, set selectorKey
-# (system key), e.g. openai | azure-openai | ollama. Ignored when only one.
-# Prefer portal Configuration category LLM after deploy; this env is the resolve target.
-# Default LLM provider systemKey when ≥2 LLM providers are published under
-# enterprise-llm (fail-closed if empty). Portal category LLM can override.
+# Deploy-time default provider (systemKey) when Environment Settings ai.llmProvider
+# is empty. Operators can override in Environment Settings without redeploying.
+# When ≥2 LLM providers are published and both settings and this env are empty,
+# resolve fails closed. Ignored when only one provider is published.
 # Lab default: openai (catalog also ships azure-openai).
 ENTERPRISE_LLM_DEFAULT_SELECTOR=openai
 
@@ -180,6 +179,8 @@ ABAC_EXPLAIN_MODE_ENABLED=false
 ABAC_PERFORMANCE_THRESHOLD_MS=1000
 
 # RBAC Audit Configuration
+# When true, audit denials (rbac.permission.check.failure) and decision traces.
+# Successful allow checks are not audited (no forensic value; floods every request).
 RBAC_AUDIT_ENABLED=true
 # RBAC audit detail: summary | detailed | explain
 RBAC_AUDIT_DETAIL_LEVEL=summary
@@ -284,7 +285,7 @@ VALIDATION_AUTO_ISSUE_INTEGRATION_CERTIFICATE=true
 CIP_EXECUTION_MAX_RESPONSE_SIZE_MB=100.0
 CIP_EXECUTION_MAX_RECORDS=100000
 CIP_EXECUTION_OPERATION_TIMEOUT=300.0
-CIP_EXECUTION_HTTP_TIMEOUT=30.0
+CIP_EXECUTION_HTTP_TIMEOUT=120.0
 CIP_EXECUTION_MAX_RETRIES=3
 CIP_EXECUTION_RETRY_BACKOFF_FACTOR=2.0
 CIP_EXECUTION_RETRY_INITIAL_DELAY=1.0

package/templates/applications/dataplane/rbac.yaml

@@ -5,47 +5,47 @@
 # MisoClient validates environment access automatically based on user/application permissions.
 
 roles:
-  - name: "AI Fabrix Platform Admin"
+  - name: "Platform Admin"
     value: "aifabrix-platform-admin"
     description: "Full platform infrastructure management and enterprise controller access"
     groups: ["AI-Fabrix-Platform-Admins"]
 
-  - name: "AI Fabrix Security Admin"
+  - name: "Security Admin"
     value: "aifabrix-security-admin"
     description: "Security and compliance management for enterprise controller"
     groups: ["AI-Fabrix-Security-Admins"]
 
-  - name: "AI Fabrix Deployment Admin"
+  - name: "Deployment Admin"
     value: "aifabrix-deployment-admin"
     description: "Application deployment orchestration and environment management"
     groups: ["AI-Fabrix-Deployment-Admins"]
 
-  - name: "AI Fabrix Compliance Admin"
+  - name: "Compliance Admin"
     value: "aifabrix-compliance-admin"
     description: "ISO 27001 compliance monitoring and audit management"
     groups: ["AI-Fabrix-Compliance-Admins"]
 
-  - name: "AI Fabrix Developer"
+  - name: "Developer"
     value: "aifabrix-developer"
     description: "Developer access to deploy applications via CI pipelines"
     groups: ["AI-Fabrix-Developers"]
 
-  - name: "AI Fabrix Business Transformation"
-    value: "aifabrix-business-transformation"
+  - name: "Business Transformation"
+    value: "business-transformation"
     description: "Built-in assistant: business intention → governed Connected Systems via Runtime and builder-api"
     groups: ["AI-Fabrix-Business-Transformation"]
 
-  - name: "AI Fabrix Observer"
+  - name: "Observer"
     value: "aifabrix-observer"
     description: "Read-only access to monitoring, logs, and compliance reports"
     groups: ["AI-Fabrix-Observers"]
 
-  - name: "AI Fabrix AI Trust Operator"
+  - name: "AI Trust Operator"
     value: "aifabrix-ai-trust-operator"
     description: "Run AI Trust access evaluation and explain visibility for governed users"
     groups: ["AI-Fabrix-AI-Trust-Operators"]
 
-  - name: "AI Fabrix External System Discoverer"
+  - name: "External System Discoverer"
     value: "aifabrix-external-system-discoverer"
     description: "Discover business context for external systems via REST and MCP"
     groups: ["AI-Fabrix-External-System-Discoverers"]

package/templates/applications/keycloak/application.yaml

@@ -10,8 +10,8 @@ app:
 image:
   name: aifabrix/keycloak
   tag: 'latest'
-  registry: aifabrixdevacr.azurecr.io
-  registryMode: acr
+  registry: aifabrixacr.azurecr.io
+  registryMode: external
 
 # Port Configuration (base for host; host port = 8082 + developer_id*100 from ~/.aifabrix/config.yaml)
 port: 8082

package/templates/applications/keycloak/env.template

@@ -9,11 +9,14 @@
 KC_BOOTSTRAP_ADMIN_USERNAME=admin
 KC_BOOTSTRAP_ADMIN_PASSWORD=kv://keycloak-admin-passwordKeyVault
 KC_HOSTNAME_STRICT=false
-KC_HTTP_ENABLED=${HTTP_ENABLED}
+# Follows tlsEnabled in ~/.aifabrix/config.yaml (same as ${TLS_ENABLED}).
+# Traefik/edge HTTPS on → true (proxy forwards HTTP to Keycloak :8080).
+# Single container without HTTPS (tlsEnabled false) → false.
+KC_HTTP_ENABLED=${TLS_ENABLED}
 # When Traefik + frontDoorRouting.enabled are on, same vdir as url://public. If the front door is off, env generation
 # rewrites url://vdir-public to "/" before expansion (empty path is invalid — Keycloak 26 SRCFG00040).
 # Docker-only templates may use url://vdir-internal instead.
-KC_HTTP_RELATIVE_PATH=url://vdir-public
+KC_HTTP_RELATIVE_PATH=/auth
 
 # =============================================================================
 # HOSTNAME / ISSUER (Docker vs localhost)

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

@@ -4,16 +4,15 @@ 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.10'
-
+  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).
 image:
   name: aifabrix/miso-controller
   tag: latest
-  registry: aifabrixdevacr.azurecr.io
-  registryMode: acr
+  registry: aifabrixacr.azurecr.io
+  registryMode: external
 
 # Port Configuration (container port; host port = 3000 + developer_id*100 from ~/.aifabrix/config.yaml)
 port: 3000
@@ -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

@@ -49,6 +49,10 @@ ONBOARDING_ADMIN_EMAIL=kv://miso-controller-admin-emailKeyVault
 # When true, supersedes ONBOARDING_CREATE_DEV_ENV for which extra environments are created
 ONBOARDING_FULL_PLATFORM=false
 
+# When true, run Azure env deploy for onboarding envs (SDK modules). Default false —
+# Marketplace already provisions infra; TA owns customer env deploy.
+ONBOARDING_CREATE_MISO_ENV=false
+
 # Set to true to create both miso and dev environments during onboarding
 # When false (default), only the miso environment is created (ignored when ONBOARDING_FULL_PLATFORM=true)
 ONBOARDING_CREATE_DEV_ENV=true
@@ -70,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
@@ -138,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
@@ -236,6 +245,14 @@ SKIP_DB_REDEPLOY=true
 # Bootstrap (SKIP_FIRST_TIME_SETUP=false) is separate from the activation wizard.
 DEPLOYMENT=database
 
+# Dev/test: open /tenant-activation on Platform Apps (last step). Default false.
+# Does not skip server-side TA — use only when env is already activated/deployed.
+TA_SKIP_TO_APP_DEPLOY=false
+
+# Dev/test: show TA Entra "Completing setup" countdown (120s cap). Default false.
+# Exposed to UI via GET /api/v1/tenant/status → showTaCountdown (restart controller after change).
+SHOW_TA_COUNT_DOWN=false
+
 # =============================================================================
 # SECURITY & ENCRYPTION
 # =============================================================================
@@ -287,9 +304,10 @@ ENTRA_GRAPH_DELEGATED_REDIRECT_URI=https://aifabrix-pro-mori-web-we.azurewebsite
 # =============================================================================
 # MORI SERVICE CONFIGURATION
 # =============================================================================
-
-# Shared pro Mori (Entra handoff + Graph callback). Prefer this over url://mori-controller-public
-# unless a local Mori app is registered and running for the developer.
+# Shared Mori (handoff poll + Entra callback). Local `url://mori-controller-public`
+# only works when a local Mori app is registered and running for this developer.
+# MORI_CALLBACK_API_KEY must be the same secret as Mori MORI_CONTROLLER_CALLBACK_API_KEY
+# (both resolve from kv://mori-callback-api-keyKeyVault — do not generate separate values).
 MORI_BASE_URL=https://aifabrix-pro-mori-web-we.azurewebsites.net
 MORI_AUTH_METHOD=kv://mori-controller-auth-methodKeyVault
 MORI_CALLBACK_API_KEY=kv://mori-callback-api-keyKeyVault
@@ -304,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

@@ -2,63 +2,103 @@
 
 {{appDescription}}
 
-Environment: **{{environment}}** · Credential key: `{{credentialKey}}`
-
-This output is connection and administration material (`channel-chatgpt.json` + `INSTALL.md`), not a plugin archive.
-
-## Workspace admin setup (manual)
-
-1. Sign in to your ChatGPT workspace as an admin and enable **Developer mode / custom MCP apps** if required by workspace policy.
-2. Create a custom MCP app and use the generated artifact from `dist/channels/chatgpt/channel-chatgpt.json` as the connection reference.
-3. Configure the remote MCP URL and transport from **Runtime connection** below.
-4. Complete authentication setup for your workspace policy. Store credential references in AI Fabrix: [Authentication settings]({{credentialPortalUrl}})
-5. Refresh tools in ChatGPT after configuration changes so ChatGPT reads the latest Runtime tool list.
-6. Publish the app to the workspace and configure workspace access controls (RBAC or equivalent).
+**Environment:** {{environment}}  
+**AI Fabrix credential reference:** `{{credentialKey}}`
+
+> This document and `dist/channels/chatgpt/channel-chatgpt.json` are deployment references for administrators. ChatGPT does not install the JSON file as a plugin archive. ChatGPT connects directly to the remote MCP endpoint and discovers the tools exposed by that server.
+
+## ChatGPT workspace setup
+
+1. Sign in to the ChatGPT web app as a workspace admin or owner.
+2. Enable Developer mode for custom MCP apps:
+   - **Business:** **Workspace settings → Apps → Create**, or **Settings → Apps → Advanced settings**.
+   - **Enterprise/Edu:** grant the appropriate Developer mode permission under **Workspace settings → Permissions & roles → Connected data**, then enable it under **Settings → Apps → Advanced settings**.
+3. Open **Settings → Apps → Create** (or the equivalent **Workspace settings → Apps → Create** entry).
+4. Enter the app name `{{appName}}` and the remote MCP URL shown under **Runtime connection** below.
+5. Select **OAuth** as the authentication mechanism. Do not configure a custom API key in ChatGPT; custom API-key authentication is not supported for a remote custom MCP app.
+6. Select **Scan tools**. If prompted, complete the OAuth authorization flow and wait for ChatGPT to finish scanning the Runtime tool list.
+7. Review the discovered tools and create the app as a draft.
+8. Test representative read and write workflows. Confirm that user authorization and action confirmations behave as expected.
+9. Publish the app to the workspace and configure its access and action controls. Only workspace admins or owners can publish it.
+10. After MCP tool names, schemas, annotations, or authentication metadata change, use **Refresh** in the app's action controls and review the changes before enabling them.
 
 ## Runtime connection
 
-Configure these values in the ChatGPT custom MCP app. Do not place secrets in generated files.
+Configure the following values in the ChatGPT custom MCP app. Never place access tokens, client secrets, or API keys in generated files.
 
+- **App name:** `{{appName}}`
 {{#if mcpUrl}}
-- **Remote MCP URL:** {{mcpUrl}}
+- **Remote MCP URL:** `{{{mcpUrl}}}`
 {{/if}}
-- **Runtime system key:** {{runtimeSystemKey}}
-- **Transport:** {{runtimeTransport}}
-- **Auth mode:** {{runtimeAuthMode}}
-- **Expected Layer B tools:**
+- **Runtime system key:** `{{runtimeSystemKey}}`
+- **Transport:** Streamable HTTP
+- **Authentication:** OAuth 2.1 authorization-code flow with PKCE (`S256`)
+- **AI Fabrix credential reference:** `{{credentialKey}}`
+- **AI Fabrix authentication settings:** [Open authentication settings]({{{credentialPortalUrl}}})
+
+The `{{credentialKey}}` value is an AI Fabrix credential reference. It is not a secret to paste into ChatGPT.
+
+## OAuth requirements
+
+Before ChatGPT can connect successfully, the MCP deployment must meet all of these requirements:
+
+- The MCP endpoint is reachable over public HTTPS with a publicly trusted TLS certificate chain.
+- The MCP server publishes OAuth protected-resource metadata, normally at `/.well-known/oauth-protected-resource`, or points to it in the `WWW-Authenticate` header returned with a `401 Unauthorized` response.
+- The protected-resource document identifies the canonical resource URL, authorization server, and supported scopes.
+- The authorization server publishes OAuth or OpenID Connect discovery metadata.
+- The authorization server supports the authorization-code flow and PKCE with `S256`.
+- The OAuth flow preserves the MCP `resource` parameter, and issued access tokens contain the expected audience and scopes.
+- The redirect URI shown by ChatGPT when the app is created is allowlisted in the authorization server.
+- The MCP server validates every access token's signature, issuer, audience, expiry, and scopes.
+- Each authenticated MCP tool declares an `oauth2` security scheme with the scopes it needs.
+
+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 governed tools
+
+ChatGPT should discover the following tools from the live MCP server during **Scan tools**:
+
 {{#each layerBToolNames}}
-  - `{{this}}`
+- `{{this}}`
 {{/each}}
 
-AI Fabrix `--probe` validates Runtime through the first-party MCP gateway
-(`/api/v1/mcp/servers/tools` and MCP docs for `{{runtimeSystemKey}}`), including
-Layer B discovery and BTA Evidence authoring reachability. ChatGPT workspace apps still
-require a working streamable-http Remote MCP URL and admin publication.
+{{#if installReady}}Install ready: yes{{else}}Install ready: no{{#if discoveryBlocker}} ({{discoveryBlocker}}){{/if}}{{/if}}
 
-## Runtime and Role Assistant boundary checks
+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 should resolve assistants dynamically per user from:
+## Runtime and Role Assistant boundaries
 
-{{assistantCatalogUrl}}
+- Runtime resolves assistants dynamically for the current user from `{{{assistantCatalogUrl}}}`.
+- 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.
 
-- The ChatGPT top-level tool surface should stay at Runtime Layer B tools.
-- Evidence authoring remains an internal Business Transformation Assistant capability path, not top-level ChatGPT tools.
+## BTA evidence-authoring proof scenario
 
-## BTA Evidence-authoring proof scenario
+Use this scenario to verify the ChatGPT → Runtime → BTA path without exposing Evidence commands as top-level ChatGPT tools:
 
-Use this scenario to verify ChatGPT → Runtime → BTA path without exposing Evidence commands as top-level ChatGPT tools:
+1. Ask {{baseName}} to improve an existing Role Assistant from process documentation.
+2. Confirm that {{baseName}} starts or continues Business Transformation Assistant work through Runtime.
+3. Confirm that BTA performs evidence metadata, download, upload, and reasoning operations internally and presents certified proposals.
+4. Approve selected proposals and confirm that activation remains an explicit human action.
 
-1. Ask ChatGPT to improve an existing Role Assistant from process documentation.
-2. Confirm ChatGPT starts or continues Business Transformation Assistant work through Runtime.
-3. Confirm BTA performs evidence metadata/download/upload reasoning and presents certified proposals.
-4. Approve selected proposals and confirm activation remains an explicit human action.
+## AI Fabrix validation
 
-## AI Fabrix validation commands
+Before workspace publication, validate the live Streamable HTTP endpoint with MCP Inspector and confirm that initialization, tool discovery, representative calls, invalid inputs, OAuth challenges, and authorization checks all work.
 
-After workspace publication and authentication setup:
+Then run the AI Fabrix probe:
 
 ```bash
 aifabrix channel add {{channelTarget}} --name "{{baseName}}" --probe
 ```
 
+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.
+
+## Current validation status
+
+- Local artifact validation: complete
+- Live Runtime validation: pending
+- ChatGPT workspace tool scan: pending
+- ChatGPT workspace publication: requires a workspace admin or owner

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

@@ -5,10 +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` for ChatGPT workspace admins to connect a custom MCP app to the
-runtime-orchestration server.
+`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/chatgpt/manifest.template.json.hbs

@@ -6,9 +6,9 @@
   "environment": "{{environment}}",
   "runtime": {
     "runtimeSystemKey": "{{runtimeSystemKey}}",
-    "remoteMcpUrl": "{{mcpUrl}}",
+    "remoteMcpUrl": "{{{mcpUrl}}}",
     "transport": "{{runtimeTransport}}",
-    "assistantCatalogUrl": "{{assistantCatalogUrl}}",
+    "assistantCatalogUrl": "{{{assistantCatalogUrl}}}",
     "roleAssistantResolution": "dynamic-runtime",
     "layerBToolNames": [
 {{#each layerBToolNames}}
@@ -19,7 +19,7 @@
   "authentication": {
     "mode": "{{runtimeAuthMode}}",
     "credentialKey": "{{credentialKey}}",
-    "credentialPortalUrl": "{{credentialPortalUrl}}",
+    "credentialPortalUrl": "{{{credentialPortalUrl}}}",
     "scopes": {{{scopesJson}}}
   },
   "boundaries": {

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",