Files

4.1 KiB

P05-CI-01 - Gitea Actions verification

Date: 2026-11-22 Source baseline: 7ecf53169776cc7f08af3dde6fe4b4492acf3ea1 State: SOURCE IMPLEMENTED; GITEA RUN #81 FINISHED (OVERALL FAILURE, 2 PASS / 2 FAIL). Checkout prerequisite source corrected after Run #81 without rerunning; corrected source remains unverified.

How to run

In Gitea vibtools/ZitPlane, open Actions > ZitPlane P05 CI Verification > Run workflow, select main. This is manual only and requires an existing ubuntu-latest runner with working Docker support. The workflow file is .gitea/workflows/p05-ci.yml.

No local PC tests, builds, Docker or dev servers are performed by this phase. The workflow jobs execute only inside Gitea runner job containers.

Gates

  • account - Account Portal pinned npm lock, dependency installation, TypeScript and Next.js production build.
  • login - upstream source's pinned pnpm frozen workspace install, Nx proto/client/Login V2 build and upstream Login unit suite.
  • security - npm/pnpm production advisory triage; HIGH/CRITICAL advisories fail the gate.
  • backend - disposable Docker preflight, P02 Python helper contracts, ZITADEL/PostgreSQL/prebuilt Login/Traefik stack and OIDC discovery/JWKS, then cleanup.

Not proved even by all four jobs passing: complete interactive Account Portal OIDC callback/session, new user signup/MFA/passkeys, Admin Console login, global logout, production host/TLS/routing. These need a separate explicitly approved and fully disposable end-to-end integration test phase.

Safety

Runner creates ephemeral secrets only. No production credentials or live user data. CI refuses to touch an existing Docker network with the fixed P02 name. Always cleanup is configured; if the runner itself crashes, disposable resources may require operator cleanup after confirming exact project ownership. No push/PR trigger, publish, release or deploy.

Gitea verification results - ONE focused cycle

  • Run: #81, workflow_dispatch on main, SHA 42b79362c13b9dbb07f85a58ad278742d91b1f5b. Overall conclusion: FAILURE (2026-11-22).
  • Account job #165: FAILED. Checkout and three source/lock/OIDC-guard structural checks PASS; npm ci installed 38 packages. Then npm run typecheck failed at users/ui/src/auth.ts(14,61), TypeScript TS2345, because inferred session.user.id callback return type is not assignable to the required string session identity type. Next production build was NOT RUN. This authentication-code fix is outside P05 write scope.
  • Login job #166: PASS. Pinned pnpm 10.30.3 frozen install PASS; Nx proto/client/Login production build/standalone artifact PASS; Vitest 84/84 files, 1219/1219 tests PASS.
  • Security job #167: PASS at high/critical threshold only. Account npm audit and Login production pnpm audit completed successfully at severity high; however Login audit also reports 18 MODERATE vulnerabilities without package-level triage in the current workflow. Those remain OPEN and require a separately reviewed advisory report.
  • Backend job #168: FAILED before tests. node:22-alpine lacks Git before actions/checkout@v4. Action attempted Gitea REST-archive fallback, returned repeated Not found; Docker preflight, live backend, OIDC/JWKS smoke and persistence were NOT EXECUTED. Always-cleanup step PASS. The workflow source was minimally corrected after the failed run with a pre-checkout apk add --no-cache git; it has not been CI-verified.
  • No second CI run, local build or local application test was executed.

Acceptance verdict: P05 CI foundation source exists and two CI jobs passed, but FULL PHASE ACCEPTANCE BLOCKED by Account TypeScript defect, missing Docker runtime verification, absent real user OIDC E2E, and 18 moderate advisory findings. No Coolify/prod deployment.

Read notes/P05-CI-01.md for scope and next-phase defect separation. Do not interpret a green Login test job as the complete central authentication platform being production-ready.

Developer map: project/CI-ARCHITECTURE.md. Phase notes and root-cause evidence: notes/P05-CI-01.md.