@aifabrix/builder 2.60.0 → 2.62.0

package/templates/agent-kit/skills/shared/interaction.md

@@ -0,0 +1,83 @@
+# Structured choices and phase gates
+
+This file owns interactive choices for every Agent Kit skill. Use the same behavior in
+Cursor, Claude, and Codex; host-specific tool names do not change the workflow.
+
+## Show choices in the host control
+
+When the user must choose between discrete actions, invoke the host's native structured
+question control instead of printing a `Choose:` block in chat:
+
+| Host | Native control |
+| --- | --- |
+| Cursor | `AskQuestion` |
+| Claude | `AskUserQuestion` |
+| Codex | `request_user_input` |
+
+Give the control a short header, one direct question, and mutually exclusive options.
+Put the recommended option first, label it `(Recommended)`, and add one short description
+of its effect. Keep the stable option ids below as the workflow result even when a host
+returns a label rather than an id.
+
+If the host supplies its own free-form **Other** choice, map that response to the matching
+`*-other` id. Otherwise include an explicit **Something else** option. If no structured
+question control is available, show the same choices as a numbered list and wait for one
+answer. Never continue merely because an option was recommended.
+
+Do not open a control when the user already made an unambiguous choice in the current
+turn. Treat that choice exactly like the corresponding control result.
+
+## Bare-invocation routes
+
+Ask once and proceed only on an explicit choice.
+
+| Option id | Control label | Means |
+| --- | --- | --- |
+| `route-normal` | Run normal path (Recommended) | Run the normal path for this skill through to its gate, stopping at each phase gate |
+| `route-check` | Inspect and test only | Run validation, checks, and status with no publish or promotion |
+| `route-other` | Something else | Collect the action in the control's free-form response |
+| `next-stop` | Stop here | End without further action |
+
+`route-normal` still stops at every phase gate and still needs `next-yes` to continue. It
+is a route, not permission to run the whole lifecycle unattended.
+
+## After success
+
+Offer the next eligible phase with the structured question control. Proceed only on
+`next-yes`.
+
+Shared option ids: `next-yes` · `next-no` · `next-stop`.
+
+| Completed | Next offer |
+| --- | --- |
+| aifabrix-plan PLAN_READY | connected-system validate |
+| connected-system READY | connected-system build |
+| connected-system BUILT | connected-system publish |
+| connected-system PASS or PASS_WITH_SKIPS | archive (separate) and/or prove validate |
+| prove READY / BUILT / UPDATED | prove next phase |
+| prove PASS or PASS_WITH_SKIPS | iterate validate/build |
+
+Archive is a distinct user decision (`archive-yes` / `archive-no`). Never archive as a
+side effect of PASS.
+
+## On gaps
+
+- NEEDS_DECISIONS: ask about every challenge row with the structured control. No
+  `cust-next`.
+- BLOCKED / FAIL / NEEDS_FIXES / ABORTED: do not offer the next phase as if success.
+
+A phase gate is per-gate, not overall. Offer the next phase only when the **Delivery** row
+supports it; a passing package gate beside `Delivery: NEEDS_FIXES` is not success and the
+offer must name what is still open.
+
+## Phase detection (connected-system and prove)
+
+1. Explicit phase from the user
+2. Ask with the structured control, offering the bare-invocation routes above
+
+There is no third step. Package and plan state decide what you *recommend*, never what you
+run: a bare invocation reports status and stops ([status.md](status.md)). Inferring "the
+safe next eligible phase" is what makes a skill start working before the user has said
+what they want.
+
+Never silently run the following phase after success.

package/templates/agent-kit/skills/shared/status.md

@@ -25,18 +25,9 @@ they cannot see coming.
 
 ## Offer the route, do not choose it
 
