AGENTS.md@e2e/journey git:20261020.8d47d7aA

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

# Agent Instructions — `e2e/journey`

The customer's local setup journey, for every CLI framework: a fresh app
directory runs `doctor`, `start` and `setup --server local`, then starts the
generated app. Never test the checked-in demo apps here. Paths below are from
the repo root.

## The journey

- CI runs `npx @zitadel/cli@alpha doctor --runtime binary`,
  `start --runtime binary` and `setup --framework <id> --server local`, each
  with `--non-interactive --json`, for every id in `ciFrameworkIds`
  (`e2e/journey/scripts/frameworks.mjs`). The ids in `ciExcludedFrameworkIds`
  run only by hand (`--framework <id>`).
- The fresh directory starts empty (page posture) or from
  `e2e/journey/fixtures/preexisting/<framework>` (`--preexisting-app`, widget
  posture, ADR 044); both run the same CLI path and browser journeys.
- Keep each pre-existing fixture minimal but real: detectable by the CLI,
  bootable with `npm run dev`, with a distinctive shell and homepage the specs
  assert survive setup. Only route-based frameworks (Next, Nuxt) get one; the
  SPA families keep the page posture.
- Use `npm` in the generated app, as the documented path does.
- Keep generated apps and temporary registries outside the worktree, and the
  app on `localhost`: WebAuthn rejects IP relying-party IDs.
- The remote https lane (`--remote`) is the one exception to `--server local`:
  setup points at `e2e/journey/scripts/https-edge.mjs`, a local https edge for
  `zitadel.test` that, like Vercel's, completes TLS only for its own name,
  routes by `Host` and overwrites `X-Forwarded-*`.
- Docker fallback coverage opts in with `--runtime docker --image <tag>`.
- Passkey coverage is required in CI and rides the `passkey-first` preset
  lane, because the shipped `password-first` flow offers no passkey.
  `JOURNEY_ENABLE_PASSKEY=0` is a local debugging escape hatch only.
- The testkit suite (`moon run e2e:journey -- --suite testkit`) installs
  `@zitadel/testing` from the journey registry into one Next app and runs the
  consumer suite in `e2e/journey/fixtures/testkit/`. It never sets
  `ZITADEL_SERVER_BINARY` or `NEXTGEN_*`: proving the published binary works
  unconfigured is the point.

## Packages and the registry

- Install `@zitadel/*` from the workflow's tarballs through the temporary
  Verdaccio registry, never from public npm.
- Produce tarballs with `moon run release:pack`, which stages the server
  binaries, packs every public package and verifies their metadata.
  `--tarballs-dir` hands prebuilt ones to the runner, which skips building but
  still verifies and publishes them.
- `e2e:journey-local` never packs its own: `release:pack` rewrites the dist
  folders the lanes beside it read. It sets `JOURNEY_TARBALLS_REQUIRED=1`; by
  hand, `moon run e2e:journey -- --ci` packs its own.
- Pack and upload only `PUBLIC_RELEASE_PACKAGES`
  (`scripts/release-manifest.mjs`); `e2e/journey/scripts/verify-tarballs.mjs`
  enforces that set.
- Keep Verdaccio's npmjs metadata cache (`maxage` in
  `e2e/journey/scripts/local-registry.mjs`) well under two hours: `nuxi init`
  can ask for a nuxt released two hours earlier.

## The runner

- CI runs every variant (fresh-app matrix, passkey preset, pre-existing app,
  testkit, remote https) in one `--ci` invocation, the `e2e:journey-local`
  lane, so one process shares one port allocator. A new variant joins the
  runner's `--ci` set, never a new workflow step. How the lane reaches CI:
  [`packages/testing/AGENTS.md`](../../packages/testing/AGENTS.md#moon-and-the-e2e-lanes).
- `scripts/ci-mode.mjs` gates the tarball snapshot and collapses the
  fresh-app matrix to one framework (`JOURNEY_MATRIX=single`) when no SDK, CLI
  or journey surface changed.
- Every option CI sets has a `JOURNEY_*` variable (`journeyArgsFromEnv` in
  `e2e/journey/scripts/run-options.mjs`): turbo puts arguments after `--` into
  every task's cache key.
- Keep each framework suite Playwright-serial with one worker. Suites run in
  parallel only with their own app directory, npm cache and tmp directories,
  app port, Zitadel port and runtime state.
- Reserve ports through the block allocator in
  `e2e/journey/scripts/ports.mjs`, never a listen-on-zero probe: a port
  reserved minutes before use gets taken as an outbound source port meanwhile.
- Time every step that takes seconds with `timePhase` and add its phase to
  `PHASES` (`e2e/journey/scripts/timings.mjs`): the lane × phase table in the
  job summary is how a slow lane is found.
- Upload logs, setup JSON, lockfiles, Playwright traces and reports and
  metadata; never generated `node_modules` or `.next` directories.