- Official versioned ZITADEL v4 backend image, local PostgreSQL persistence, secure random dev secret generation, first-admin bootstrap and health checks.
- Official prebuilt Login V2 image as a **runtime dependency only** (v4 Admin Console login requires it); no Login V2 source import.
- No backend Go source vendoring, UI redesign, public domain, Coolify deploy, production keys, remote push or changes to unrelated files.
- Verify: static focused test/patch audit; with Docker available, live startup/ready/Admin Console, persistent DB after restart and shutdown.
- **Execution evidence:** Docker CLI/Desktop absent on connected Windows PC; live Compose startup, admin login and persistence remain NOT VERIFIED. Prior P02 static checks are recorded in `docs/P02-EVIDENCE.md`.
- **P02-RUNTIME-ACCEPTANCE-01 instruction update (2026-11-22):** user explicitly deferred all local test/dev execution to a future Gitea Actions phase; this is a source handoff, **not** runtime acceptance. Existing source is committed; authorized push to `vibtools/ZitPlane` is in scope. CI workflow creation and UI import remain outside P02.
- **Write Scope:** `auth/ui/v2/**` (Login V2 and required upstream workspace files), narrow `README.md` and `docs/**` (P03 source/phase notes). No other files.
- **Upstream tag:** `v4.20.4` at `384bb9ec96b501ad39dc232ee2061a40fe180bbd`, matching P02 Go backend image.
- Import `apps/login`, `packages/zitadel-client`, `packages/zitadel-proto`, `proto`, root pnpm/Nx/build files and licensing **nested under `auth/ui/v2/`**. Preserve auth/UI behavior. Exclude upstream environment files; never commit secrets.
- User explicitly requested **no local builds, tests, dev servers or deployments**. Only source/provenance/patch audit, documentation, Git commit and approved Gitea push. CI deferred.
- P02 prebuilt Login UI remains configured in the development Compose; do **not** replace it or call runtime acceptance complete.
- Evidence and known gaps: `docs/P03-SOURCE-IMPORT.md`. CI workflow not part of this scope.
- Separate compact Next.js portal, ZITADEL OIDC/PKCE authentication, server-protected user routes, read-only profile and security settings structure.
- Real OIDC only; no fake production auth, browser admin credentials, billing or user-management mutation endpoints. Existing ZITADEL core/Login V2 untouched.
- Explicitly **no local builds, tests, dev server, Docker or deployment**. Source-level audit only, Git commit and approved Gitea main push. Gitea Actions testing deferred; no CI workflow in this scope.
- Evidence and pending runtime acceptance: `docs/P04-ACCOUNT-PORTAL.md`.
- Full OIDC login/session/MFA/Admin Console interactive acceptance is not covered without disposable app/user provisioning; status remains BLOCKED/PENDING, not fabricated PASS.
- One focused isolated run after source commit/push, no local test/build/Docker, no repeated Account/Login suites, no real users/secrets or production deployment. Full interactive login/MFA remains a separate phase.
- **Gitea Actions Run #86 SUCCESS** on `03fb58954dec886128a4011b6121754cbcdd79ff`: portless effective config PASS, all four services ready, disposable PostgreSQL marker persisted after restart, ZITADEL ready/OIDC issuer/discovery/JWKS and negative contracts PASS, CI-owned network/containers/volumes cleanup verified PASS. No Account/Login build rerun, no local build/Docker. Full interactive OIDC login/MFA and Moderate dependencies remain outside this phase. Evidence: `notes/P05-CI-03.md`, `docs/P05-CI-03.md`.
- Baseline `1a602551ad9a791efcc594834f2fa6ce748339ae`. Previous Run #83 security: 18 Moderate Login advisory records and 1 Moderate Account vulnerable Next.js package; Run #86 backend-only SUCCESS.
- Narrow approved manifest writes: `users/ui/{package.json,package-lock.json}`, `auth/ui/v2/apps/login/package.json`, root `auth/ui/v2/{package.json,pnpm-lock.yaml}` only if justified; new `.gitea/workflows/p05-security-acceptance.yml`, focused `tests/ci/**`, notes/project/docs and associated README/MINIFEST. **`pnpm-workspace.yaml`, application source, Go backend, developer Compose, production and unrelated files remain read-only.**
- Direct Next.js pinned 16.4.6; Login coordinated OTel auto-instrumentation 0.80.0 / SDK 0.222.0 family, PNPM/npm metadata-only lockfile reconciliation. Root overrides are read-only, so glob14/minimatch11 major transitive remediation remains an explicit blocker if registry audit reproduces it.
## P05-SEC-02 - Final Transitive Dependency Remediation (APPROVED 2026-11-22)
- Baseline `43eee54e7ad6b647e38491ac4dc28703547cf410`; prior Gitea Run #87: 3 PASS/1 FAIL, only 2 Login Moderate GHSA (`glob`/`minimatch`) remaining, Account audit 0.
- Exact Scope Lock: `auth/ui/v2/pnpm-workspace.yaml`, `pnpm-lock.yaml`, justified root or Login dependency manifests only, `.gitea/workflows/p05-security-acceptance.yml`, focused `tests/ci/**`, notes/project/docs and associated README/MINIFEST. **Login/auth/UI source, users/ui/**, Go backend, developer Compose, other packages and production READ-ONLY.** Preserve untracked AI_INSTRUCTIONS.md.
- Seven **exact parent-scoped** overrides: two glob10 parents → glob14.0.6, five minimatch10 parents → minimatch11.0.9. No broad global major override; pinned PNPM 10.30.3 metadata-only lockfile regeneration; compatibility subject to CI proof.
- **Actual Gitea Run #88**, tested source SHA `66cfed5a8b6bd5845b229c9934695e307f9a0775`, overall **FAILURE**: Account jobs correctly SKIPPED, Login live production audit **0 Moderate/High/Critical PASS**; Login build job FAIL before frozen install because new contract helper falsely treated existing `>=` semver ranges as parent overrides. No frozen install/build/units executed in this run. Corrected parser to recognize exact `>glob` or `>minimatch` selectors after the run, **not CI-verified**. Full security/compatibility acceptance **BLOCKED** pending separately approved focused CI; one run only, no local app builds/tests or deployment. Exact evidence: `notes/P05-SEC-02.md`, `docs/P05-SEC-02.md`.
- Baseline `7655dbdcb48c49aab8f3bf97aab8f1867f129531`. Previous Run #88 security 0 Moderate/High/Critical; Login frozen/build/unit unexecuted due CI helper `>=` selector false-positive. Corrected parser is committed but not yet CI-verified.
- **Exact Scope Lock:** `tests/ci/transitive_override_contract.py` and `.gitea/workflows/p05-security-acceptance.yml` only if a NEW exact validator/CI defect is reproduced; `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST for evidence. All PNPM lock/config/manifests, original Login/UI/auth, Account Portal, ZITADEL backend, Compose, production and unrelated files read-only. Preserve untracked `AI_INSTRUCTIONS.md`.
## P05-OIDC-01 — Disposable Real OIDC Login/Session Acceptance (APPROVED 2026-11-22)
- Baseline `f423c696544f28a42d6a5d1ad0acfd88a3b6f56d`, prior Run #86 disposable backend, Run #87 Account and Run #89 Login build/security PASS. **Real OIDC positive callback/session still unverified**.
- Exact Write Scope: new `.gitea/workflows/p05-oidc-acceptance.yml`, focused `tests/ci/oidc_e2e/**` and narrow CI-only helpers, `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST and root navigation. Original P02 Compose/backend, original Login V2/auth UI, Account Portal Auth.js/UI, all package manifests/locks, production and unrelated files READ ONLY. Preserve untracked `AI_INSTRUCTIONS.md`.
- Pre-change plan `notes/P05-OIDC-01.md` documents official IAM_OWNER bootstrap PAT (not the Login-client PAT), disposable project/real OIDC Web client and human, original Login V2 Chromium password flow, Auth.js PKCE/state/nonce, positive Account API/session and anonymous/invalid negatives, and mandatory run-owned secret/Compose cleanup. No public host ports. Existing HTTP localhost issuer requires development **only in the disposable CI container**, not a production TLS acceptance.
- One manual Gitea Actions CI cycle; **no local app installs/builds/tests/dev servers or production deployment**, no fake login/session or identity bypass. Exact real job results required for PASS. `docs/P05-OIDC-01.md`, `project/OIDC-E2E-ARCHITECTURE.md`.
- Baseline `b78270e9d45c1764c5642024b8147885deaacde3`. Run #90 tested `cbcd60e`, four backend services healthy and host portless, but CI-only localhost:8080 sidecar not ready; project/client/user/browser tests **NOT RUN**; owned teardown **PASS**. Root cause not established by previous logs.
- Exact Write Scope: `tests/ci/oidc_e2e/run.sh`, justified `provision.py` and optional `cleanup.sh`, optional `.gitea/workflows/p05-oidc-acceptance.yml`, `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST only if required. Original backend/dev Compose, Login V2, Account Portal, manifests/locks, production and unrelated files READ-ONLY. Preserve untracked `AI_INSTRUCTIONS.md`.
- Pre-change `notes/P05-OIDC-02.md`: before provisioning probe private 127.0.0.1:80 proxy/Host HTTP 200; replace runtime `apk add` with published versioned `alpine/socat:1.8.1.3`, verify preinstalled entrypoint + digest and run by immutable digest; inspect sidecar state/exit and require private forwarded 127.0.0.1:8080 HTTP 200; fix only the provisioner's status-only readiness without touching official API/secret checks. Existing owned-only cleanup unmodified.
- **Actual single Gitea Run #91:** tested `4831165548feabc2c0a0d39d25c40e0d1bc23bb2`, overall **FAILURE**. 4-service backend health, no-host-ports, private Traefik:80 Host-routing HTTP 200, socat version/entrypoint/digest checks **PASS**. socat sidecar **exited (code 1)** before localhost:8080 readiness; no project/client/human or real Chromium/PKCE/callback/session tests executed. **Always-run owned cleanup PASS**. Root cause inside socat process not proven without safe startup stderr diagnostics. NO rerun, local app tests or production changes. Follow-up P05-OIDC-03 requires separate exact approval, not auth bypass. `notes/P05-OIDC-02.md`, `docs/P05-OIDC-02.md`.
## P05-OIDC-03 — Forwarder Process Diagnosis and Real OIDC Acceptance (APPROVED 2026-11-23)
- Baseline `5f542a6aa376d06ba2c1fd3d46835baae9b8654e`. Gitea Run #91 proved 4 healthy services, private proxy Host route and prebuilt socat digest PASS, but socat exited 1; project/client/human/browser NOT EXECUTED; cleanup PASS. Actual socat stderr root cause unverified.
- Exact write scope: `tests/ci/oidc_e2e/run.sh`, optional new `forwarder.py` because Run #91 proved socat unreliable; `provision.py` / `cleanup.sh` ONLY if a separately reproduced narrow defect; `notes/**`, `project/**`, relevant `docs/**` and associated README/MINIFEST navigation. Original backend/Compose, Login V2, Account Portal, browser scripts, manifests/lockfiles and production READ-ONLY. Preserve untracked `AI_INSTRUCTIONS.md`.
- Single CI-only run plan: start pinned socat for safe error classification before credentials; only if unhealthy, remove its run-labeled container and use official `python:3.12-alpine` resolved immutable digest, copying a transparent 127.0.0.1:8080 → 127.0.0.1:80 stdlib relay; fail closed on forwarded HTTP/Host readiness. Continue unchanged official provisioning, original Chromium password/PKCE/state/nonce/Auth.js callback/session/negative tests and mandatory owned cleanup. **ONE manual Gitea cycle, no local tests or production deployment; real PASS only on actual browser & cleanup evidence.**`notes/P05-OIDC-03.md`, `docs/P05-OIDC-03.md`.
- **One** Gitea Actions Run #90, job #197, **overall FAILURE**. Repo checkout/Docker preflight PASS, no published host ports PASS, official four-container disposable backend startup/health PASS.
- **Blocker:** private run-owned localhost:8080 forwarder did not become ready in bounded 70 seconds; no admin API project/client/human provisioning or Chromium PKCE/state/nonce/callback/session/negative tests were executed. Exact sidecar cause **unknown** with current suppressed diagnostics. **Interactive OIDC acceptance BLOCKED**.
- **Safety PASS:** mandatory `always()` cleanup step succeeded: `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`, `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`. No production users/secrets/ports/deployment affected.
- No local application tests/builds, no second Gitea run, no original backend/Login/Auth.js source/manifest edits. Next P05-OIDC-02 requires separate exact scope approval limited to CI-only forwarder readiness/observability, then one new isolated full OIDC run. Full evidence `notes/P05-OIDC-01.md`, operator guidance `docs/P05-OIDC-01.md`.