mfeflow 0.5.0 → 0.6.0

package/README.md

@@ -26,7 +26,7 @@ pnpm dev                                    # shell on :4300, remotes on :4311,
 | `mfeflow registry build <dir>`        | Check a folder of features and write `index.json` and the files to host               |
 | `mfeflow dev`                         | Run the shell and every remote, one prefixed log each; follows `add remote`           |
 | `mfeflow doctor`                      | Singletons, compatibility, config health, drift; `--fix` repairs the safe ones        |
-| `mfeflow validate`                    | `mfeflow.json`, every `mfe.json` and every registry entry against their schemas       |
+| `mfeflow validate`                    | `mfeflow.json`, every `mfeflow.app.json` and every registry entry against schemas     |
 | `mfeflow check-compat`                | Each remote's shared ranges against the shells it runs in                             |
 | `mfeflow budget`                      | Built first-load JS of the shell and each remote against the cost-model budget        |
 | `mfeflow deploy <remote> --env <env>` | Upload a remote's build to a static registry host and point the env's index at it     |
@@ -48,13 +48,17 @@ runs part of the project; `--remote name=url` uses a server you run yourself (th
 localhost unless `--allow-origin <origin>` names it); Ctrl+C stops every app, process trees included, on Windows too.
 It exits 130 after Ctrl+C.
 
+Each app keeps its owner, routes and budgets in `mfeflow.app.json`. An app that still has the old `mfe.json` works:
+the CLI reads it and prints one notice per command. An app with both files is an error (E122).
+
 `doctor` runs these checks, each with a code and a docs page (`https://mfeflow.github.io/mfeflow/errors/<code>`). It exits with 0
 when there are no errors, else with the lowest exit code among the errors' ranges (project 3 before build 5).
 
 | Check                                 | Code           | Fixed by `--fix`              |
 | ------------------------------------- | -------------- | ----------------------------- |
 | every app in mfeflow.json is on disk  | E112           |                               |
-| valid `mfe.json`, name matches        | E113, E116     |                               |
+| valid `mfeflow.app.json`, name match  | E113, E116     |                               |
+| no app has both app file names        | E122           |                               |
 | no shared port                        | E115           |                               |
 | no route claimed twice                | E116           |                               |
 | registry entry per remote and env     | E114           | writes the missing ones       |
@@ -70,7 +74,7 @@ when there are no errors, else with the lowest exit code among the errors' range
 | server keys listed in `turbo.json`    | E121 (warning) |                               |
 
 `validate` runs the schema and registry checks, `check-compat` the compatibility check, `budget` reads the build output
-(`dist/`): each remote's entry against `budget.remoteKb` (10), a route against `mfe.json` `budgets.initialJsKb`, and the
+(`dist/`): each remote's entry against `budget.remoteKb` (10), a route against `mfeflow.app.json` `budgets.initialJsKb`, and the
 shell against `budget.baselineKb + budget.shellKb` (32) when a baseline is set. All four take `--json` and exit non-zero on
 errors. LCP is measured by the perf job, not by `budget`.
 
@@ -111,6 +115,7 @@ MFEFLOW_E108 The target folder is not empty: /work/app already has notes.txt
 | 5    | build or runtime problem: `MFEFLOW_E3xx`                                |
 | 6    | feature registry problem: `MFEFLOW_E4xx`                                |
 | 7    | deploy problem: `MFEFLOW_E5xx`                                          |
+| 8    | upgrade problem, or files that need a decision: `MFEFLOW_E6xx`          |
 | 130  | cancelled at a prompt (nothing was written), or Ctrl+C in `mfeflow dev` |
 
 ## Try it from a checkout

package/assets/features/registry-server/feature.json