-Ask once, with these options. Proceed only on an explicit choice.
-
-| Option id | Means |
-| --- | --- |
-| `route-normal` | Run the normal path for this skill through to its gate, stopping at each phase gate |
-| `route-check` | Inspect and test only — validation, checks and status, no publish or promotion |
-| `route-other` | Something else; ask what |
-| `next-stop` | Stop here |
-
-`route-normal` still stops at every phase gate and still needs `next-yes` to continue
-([interaction.md](../aifabrix-plan/references/interaction.md)). It is a route, not a
-licence to run the whole lifecycle unattended.
+Use the host's native selection control and the canonical route options in
+[interaction.md](interaction.md). Proceed only on an explicit choice. Do not print a
+`Choose:` block when a structured question control is available.
 
 ## Always report the combined matrix
 

package/templates/applications/builder-api/application.yaml

@@ -5,7 +5,7 @@ app:
   description: 'Business Transformation services — HTTP orchestration for connected-system workspace lifecycle via Dataplane Enterprise MCP and governance APIs.'
   type: webapp
   language: typescript
-  version: 2.60.0
+  version: 2.62.0
 
 # Image Configuration
 image:

package/templates/applications/builder-api/env.template

@@ -23,11 +23,15 @@ MAX_UPLOAD_TIMEOUT_MS=300000
 # =============================================================================
 # url:// resolves after kv:// at resolve time (see docs/configuration/resolve-running-urls.md)
 
+# Governed configuration uses per-application client credentials by default. The SDK loads
+# its bootstrap snapshot and refreshes it automatically within two minutes; consumers decide
+# whether a changed key also requires an internal client or resource to be recreated.
+MISO_AUTH_MODE=client-credentials
 # Registered OAuth client (populated by aifabrix app register / bootstrap — same as dataplane)
 MISO_CLIENTID=kv://builder-api-client-idKeyVault
 MISO_CLIENTSECRET=kv://builder-api-client-secretKeyVault
 
-# Internal: controller API for token validation (supports all miso-controller auth modes)
+# Private service-to-service controller origin. Public or remote controller origins require HTTPS.
 MISO_CONTROLLER_URL=url://miso-controller-internal
 # Public: OAuth profile and remaining-step links shown to vendors (not Docker DNS)
 MISO_CONTROLLER_PUBLIC_URL=url://miso-controller-public

package/templates/applications/dataplane/application.yaml

@@ -5,7 +5,7 @@ app:
   description: "AI Fabrix Dataplane is a secure, in-tenant integration and automation layer that supplies governed, normalized, and explainable enterprise data to AI agents. Using CIP as a declarative standard, it enforces RBAC and ABAC, executes integrations, and exposes trusted data via MCP and OpenAPI."
   type: webapp
   language: python # Explicitly specify Python language
-  version: 2.0.74
+  version: 2.0.82
 # Image Configuration
 # Set tag to match your build (example: aifabrix build dataplane -t 1.0.0).
 # Registry is required so the controller can pull the image (avoids docker-not-found on the controller host).
