AGENTS.md@apps git:20261014.8f2239eA

Immutable. This exact content never changes and is served at /api/v1/blob/f175cb1ec53111ab.

# Agent Instructions — `apps/`

Shared conventions for the deployable apps. Read together with the
[root `AGENTS.md`](../AGENTS.md) and the app's own scoped `AGENTS.md`.

## Vercel build output

**Static Vercel sites build into `dist/` inside the app** (`apps/<app>/dist`).
The output is `dist` either because the app's build writes there (e.g.
`storybook`, whose `build` script passes `--output-dir dist`) or because its
framework preset already defaults there. Keep it `dist` — do not introduce
per-app output names (`storybook-static`, `build`, `out`, …). The hosted cloud's
`storybook` service (repo-root [`vercel.json`](../vercel.json)) serves `dist`
at `/storybook/`: a rewrite of the service maps that path onto the build. The
global `dist` rule in [`.gitignore`](../.gitignore) already covers it, so no
per-app ignore entry is needed.

Four apps are **exceptions**, for reasons that are not a style choice:

- **`console`** emits to `internal/staticui/console/dist` because the Go server
  `go:embed`s that exact tree to serve the console itself
  ([`internal/staticui/console/embed.go`](../internal/staticui/console/embed.go)).
  The output path is dictated by the embed, not by this convention. The
  hosted cloud's `console` service (repo-root [`vercel.json`](../vercel.json))
  builds it for `/console/` (`CONSOLE_BASE_PATH`) and serves that tree as its
  output directory, a rewrite of the service mapping `/console/` onto it.
- **`docs`** and **`website`** are Next.js apps, deployed only as the hosted
  cloud's `docs` and `website` services: Next builds into `.next/`, which
  Vercel's Next.js preset reads, so there is no output directory to set.
- **`mock-zitadel`** is a Vercel **Function** deploy, not a static site: it
  bundles into `api/` and rewrites `/(.*) → /api`, so it has no static
  `outputDirectory` to standardise.