| `/signin` | `users/ui/src/app/signin/page.tsx` | `Continue with ZITADEL` button submits server action; OIDC redirect; `Back to account home` link | Source implemented; untested |
| `/account` | `users/ui/src/app/(protected)/account/page.tsx` | Shows identity-backed greeting, cards linking to profile/security, informational note and review link | Source implemented; untested |
| `/account/profile` | `users/ui/src/app/(protected)/account/profile/page.tsx` | Read-only display name, email, immutable ZITADEL user ID; link to ZITADEL self-service if available | Source implemented; untested |
| `Open ZITADEL account settings` | Profile link -> derived issuer `/ui/console/users/me`; policy/route availability not verified |
| `Open central security settings` | Security link -> same ZITADEL self-service location, conditional upon access |
| Responsive UI | `users/ui/src/styles/globals.css` CSS media query at 760px, prefers-color-scheme dark |
## ZITADEL login/source functionality
The upstream Login V2 app is **imported** with its original page source, not remapped or redesigned. Actual source route folders at `auth/ui/v2/apps/login/src/app/(login)/` include `loginname`, `password`, `register`, `verify`, `otp/[method]`, `mfa`, `passkey`, `u2f`, `authenticator`, `logout`, `idp`, `accounts`, `device`, and their nested steps where present. These are **upstream source files only**; ZitPlane has not independently verified each flow, field or UI action. See `auth/ui/v2/apps/login/src/app` and upstream acceptance tests for implementation details.
P02 also configures an official prebuilt Login UI container for ZITADEL Console sign-in. This is **distinct from** compiling the imported workspace.
## Not implemented (do not advertise as working)
Custom profile edits, password/MFA/passkey changes inside the portal, sessions/device management UI, federated logout, app marketplace, subscription/billing, product entitlements, production domains, production Docker/Coolify integration, CI workflow, release, E2E verification, and clean `auth.vib.tools/login` URL rewrite.
## Feature-update contract
For every future page/feature change, record exact route/file, action, data source, guards, validation, errors, dependency version, accessibility details, status (proposed/source/CI verified/deployed), and phase/commit. Update user button-by-button guidance in `docs/USER-GUIDE.md` alongside this register.
New manually dispatched workflow `.gitea/workflows/p05-ci.yml` defines four isolated runner gates: Account Portal reproducible dependency install/build, official Login V2 frozen install/build/unit, dependency security advisory triage, and disposable Docker ZITADEL/OIDC discovery smoke. Exact verification scripts reside at `tests/ci/source_contract.py` and `tests/ci/oidc_discovery.py`. The full Account Portal interactive OIDC callback/session/SSO flow is **not implemented as a CI test**; it remains a pending acceptance gate. Status must be updated from the actual Gitea run report in `notes/P05-CI-01.md`.
## P05-CI-03 verified backend runtime, not a user page
Gitea [Run #86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86) verified P02's PostgreSQL, ZITADEL API, prebuilt Login V2 and Traefik running/healthy in a disposable runner, including restart persistence, exact `http://localhost:8080` OIDC issuer discovery/JWKS, negative metadata fixtures and cleanup. This is **not** verification of a human pressing Login/Sign Up/MFA or any positive Account Portal session. Those remain **unverified** and must be documented when future phases implement isolated real-identity E2E.