Files
ZitPlane/project/CI-ARCHITECTURE.md
T

3.9 KiB

ZitPlane P05-CI-01 — Gitea Actions verification architecture

Status: source implemented, CI run result pending. Approved baseline: 7ecf53169776cc7f08af3dde6fe4b4492acf3ea1 (2026-11-22).

Exact job map

Job Runner / source What PASS means Not covered
account ubuntu-latest, node:22-bookworm; users/ui/ Structural guard + npm ci, tsc --noEmit, Next standalone production build Real login/redirect, live Account Portal
login ubuntu-latest, node:22-bookworm; auth/ui/v2/ Frozen pnpm install, Nx proto/client/login build and original Login unit suite Interactive admin/password/MFA/SSO integration
security ubuntu-latest, node:22-bookworm NPM and pnpm production dependency advisories at HIGH+ thresholds triaged by runner registry License/legal or full application security proof
backend ubuntu-latest, node:22-alpine; deployment/docker/compose.backend.dev.yaml read-only Docker daemon preflight, Python helper contracts, disposable ZITADEL stack, readiness, OIDC discovery and JWKS Portal OIDC callback, MFA, live account session, production TLS

All jobs use the previously seen Gitea standard ubuntu-latest runner label; no separate runner is created or installed. A failed runner capability is a BLOCKED gate, never a PASS. Docker job must not run from an untrusted pull request; the workflow is workflow_dispatch only.

Dependency/root cause fixes

  • auth/ui/v2/pnpm-workspace.yaml has only the 3 actually imported packages. P03's original pnpm-lock.yaml retains exact packages:/snapshots: resolution graph; 4 missing-upstream importers were removed, 4 present importers retained.
  • Account Portal package-lock v3 generated using local npm install --package-lock-only --ignore-scripts --no-audit --no-fund --engine-strict, not an install/test/build. Root package manifest matches lock manifest.
  • Login CI sets up pinned pnpm 10.30.3, runs --frozen-lockfile and the upstream Nx dependency graph; no upstream UI/auth logic was modified.
  • Account CI uses npm ci only from committed lock, plus TS + production Next build. No automatically loosened package versions or npm install fallback.
  • Security jobs audit dependency advisory metadata on the runner. Any failure is reported verbatim with severity/package/version; no blind package updates.

Disposable backend safety and behavior

The P02 Compose has a fixed named network zitplane-backend-dev-internal and loopback-only 127.0.0.1:8080. CI refuses to start if that network already exists. It generates independent random .env in runner checkout and uses unique Compose project name zitplane-p05-${GITHUB_RUN_ID}. A marker is written only after the network absence check; cleanup uses that exact Compose project, deletes its ephemeral volumes, and removes its temporary credentials. It never connects to auth.vib.tools, account.vib.tools or any production database.

tests/ci/oidc_discovery.py probes ready/discovery/JWKS inside disposable Docker network only, avoiding exposing admin PATs. OIDC full user-session acceptance is explicitly NOT VERIFIED: P05 does not provision a disposable confidential OIDC app, fake user or Session API script. A 200 readiness/discovery alone does not constitute user login, MFA, PKCE callback, protected account route or logout acceptance.

Future gates

  1. Document actual Gitea runner job results and exact failure/line in notes/P05-CI-01.md and docs/P05-CI-01.md.
  2. If any job fails, keep immutable logged evidence; fix only reproduced narrow defects with separate approval if outside P05 Scope Lock.
  3. Provide disposable OIDC client/user provisioning and Account Portal auth/session lifecycle tests in a narrow separately approved integration phase.
  4. Production Docker/Coolify/TLS and DNS are out of scope.

Reference: notes/P05-CI-01.md, docs/PHASES.md, .gitea/workflows/p05-ci.yml, tests/ci/.