# P02 — Local backend integration evidence Date: 2026-11-22 Baseline: `8f54ccb30426f2955472c0cd40fb94d0b18e86ac` Scope: `docs/PHASES.md` P02. ## What was introduced - Official ZITADEL v4.20.4 Go image; matching official prebuilt Login V2 v4.20.4 runtime dependency. - PostgreSQL 17.10 Alpine, Traefik 3.7.7; Docker Compose loopback-only development stack. - Generated random, local-only ignored `.env` with non-overwriting setup; no secrets committed. - Backend health check via `/app/zitadel ready`, HTTP probe via `/debug/ready`. - Persistent Postgres and login client token volumes; no port exposure besides local 127.0.0.1:8080. - Local helper commands and focused unittest contracts. ## Verification status - Baseline hash and existing unrelated untracked file: inspected before changes. - PC Python: 3.12.0; Docker CLI/Desktop: not detected; PyYAML: not installed. - Python stdlib focused tests: **3/3 PASS**, 0 failures (secret generation/idempotence; version-pinned local-only Compose contract; secrets ignored). - Dev `.env`: generated locally with random secrets, values not printed; `git check-ignore .env` = PASS. - Exact staged patch: 9 approved files; `git diff --cached --check` = PASS; unrelated `AI_INSTRUCTIONS.md` left untracked and unchanged. - Docker Compose validation via `docker compose config`: **BLOCKED** (Docker missing). - Actual backend image pull/start: **BLOCKED** (Docker missing). - Admin Console login: **NOT TESTED**. - Database persistence across restart: **NOT TESTED**. - Safe shutdown/no volume removal: only script behavior reviewed; **runtime NOT TESTED**. ## Exit criteria / unresolved item This phase can be committed as a **configuration-ready, runtime-unverified** checkpoint, but must not be marked full backend acceptance. Once Docker Desktop with Linux containers is installed, run the documented local init/config/up/ps/check/down workflow, verify Admin Console and persistence, and record results in a separately approved follow-up scope. No production deployment is permitted from this developer Compose. ## Safety notes - The new dev Compose stack uses local HTTP and password pre-verification for a synthetic local administrator; do not deploy as production. - P02 does not include UI source, Coolify deployment, domain changes or external Git actions.