@@ -0,0 +1,128 @@
+{
+  "name": "registry-server",
+  "version": "0.1.0",
+  "description": "Wire the project to a self-hosted mfeflow registry server: the shell reads its index from the server (with the browser beacon for percentage rollouts), a CI workflow deploys every remote with a token from the environment, and a guide covers the day-to-day commands. Opt-in; the static registry works without it.",
+  "requires": ["core"],
+  "prompts": [
+    {
+      "name": "serverUrl",
+      "type": "string",
+      "message": "Registry server address (https://registry.example.com), empty to set it later",
+      "default": ""
+    }
+  ],
+  "files": [
+    {
+      "to": "src/registry-sources.ts",
+      "target": "shell",
+      "from": "files/registry-sources.ts"
+    },
+    {
+      "to": "docs/registry-server.md",
+      "target": "root",
+      "from": "files/registry-server.md.eta",
+      "template": true
+    },
+    {
+      "to": ".github/workflows/deploy-server.yml",
+      "target": "root",
+      "from": "files/deploy-server.yml",
+      "when": {
+        "feature:ci-github": true
+      }
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "mfeflow",
+      "range": "latest",
+      "target": "root",
+      "dev": true
+    }
+  ],
+  "scripts": [
+    {
+      "name": "server:deploy",
+      "command": "mfeflow deploy",
+      "target": "root"
+    },
+    {
+      "name": "server:rollback",
+      "command": "mfeflow rollback",
+      "target": "root"
+    },
+    {
+      "name": "server:status",
+      "command": "mfeflow status",
+      "target": "root"
+    }
+  ],
+  "transforms": [
+    {
+      "op": "add-env-key",
+      "file": "src/config/schema.ts",
+      "target": "shell",
+      "key": "registryUrls",
+      "scope": "runtime",
+      "schema": {
+        "zod": "z.array(z.string())",
+        "valibot": "v.array(v.string())",
+        "arktype": "'string[]'"
+      },
+      "value": [],
+      "configFiles": [
+        "public/config/runtime-config.dev.json",
+        "public/config/runtime-config.staging.json",
+        "public/config/runtime-config.prod.json"
+      ],
+      "when": {
+        "feature:env-t3": true
+      }
+    },
+    {
+      "op": "add-env-key",
+      "file": "src/config/schema.ts",
+      "target": "shell",
+      "key": "registryBeacon",
+      "scope": "runtime",
+      "schema": {
+        "zod": "z.boolean()",
+        "valibot": "v.boolean()",
+        "arktype": "'boolean'"
+      },
+      "value": false,
+      "configFiles": [
+        "public/config/runtime-config.dev.json",
+        "public/config/runtime-config.staging.json",
+        "public/config/runtime-config.prod.json"
+      ],
+      "when": {
+        "feature:env-t3": true
+      }
+    },
+    {
+      "op": "add-env-key",
+      "file": "public/config/runtime-config.json",
+      "target": "shell",
+      "key": "registryUrls",
+      "scope": "runtime",
+      "schema": "z.array(z.string())",
+      "value": [],
+      "when": {
+        "feature:env-t3": false
+      }
+    },
+    {
+      "op": "add-env-key",
+      "file": "public/config/runtime-config.json",
+      "target": "shell",
+      "key": "registryBeacon",
+      "scope": "runtime",
+      "schema": "z.boolean()",
+      "value": false,
+      "when": {
+        "feature:env-t3": false
+      }
+    }
+  ]
+}

package/assets/features/registry-server/files/deploy-server.yml

