Files
ZitPlane/notes/P05-CI-01.md
T

44 lines
4.0 KiB
Markdown

# P05-CI-01 — Gitea Actions Verification Foundation
Date: 2026-11-22
Status: APPROVED / IN PROGRESS — before code edits
Baseline: `7ecf53169776cc7f08af3dde6fe4b4492acf3ea1` (local and Gitea `main` matched before implementation)
User approval: 2026-11-22 P05-CI-01 explicit instruction. One focused Gitea Actions acceptance cycle, Git commit/push; **no local tests/builds/dev services**.
## Exact write scope
- `.gitea/**` — new workflow plus README/MINIFEST for first-party directories
- `tests/ci/**` — isolated runner verification utilities and folder docs
- `users/ui/package.json` and `users/ui/package-lock.json` — only justified dependency/lock corrections
- `auth/ui/v2/pnpm-workspace.yaml` and `auth/ui/v2/pnpm-lock.yaml` — only slim workspace reconciliation
- `notes/**`, `project/**`, relevant `docs/**`, `README.md` — evidence, manifests and documentation
- Existing `tests/README.md` is **not** approved for write; document test folder in its nested `tests/ci/` instead.
- `deployment/docker/compose.backend.dev.yaml` and `core/backend/zitadel/dev.py` remain **read-only**. Any reproduced runtime bug here requires a separate approved exception.
Excluded: application Login V2 source logic, account portal auth/session/pages, UI redesign, production deployment, release/tag, real credentials, production data, local build/test, unrelated untracked `AI_INSTRUCTIONS.md`.
## Pre-change root cause evidence
1. Gitea `vibtools/ZitPlane`: Actions enabled but **0 workflows**. Existing Gitea runner success in the sister repo DataStack on `ubuntu-latest` for CLI/Docker workflows; ZitPlane runner capability still must be checked on its own run.
2. P03 slim Login source: root `auth/ui/v2/pnpm-workspace.yaml` still references upstream `console`, `tests/*`, `deploy/compose` etc; only `apps/login`, `packages/zitadel-client`, `packages/zitadel-proto` imported. Original `pnpm-lock.yaml` contains absent importers (`apps/docs` etc), likely requires lockfile-safe reconciliation.
3. `auth/ui/v2/apps/login/project.json` declares build dependencies on generated proto and client; explicit reproducible install/build/verification must preserve this dependency graph.
4. `users/ui/package.json` pins Next/React/Auth.js and lacks `package-lock.json`; CI cannot use `npm ci` until a reviewed lockfile exists.
5. P02 dev Compose defines PostgreSQL, official ZITADEL API, prebuilt Login V2 and Traefik; **Docker/health/SSO not previously tested**.
6. P04 Auth.js OIDC route, session expiry, protected pages, local-only sign-out are **source-only**, not integrated with a disposable ZITADEL instance. Avoid simulated PASS or real-user tokens.
## Execution plan
A. Create first-party `.gitea/`, `.gitea/workflows/`, `tests/ci/` README/MINIFEST files and single manually dispatched `p05-ci.yml` with a preflight gate, account reproducible build, Login V2 frozen build, targeted dependency triage, disposable backend smoke and optional OIDC acceptance with explicit prerequisites.
B. Reconcile only necessary workspace/lockfile inputs. Lockfiles are generated **without executing local builds/tests**. Any unsupported reproducibility or failed generation must become a clear BLOCKED condition, not a silent unlocked install.
C. Runner job uses transient secrets, loopback-only services, disposable Docker Compose project/volumes, and always cleanup; never touches live ZITADEL domains or production data.
D. Stage exact paths, audit source scope and sensitive files, commit locally, push `main`; dispatch **one** workflow run; read run/jobs/log evidence and document exact results/remaining blockers.
E. Final evidence, notes/project/docs/manifests synchronized. If CI fails, record failure and propose a new phase/scope instead of unlimited edit/retry loops.
## Acceptance policy
Only call a gate PASS if real Gitea Actions job step succeeded. Docker/OIDC requiring missing capability must state BLOCKED. No production-ready claim until all required gates succeed. Version/security advisories: report exact package/version/severity/decision; do not apply blind dependency updates.