@@ -26,7 +26,7 @@ frontDoorRouting:
   pattern: /data/*
   enabled: true
   # Docker url://internal full URLs: http://dataplane:PORT only (ingress /data is not on in-container routes).
-  internalDockerUseOriginOnly: false
+  internalDockerUseOriginOnly: true
   host: ${DEV_USERNAME}.${REMOTE_HOST}
   tls: ${TLS_ENABLED}
   # Origin RFC 9728 PRM (outside /data PathPrefix) — Builder Traefik pass-through (plan 171.0).

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.74
+VERSION=2.0.82
 # 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
@@ -137,21 +137,18 @@ ABAC_POLICY_PARSE_CACHE_MAX_ENTRIES=2048
 # AUTHENTICATION CONFIGURATION
 # =============================================================================
 
-# MISO secret runtime (583.0): every process calls miso-client init_secrets() once.
-# Unset/local: MISO_AUTH_MODE=local — the SDK keeps this .env/dotenv credential flow.
-# Azure: deployment supplies MISO_AUTH_MODE=azure-managed-identity, MISO_CONTROLLER_URL,
-# MISO_BOOTSTRAP_AUDIENCE (and optional AZURE_CLIENT_ID); Miso-managed secrets
-# (DATABASE_URL, REDIS_URL, ENCRYPTION_KEY, ...) come from the Controller broker,
-# never from this file, and no MISO_CLIENTSECRET is required or returned.
-# Rotation: changed names are reread from the SDK; DB/Redis pools are disposed and
-# the process reports secretRotationRestartRequired until restarted. Invalidation
-# (denial/expiry) stops new secret-dependent work and makes health unhealthy.
+# MISO governed configuration runtime (583.0): client credentials are active by default.
+# The SDK uses the per-application credentials below to load its bootstrap snapshot and
+# refreshes it automatically within two minutes. Changed names invoke application refresh
+# handlers; a handler may still recreate an internal resource such as a DB or Redis client.
+# Override with MISO_AUTH_MODE=local only for an explicit .env/dotenv development flow.
+# Invalidation (denial/expiry) stops new secret-dependent work and makes health unhealthy.
 # Health: /health, /api/v1/health and /api/v1/health/platform return HTTP 503 with
 # reasonCode misoTokenUnavailable | misoTokenRejected | misoControllerUnreachable |
 # misoValidationTimeout whenever the Controller does not accept the live client
 # token — in LOCAL_MODE too. These endpoints measure usable application health,
 # not process liveness.
-MISO_AUTH_MODE=local
+MISO_AUTH_MODE=client-credentials
 # MISO Application Client Credentials (per application)
 # Backend-only: never expose MISO_CLIENTSECRET to the Vite frontend (use VITE_* in app-ui).
 MISO_CLIENTID=kv://dataplane-client-idKeyVault
@@ -167,7 +164,8 @@ KEYCLOAK_REALM=aifabrix
 # =============================================================================
 # Public: browser redirects and CORS (includes /controller front-door path from miso-controller application.yaml).
 MISO_WEB_SERVER_URL=url://miso-controller-public
-# Internal: server-to-controller API calls (Docker: service:port; local: host:port — no front-door path).
+# Private service-to-service controller origin. The SDK permits HTTP only for a local/private
+# target; public or remote controller origins still require HTTPS.
 MISO_CONTROLLER_URL=url://miso-controller-internal
 # Browser logout page on miso-controller (path relative to MISO_WEB_SERVER_URL; not dataplane /login).
 MISO_LOGOUT_URL=/logout

package/templates/applications/integration-server/application.yaml

@@ -0,0 +1,91 @@
+# AI Fabrix Builder app config — INTEGRATOR server type.
+#
+# Same code as builder/builder-server/, different installation. One source tree, two
+# manifests: the Dockerfile's `integrator` target and this folder's env.template are the
+# only things that differ, so there is no forked codebase to keep in step.
+#
+# Enterprise is the existing full development box with Docker. Integrator is a single
+# container giving developers SSH-only access, with no Docker execution inside it.
+
+app:
+  key: integration-server
+  displayName: AI Fabrix Integration Server
+  description: AI Fabrix Integration Server onboards developers over SSH into one container. It creates their Linux accounts and authorized keys, and gives them SSH-only access without Docker inside that container.
+  type: webapp
+  version: 2.0.10
+image:
+  name: aifabrix/integration-server
+  tag: latest
+  registry: aifabrixacr.azurecr.io
+  registryMode: external
+# Base 3006 keeps it clear of builder-server (3002), dataplane (3001), mori-controller
+# (3004) and builder-api (3005), so both server types can run on one dev host.
+# Builder derives the host port as `port` + developerId * 100 (dev01 -> 3106).
+port: 3006
+webSocketsEnabled: true
+# This container administers its own operating system: it creates the developers'
+# Linux accounts, writes /etc/ssh/authorized_keys.d and runs sshd. Builder otherwise
+# runs containers as the invoking host user, which cannot do any of that.
+runAsRoot: true
+# Developers reach this installation over SSH, so that port has to be published as well
+# as the HTTP one. The base keeps SSH's well-known number and the published port follows
+# the same formula as the main port — 22 + developerId * 100 — so dev01 gets 122 and two
+# developers on one host cannot collide. Bootstrap advertises it via SSH_PUBLIC_PORT.
+additionalPorts:
+  - name: ssh
+    containerPort: 22
+    hostPort: 22
+requires:
+  database: false
+  redis: false
+  storage: true
+build:
+  language: typescript
+  context: ../..
+  dockerfile: builder/builder-server/Dockerfile
+  # Selects the Dockerfile's integrator stage. Without it Docker builds the last stage,
+  # which is enterprise — the same image under a different name. This is the one build
+  # difference between the two installations.
+  target: integrator
+  # No envOutputPath: this installation only runs in Docker, and Builder treats the
+  # value as a directory — pointing it at a file name creates a folder of that name.
+  #
+  # Reload runs the real entrypoint, not a bare watcher. The generated compose bind-mounts
+  # the repository over /app and clears the image ENTRYPOINT, which for this installation
+  # meant no sshd, no account-ops worker, and the API running as root — so nothing about
+  # SSH, provisioning or privilege separation worked in the mode developers actually use,
+  # and a queued account was never created. The entrypoint finds the build itself —
+  # /app/dist in the image, /app/builder-server/dist under the bind mount — because the
+  # compose template HTML-escapes `=`, so a VAR=value prefix never survives as an
+  # assignment.
+  #
+  # The API therefore starts from the host's build, so a code change is
+  # `npm run build --prefix builder-server` and a restart, not an in-container watch. That
+  # is deliberate: the watcher ran as root and left root-owned dist/ behind, which then
+  # broke the next `pnpm check` on the host.
+  reloadStart: exec /docker-entrypoint-integrator.sh
+# Ingress. A distinct prefix from builder-server's /server/*, which is not cosmetic: the
+# two installation types are alternatives in production, but a development host runs both,
+# and two applications declaring the same host and prefix collide. Traefik then routes the
+# prefix to whichever container was created last, so integrator-only routes answer 404
+# from the enterprise container — a failure that looks like a bug in the route rather than
+# a collision in the manifests.
+#
+# The pattern is a PathPrefix, not an allowlist: it forwards every path beneath it, so the
+# application refuses anything else that arrives through the front door. Filtering at the
+# ingress is still required and is tracked as open in 029 V4.
+frontDoorRouting:
+  pattern: /integrator/*
+  enabled: true
+  host: ${DEV_USERNAME}.${REMOTE_HOST}
+  tls: ${TLS_ENABLED}
+  internalDockerUseOriginOnly: true
+repository:
+  enabled: false
+  repositoryUrl: ''
+deployment:
+  controllerUrl: ''
+  environment: dev
+healthCheck:
+  path: /health
+  interval: 30

package/templates/applications/integration-server/env.template

@@ -0,0 +1,215 @@
+# Integration Server — INTEGRATOR installation
+# =============================================================================
+# A single managed container giving developers SSH-only access, with no Docker
+# execution inside it. Identity and configuration are pushed in by Miso; secrets
+# come from the secret store, not from this container's filesystem.
+#
+# The enterprise installation is a different manifest with its own template —
+# builder/builder-server/env.template. Same code, different deployment; each
+# template lists only the variables its own installation reads.
+#
+# Conventions (as used across AI Fabrix apps):
+#   kv://name    secret resolved from the secret store — never a literal here
+#   url://name   URL derived by Builder from the manifest
+#   ${VAR}       value supplied per environment
+
+# =============================================================================
+# CORE
+# =============================================================================
+
+# HTTP listen port (main.ts). Default: 3006
+PORT=3006
+
+# SQLite DB, audit log and managed state.
+#
+# A subdirectory of the mount, not its root: this is a separate installation with its
+# own database, users and identity model. On a dev host running both side by side the
+# bind mount is shared, and pointing both at the root would have each read the other's
+# database — which fails closed, because the recorded server type would not match.
+DATA_DIR=/mnt/data/integrator
+
+# Installation type (config/server-type.ts), resolved once at startup and then
+# persisted in builder.db. This installation IS an integrator, so it is set
+# explicitly: unset would mean enterprise. A populated installation cannot switch
+# type on a restart — that needs a migration.
+BUILDER_SERVER_TYPE=integrator
+
+# Set false or 0 to disable DATA_DIR/audit.log (audit.service.ts). Default: true
+# AUDIT_LOG_ENABLED=true
+
+# =============================================================================
+# SECRETS
+# =============================================================================
+
+# AES-GCM key for the secrets API, as a value from the secret store — this
+# installation has no host filesystem to mount a key file from.
+# 64 hex characters or 32 bytes.
+#
+# Generate a NEW key when installing this server. Never point this at the platform's
+# own key — Miso's, or the enterprise Builder Server's ENCRYPTION_KEY_PATH file.
+# Installing a customer's integrator with the platform key would let every developer
+# with a shell in that container decrypt every other installation's secrets, because
+# the same key is handed to each of them in their config.yaml. One installation, one
+# key: the blast radius of a leaked key is then that installation and nothing else.
+#
+#   openssl rand -hex 32
+#
+# The name follows the catalog's own `{appKey}-secrets-encryptionKeyVault` convention,
+# so it is this application's app-scoped secret and nothing else's. The earlier name said
+# `builder-server`: that is another application's key, and reading it from here would be
+# a cross-application read that only works by being deliberately shared — which is the
+# hole this avoids. Register it at install:
+#
+#   aifabrix secret set integration-server-secrets-encryptionKeyVault "$(openssl rand -hex 32)"
+#
+# The same key is written into every managed developer's config.yaml as
+# `secrets-encryption`, so the CLI can decrypt what this server encrypted. Those two
+# are one value from one source by construction — see account-ops-worker.ts, which
+# resolves it from this variable at the moment it writes the file. Rotating it means
+# re-running configuration sync so the homes are rewritten; values already stored in
+# the secrets table are encrypted with the old key and do not survive a rotation.
+ENCRYPTION_KEY=kv://integration-server-secrets-encryptionKeyVault
+
+# =============================================================================
+# MISO
+# =============================================================================
+# Where identity and configuration come from. Builder Server knows Miso only: it
+# never configures or verifies the identity provider — miso-client owns that.
+# /health carries a `miso` check on this installation, and fails without these.
+
+# Server-to-controller API calls on the environment network.
+MISO_CONTROLLER_URL=url://miso-controller-internal
+
+# Application client credentials, used to obtain an application token and to verify
+# the client tokens on POST /api/integrations/miso/*.
+MISO_CLIENTID=kv://integration-server-client-idKeyVault
+MISO_CLIENTSECRET=kv://integration-server-client-secretKeyVault
+
+# Reachable addresses reported to Miso after the HTTP listener starts. Miso uses the
+# internal address for user/configuration delivery and exposes the public address in
+# application status. Keep these derived from the manifest, like Dataplane's status
+# registration; a typed hostname or port drifts in local developer environments.
+INTEGRATION_SERVER_WEB_SERVER_URL=url://public
+INTEGRATION_SERVER_INTERNAL_URL=url://internal
+
+# The `environment` value written into each developer's ~/.aifabrix/config.yaml.
+# `controller` and `codingPlatform` are pushed by Miso; this one is the
+# installation's own deployment configuration and is never taken from the request.
+MANAGED_CONFIG_ENVIRONMENT=dev
+MISO_ENVIRONMENT=dev
+
+# =============================================================================
+# DEVELOPER ACCESS — SSH
+# =============================================================================
+
+# SSH endpoint returned to enrolling developers by POST /api/bootstrap/ssh.
+#
+# This is what the client is told to connect to, so it must be the address that is
+# actually reachable, not the container's own view. Both are derived rather than typed:
+# the host from the front door, and the port from the `ssh` entry in the manifest's
+# `additionalPorts` (Builder publishes it as SSH_PUBLIC_PORT = hostPort + developerId *
+# 100). Typing either by hand drifts from the manifest and advertises an endpoint
+# nothing is listening on.
+INTEGRATOR_SSH_HOST=url://public
+INTEGRATOR_SSH_PORT=${SSH_PUBLIC_PORT}
+
+# Where sshd reads each developer's authorized keys from.
+#
+# State, not configuration: it records which key each developer enrolled. Kept in the
+# image it was destroyed by every redeploy, and although reconciliation rebuilds it from
+# the database at startup, a developer reconnecting before that finishes is refused.
+# On the volume the file is already correct when sshd starts.
+#
+# Root-owned, inside a directory developers cannot write to.
+# Default: ${DATA_DIR}/authorized_keys.d
+# AUTHORIZED_KEYS_DIR=/mnt/data/integrator/authorized_keys.d
+
+# Root of the managed developer home directories.
+#
+# Must be on the persistent volume. A managed home is not scratch space: it holds the
+# developer's cloned repositories and build trees, the credentials their agent uses, the
+# managed config.yaml and the client certificate this server issued. An agent run takes
+# hours and outlives any single connection, so the work has to survive a redeploy.
+#
+# Inside the image it did not. Every redeploy destroyed the homes, which silently revoked
+# access as well as losing the work: the Linux accounts and their authorized_keys went
+# with them, while the projection in builder.db still said the developer was entitled.
+#
+# The entrypoint creates this root 755 and grants traverse on the path leading to it;
+# each developer's own home inside is 700 and owned by them.
+# Default: ${DATA_DIR}/home
+# DEVELOPER_HOME_ROOT=/mnt/data/integrator/home
+
+# Restores keys even though the projection has gone backwards.
+#
+# This installation records the highest Miso revision it has ever seen, outside the
+# database, so restoring builder.db from before a revocation is detectable: the mark is
+# higher than anything the projection now holds. When that happens the installation fails
+# closed — every developer is reconciled to no keys until Miso re-synchronises a revision
+# at least as high as the one already seen. Homes are retained and the server still boots,
+# so it can be repaired.
+#
+# A database rebuilt deliberately looks identical to one restored from before a
+# revocation, so this is the way past it. Set it only when you know the rebuild was
+# intended; it is logged when used. Only the exact value `true` is accepted.
+# ONBOARDING_ALLOW_BACKWARDS_PROJECTION=true
+
+# =============================================================================
+# CLIENT DOWNLOAD
+# =============================================================================
+# What GET /client/<target>.zip writes into the aifabrix.json beside the executable.
+#
+# The executable itself is identical for every installation — SmartScreen builds
+# reputation against a file hash, so a per-customer binary would never accumulate any.
+# The customer scope travels in this small file instead.
+
+# Platform origin the client posts its SSH key to. Only the origin is used; the client
+# appends its own path, so a value carrying /server would double it.
+CLIENT_PLATFORM_URL=url://public
+
+# Controller the client signs in against, as a browser reaches it.
+CLIENT_CONTROLLER_URL=url://miso-controller-public
+
+# Shown while onboarding, e.g. "Acme Corp". Optional.
+# CLIENT_DISPLAY_NAME=
+
+# How this installation is reached: `ssh` or `wss`. Exactly one is served.
+#
+#   ssh  Developers reach sshd over a private network overlay, which is the only route to
+#        the port — this installation must not publish 22 publicly. Deactivating a person
+#        in the overlay removes their route, and that is what ends access, including for
+#        sessions already open. The tunnel endpoint does not exist.
+#
+#   wss  There is no overlay: the session travels inside a WebSocket on the published
+#        HTTPS port, and sshd listens on loopback only, so the tunnel is the only way in.
+#        This server does the authorizing — a short-lived token at the open, refreshed
+#        over the tunnel while the developer works, and dropped on idle or revocation.
+#
+# Not both. Publishing 22 alongside the tunnel would make the overlay stop being a
+# control, and running both against one sshd means "does this person still have access?"
+# depends on which door they used — with the door that fails open deciding.
+#
+# Stated by the server because the server knows how it is published; the client reads it
+# from aifabrix.json and never has to guess. Guessing wrong fails as a timeout, which is
+# the least diagnosable failure there is.
+CLIENT_TRANSPORT=wss
+
+# =============================================================================
+# FRONT DOOR
+# =============================================================================
+# The application is published whole at its virtual directory, the same way
+# miso-controller serves /miso and dataplane serves /data. What is reachable from
+# outside is decided by `frontDoorRouting` in application.yaml and by the ingress.
+
+# Injected by Builder from `frontDoorRouting.pattern` in application.yaml; listed
+# because the app reads it. Routes are served unprefixed — the ingress strips the
+# prefix before the request arrives — so this only builds URLs handed to clients.
+# BASE_PATH=/integrator
+# X_FORWARDED_PREFIX=/integrator
+
+# =============================================================================
+# TESTING
+# =============================================================================
+
+# Enables POST /api/dev/e2e-reset. Never set in production.
+# E2E_RESET_SECRET=

package/templates/applications/keycloak/application.yaml

@@ -9,7 +9,12 @@ app:
 # Image Configuration
 image:
   name: aifabrix/keycloak
-  tag: '26.7.3-aifabrix.1'
+  # `latest`, like every other app here. The Keycloak version lives in app.version above,
+  # which is what `aifabrix push --tag 'latest,{version}'` expands, so nothing is lost by
+  # not repeating it here. Pinning it made `aifabrix run` look for keycloak-dev1:<version>
+  # while `aifabrix build` only ever produces :latest, so dev-build-kc failed with
+  # "Docker image not found" on an image it had just built.
+  tag: latest
   registry: aifabrixacr.azurecr.io
   registryMode: external
 

package/templates/applications/mirrored-templates.json

@@ -0,0 +1,52 @@
+{
+  "mirrors": [
+    {
+      "path": "templates/applications/miso-controller/env.template",
+      "master": {
+        "repo": "aifabrix-miso",
+        "path": "builder/miso-controller/env.template"
+      },
+      "sha256": "9b74b94d5d6e7457d22cfe213f2ec9c3dceb75c540df3953aba3b51c35df05c7"
+    },
+    {
+      "path": "templates/applications/builder-api/env.template",
+      "master": {
+        "repo": "aifabrix-miso",
+        "path": "builder/builder-api/env.template"
+      },
+      "sha256": "1a6b013aa0a34b72c5a0be3dd714bd718a8adb981bcbb9de3d5370e2dd33786c"
+    },
+    {
+      "path": "templates/applications/keycloak/env.template",
+      "master": {
+        "repo": "aifabrix-miso",
+        "path": "builder/keycloak/env.template"
+      },
+      "sha256": "72de7dc5345b842bc20566f8d5105b6541e8185dff157e9af2d37db9590b01fb"
+    },
+    {
+      "path": "templates/applications/dataplane/env.template",
+      "master": {
+        "repo": "aifabrix-dataplane",
+        "path": "builder/dataplane/env.template"
+      },
+      "sha256": "d35eda839464a65ebd018064ea7c2d292654891b41d1f56862b052720a78a3cc"
+    },
+    {
+      "path": "templates/applications/integration-server/env.template",
+      "master": {
+        "repo": "aifabrix-setup",
+        "path": "builder/integration-server/env.template"
+      },
+      "sha256": "a80584bcf6880937c43557a71ca1c423104ab4e15badf4bb14a0a9a9dcaa01d6"
+    },
+    {
+      "path": "templates/applications/integration-server/application.yaml",
+      "master": {
+        "repo": "aifabrix-setup",
+        "path": "builder/integration-server/application.yaml"
+      },
+      "sha256": "04cbfdb9a012393a5e97a1dda1b8f304e97c9532339f045e5912cd250a26a179"
+    }
+  ]
+}