@@ -0,0 +1,69 @@
+name: deploy-server
+
+# Deploys every remote through the registry server when main changes. The builds go to the artifact host first,
+# then the server moves the pointer. Needs the address of the server (MFEFLOW_REGISTRY_URL, a variable), a token
+# (MFEFLOW_REGISTRY_TOKEN, a secret) and an artifact host (see docs/registry-server.md).
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      env:
+        description: Environment to deploy to
+        default: prod
+        type: string
+
+permissions: {}
+
+# Two deploys at once would race on the same pointer; let the first finish.
+concurrency:
+  group: deploy-server
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    # A manual run from another branch would otherwise deploy that branch.
+    if: github.ref == 'refs/heads/main'
+    environment: registry
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: pnpm/action-setup@ea17c68df8912ef543352723c149a84f56e3d413 # v6.1.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
+        with:
+          node-version: lts/*
+          cache: pnpm
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm build
+      - name: Deploy remotes
+        env:
+          DEPLOY_ENV: ${{ inputs.env || 'prod' }}
+          MFEFLOW_REGISTRY_URL: ${{ vars.MFEFLOW_REGISTRY_URL }}
+          MFEFLOW_REGISTRY_TOKEN: ${{ secrets.MFEFLOW_REGISTRY_TOKEN }}
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          MFEFLOW_S3_ENDPOINT: ${{ vars.MFEFLOW_S3_ENDPOINT }}
+          MFEFLOW_S3_REGION: ${{ vars.MFEFLOW_S3_REGION }}
+        run: |
+          set -euo pipefail
+          # With -e, a mfeflow.json that cannot be read or parsed stops the step here.
+          remotes=$(node -p "Object.entries(JSON.parse(require('fs').readFileSync('mfeflow.json', 'utf8')).apps).filter(([, app]) => app.kind === 'remote').map(([name]) => name).join(' ')")
+          if [ -z "$remotes" ]; then
+            echo "::error::mfeflow.json lists no remotes to deploy"
+            exit 1
+          fi
+          failed=""
+          for remote in $remotes; do
+            if ! pnpm mfeflow deploy "$remote" --env "$DEPLOY_ENV" --yes; then
+              failed="$failed $remote"
+            fi
+          done
+          if [ -n "$failed" ]; then
+            echo "::error::deploy failed for:$failed"
+            exit 1
+          fi

package/assets/features/registry-server/files/registry-server.md.eta

@@ -0,0 +1,52 @@
+# Registry server
+
+This project can publish its remotes through a self-hosted mfeflow registry server. The server keeps the pointer
+(which version each environment serves) in SQLite, checks every deploy, and takes tokens with narrow scopes. The
+build files still live on a static host or bucket; the server only moves the pointer.
+
+## Configuration
+
+- `serverUrl`: <%= it.options.serverUrl === '' ? 'not set yet' : '`' + it.options.serverUrl + '`' %>
+
+This is the address `registry-server` was added with. Commands read it from `MFEFLOW_REGISTRY_URL`, or `--registry-url`.
+The token is read only from `MFEFLOW_REGISTRY_TOKEN`; there is no flag for it, so it never lands in your shell history.
+Plain http works only for localhost.
+
+## Point the shell at the server
+
+In `public/config/runtime-config.prod.json`, set the index address and the origins it may be on:
+
+```json
+{
+  "registryUrls": ["https://registry.example.com/v1/index/prod", "/registry/index.json"],
+  "registryOrigins": ["https://registry.example.com"],
+  "registryBeacon": true
+}
+```
+
+The second URL is the static fallback the server republishes, so shells still boot if the server is down. Then use
+`src/registry-sources.ts` in `src/bootstrap.tsx`: replace `registrySources()` with the one from `./registry-sources`.
+`registryBeacon: true` lets browsers report load errors, which is how the server halts a bad percentage rollout.
+
+## Commands
+
+```sh
+export MFEFLOW_REGISTRY_URL=https://registry.example.com
+export MFEFLOW_REGISTRY_TOKEN=...            # from `mfeflow-registry token create` on the server
+pnpm server:deploy catalog --env prod        # upload the build, ask the server to point prod at it
+pnpm server:status --env prod                # what the server serves
+pnpm server:rollback catalog --env prod      # back to the previous version
+pnpm mfeflow kill catalog --env prod         # out of the index at once
+pnpm mfeflow deploy catalog --env prod --percent 10 --steps 50,100
+pnpm mfeflow rollout status catalog --env prod
+```
+
+`deploy` uploads the build to the artifact host first (`--host`, or `registry.host` in `mfeflow.json`), so the host
+credentials are the same as for the static registry. Then it asks the server, which reads the files back and runs its
+own checks.
+
+## In CI
+
+With `ci-github` in the project, `.github/workflows/deploy-server.yml` deploys every remote when `main` changes. Add
+`MFEFLOW_REGISTRY_TOKEN` and the artifact host credentials as secrets of the `registry` environment, and
+`MFEFLOW_REGISTRY_URL` as a variable. Give the token only `read` and `deploy` for the environment it deploys to.

package/assets/features/registry-server/files/registry-sources.ts

@@ -0,0 +1,12 @@
+import type { RegistrySources } from '@mfeflow/runtime';
+
+/**
+ * The index URLs for the shell. With `registryBeacon: true` in the runtime config this adds the
+ * browser's id to the registry server's URLs (so a percentage rollout reaches the same people every
+ * time) and starts the reporter that lets the server halt a bad rollout. Otherwise it is
+ * `registrySources()` as it was. Use it in `bootstrap.tsx` in place of `registrySources()`.
+ */
+export async function registrySources(): Promise<RegistrySources> {
+  const { registrySourcesWithBeacon } = await import('@mfeflow/runtime/beacon');
+  return registrySourcesWithBeacon();
+}

package/assets/features/registry-static/feature.json

@@ -0,0 +1,61 @@
+{
+  "name": "registry-static",
+  "version": "0.1.0",
+  "description": "Publish remotes to a static registry (a folder, S3, R2 or MinIO) with mfeflow deploy, promote, rollback and status. Adds registry:deploy, registry:rollback and registry:status scripts, a guide, and, when ci-github is present, a workflow that deploys every remote when main changes. Credentials come from CI secrets and the environment only.",
+  "requires": ["core"],
+  "prompts": [
+    {
+      "name": "host",
+      "type": "string",
+      "message": "Registry host (file:<dir> or s3://<bucket>[/prefix]), empty to set it later",
+      "default": ""
+    },
+    {
+      "name": "baseUrl",
+      "type": "string",
+      "message": "URL the host's files are served from (https://cdn.example.com), empty to set it later",
+      "default": ""
+    }
+  ],
+  "files": [
+    {
+      "to": "docs/registry.md",
+      "target": "root",
+      "from": "files/registry.md.eta",
+      "template": true
+    },
+    {
+      "to": ".github/workflows/deploy.yml",
+      "target": "root",
+      "from": "files/deploy.yml",
+      "when": {
+        "feature:ci-github": true
+      }
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "mfeflow",
+      "range": "latest",
+      "target": "root",
+      "dev": true
+    }
+  ],
+  "scripts": [
+    {
+      "name": "registry:deploy",
+      "command": "mfeflow deploy",
+      "target": "root"
+    },
+    {
+      "name": "registry:rollback",
+      "command": "mfeflow rollback",
+      "target": "root"
+    },
+    {
+      "name": "registry:status",
+      "command": "mfeflow status",
+      "target": "root"
+    }
+  ]
+}

package/assets/features/registry-static/files/deploy.yml

@@ -0,0 +1,61 @@
+name: deploy
+
+# Publishes every remote to the static registry when main changes. Needs a host: set the `host` option of
+# the registry-static feature (or `registry.host` in mfeflow.json), and the secrets named below.
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      env:
+        description: Environment to deploy to
+        default: prod
+        type: string
+
+permissions: {}
+
+# Two deploys at once would race on the index; let the first finish.
+concurrency:
+  group: deploy
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    # A manual run from another branch would otherwise deploy that branch.
+    if: github.ref == 'refs/heads/main'
+    environment: registry
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: pnpm/action-setup@ea17c68df8912ef543352723c149a84f56e3d413 # v6.1.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
+        with:
+          node-version: lts/*
+          cache: pnpm
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm build
+      - name: Deploy remotes
+        env:
+          DEPLOY_ENV: ${{ inputs.env || 'prod' }}
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          MFEFLOW_S3_ENDPOINT: ${{ vars.MFEFLOW_S3_ENDPOINT }}
+          MFEFLOW_S3_REGION: ${{ vars.MFEFLOW_S3_REGION }}
+        run: |
+          set -uo pipefail
+          remotes=$(node -p "Object.entries(JSON.parse(require('fs').readFileSync('mfeflow.json', 'utf8')).apps).filter(([, app]) => app.kind === 'remote').map(([name]) => name).join(' ')")
+          failed=""
+          for remote in $remotes; do
+            if ! pnpm mfeflow deploy "$remote" --env "$DEPLOY_ENV" --yes; then
+              failed="$failed $remote"
+            fi
+          done
+          if [ -n "$failed" ]; then
+            echo "::error::deploy failed for:$failed"
+            exit 1
+          fi

package/assets/features/registry-static/files/registry.md.eta

@@ -0,0 +1,49 @@
+# Registry
+
+Remotes are published to a static host: a folder, or an S3-compatible bucket (S3, R2, MinIO). Each version is
+uploaded once and never changes; the environment's `index.json` points at the version people get. A rollback moves
+that pointer back, with no rebuild.
+
+## Configuration
+
+- `host`: <%= it.options.host === '' ? 'not set yet' : '`' + it.options.host + '`' %>
+- `baseUrl`: <%= it.options.baseUrl === '' ? 'not set yet' : '`' + it.options.baseUrl + '`' %>
+
+These are the options `registry-static` was added with (see `features` in `mfeflow.json`). `registry.host` and
+`registry.baseUrl` in `mfeflow.json` take precedence, and `--host` and `--base-url` on a command beat both.
+`host` is `file:<dir>` or `s3://<bucket>[/prefix]`; `baseUrl` is where the host's files are served from, without a
+trailing slash.
+
+## Commands
+
+```sh
+pnpm registry:deploy catalog --env prod     # upload the build, point prod at it
+pnpm registry:status                        # what each environment serves, and drift
+pnpm registry:rollback catalog --env prod   # back to the previous version, no rebuild
+```
+
+`deploy` publishes the version in the remote's `package.json` unless you pass `--version`. Run it with `--dry-run`
+first to see the uploads and the checks.
+
+## Credentials
+
+Credentials are read from the environment and never written to a file: `AWS_ACCESS_KEY_ID`,
+`AWS_SECRET_ACCESS_KEY` and, for R2 or MinIO, `MFEFLOW_S3_ENDPOINT` and `MFEFLOW_S3_REGION`. Locally, export them in
+your shell. Do not commit a `.env` file with them.
+
+## In CI
+
+With `ci-github` in the project, `.github/workflows/deploy.yml` deploys every remote when `main` changes (and from the
+Actions tab, for another environment). Add `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as secrets of the
+`registry` environment, and `MFEFLOW_S3_ENDPOINT` and `MFEFLOW_S3_REGION` as its variables. The workflow is only
+generated when `ci-github` is already in the project, so add `ci-github` first.
+
+Protect the `registry` environment (Settings, Environments): allow deployments from the `main` branch only, and add
+required reviewers for `prod`. The workflow also refuses to run from any other branch. A remote whose files changed
+without a version bump fails its deploy; the others still deploy, and the run fails at the end with the list.
+
+## How fast a rollback reaches people
+
+The index is served with `Cache-Control: max-age=60`, so a browser that already has it keeps it for up to a minute.
+GitHub Pages cannot change its 10 minute cache, so a rollback there takes about 11 minutes. Use a bucket if that is
+too slow.

package/assets/features/release/feature.json

@@ -0,0 +1,43 @@
+{
+  "name": "release",
+  "version": "0.1.0",
+  "description": "Changesets versions each remote on its own. A pull request adds a changeset, `pnpm release:version` bumps the remote's package.json and changelog, and `mfeflow deploy` publishes that same version.",
+  "requires": ["core"],
+  "files": [
+    {
+      "to": ".changeset/config.json",
+      "target": "root",
+      "from": "files/config.json"
+    },
+    {
+      "to": ".changeset/README.md",
+      "target": "root",
+      "from": "files/changeset-readme.md"
+    },
+    {
+      "to": "docs/releasing.md",
+      "target": "root",
+      "from": "files/releasing.md"
+    }
+  ],
+  "dependencies": [
+    {
+      "name": "@changesets/cli",
+      "range": "3.0.3",
+      "target": "root",
+      "dev": true
+    }
+  ],
+  "scripts": [
+    {
+      "name": "changeset",
+      "command": "changeset",
+      "target": "root"
+    },
+    {
+      "name": "release:version",
+      "command": "changeset version",
+      "target": "root"
+    }
+  ]
+}

package/assets/features/release/files/changeset-readme.md

@@ -0,0 +1,7 @@
+# Changesets
+
+A changeset is a short note, in this folder, that says which remote changed and how big the change is. Add one with
+`pnpm changeset` in every pull request that changes a remote. `pnpm release:version` turns the notes into version
+bumps in each remote's `package.json` and into its `CHANGELOG.md`.
+
+See `docs/releasing.md`.

package/assets/features/release/files/config.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": [],
+  "privatePackages": { "version": true, "tag": false }
+}

package/assets/features/release/files/releasing.md

@@ -0,0 +1,21 @@
+# Releasing
+
+Each remote has its own version, kept by [Changesets](https://github.com/changesets/changesets). `mfeflow deploy`
+publishes the version in the remote's `package.json`, so the version you release and the version you deploy are the
+same number.
+
+1. In a pull request that changes a remote, run `pnpm changeset`. Pick the remote, pick patch, minor or major, and
+   write one plain sentence about the change. Commit the file it creates in `.changeset/`.
+2. When you are ready to release, run `pnpm release:version`. It bumps `package.json` and `CHANGELOG.md` in each remote
+   that has a changeset, and deletes the used notes. Commit the result and merge it.
+3. Deploy: `pnpm mfeflow deploy <remote> --env prod`. With the `registry-static` feature that is
+   `pnpm registry:deploy <remote> --env prod`, or the deploy workflow on `main`.
+
+The remotes are private packages, so `.changeset/config.json` sets `privatePackages.version` to `true` (they get a
+version) and `tag` to `false` (nothing is published to npm or tagged).
+
+The files of a published version never change: deploying the same number with different content is refused. To ship
+a fix, add a changeset and bump.
+
+To go back to the previous version, run `mfeflow rollback <remote> --env prod`. It does not touch the version in
+`package.json`, so after a rollback ship the fix as a new patch.

package/assets/templates/monorepo/feature.json

@@ -1,6 +1,6 @@
 {
   "name": "core",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "description": "The shell, the remotes, the registry and the workspace around them.",
   "files": [
     {
@@ -67,9 +67,9 @@
       "template": true
     },
     {
-      "to": "mfe.json",
+      "to": "mfeflow.app.json",
       "target": "shell",
-      "from": "files/shell/mfe.json.eta",
+      "from": "files/shell/mfeflow.app.json.eta",
       "template": true
     },
     {
@@ -121,9 +121,9 @@
       "template": true
     },
     {
-      "to": "mfe.json",
+      "to": "mfeflow.app.json",
       "target": "remotes",
-      "from": "files/remote/mfe.json.eta",
+      "from": "files/remote/mfeflow.app.json.eta",
       "template": true
     },
     {
@@ -323,5 +323,6 @@
       "command": "rsbuild build",
       "target": "remotes"
     }
-  ]
+  ],
+  "migrations": [{ "from": "0.3.0", "to": "0.4.0", "module": "migrations/0.4.0-app-file.mjs" }]
 }

package/assets/templates/monorepo/files/remote/{mfe.json.eta → mfeflow.app.json.eta}

@@ -1,4 +1,5 @@
 {
+  "$schema": "https://mfeflow.github.io/mfeflow/schema/mfeflow-app.json",
   "name": "<%= it.app.name %>",
   "owner": "team-<%= it.app.name %>",
   "shells": ["shell"],

package/assets/templates/monorepo/files/root/README.md.eta

@@ -36,7 +36,7 @@ pnpm mfeflow add <feature>           # see `pnpm mfeflow features`
 
 ```sh
 pnpm doctor              # singletons, compatibility, config, drift; `pnpm doctor --fix` repairs the safe ones
-pnpm validate            # mfeflow.json, every mfe.json and every registry entry
+pnpm validate            # mfeflow.json, every mfeflow.app.json and every registry entry
 pnpm check-compat        # each remote's shared ranges against its shell
 pnpm budget              # after `pnpm build`: first-load JS per shell and remote
 ```

package/assets/templates/monorepo/files/shell/{mfe.json.eta → mfeflow.app.json.eta}

@@ -1,4 +1,5 @@
 {
+  "$schema": "https://mfeflow.github.io/mfeflow/schema/mfeflow-app.json",
   "name": "<%= it.app.name %>",
   "owner": "team-<%= it.app.name %>",
   "shells": [],