Files

CI workflows - manual verification only

P05-CI-01 introduced p05-ci.yml; P05-CI-03 adds a separate backend-only p05-backend-acceptance.yml. Both use manual workflow_dispatch. Do not enable automatic push/PR builds with Docker access without a fresh security review.

Job responsibilities:

  1. account: reproducible Account Portal npm ci, TypeScript, Next.js production build and dependency advisory check.
  2. login: pinned pnpm workspace frozen install, proto/client/Login build and upstream unit checks.
  3. backend: install Git before Alpine checkout, Docker daemon preflight, disposable local-only P02 ZITADEL Compose, ready/discovery/JWKS smoke and safe cleanup. Full interactive OIDC login is NOT certified.

P05-CI-02 additions: Account Portal CI negative route/API smoke, npm/pnpm structured Moderate advisory detail, and disposable Postgres restart persistence plus stronger OIDC issuer/JWKS negative checks. Run #83 passed Account, Login V2 and Security jobs but backend proxy bind to shared host port 8080 failed after Postgres/ZITADEL/Login healthy. Post-run source fix: all backend Compose calls include tests/ci/compose.portless.override.yaml (ports: !reset []), config rejects any published proxy port; this is not CI-verified. Full authenticated user sign-in/MFA remains deferred.

P05-SEC-02: Existing p05-security-acceptance.yml manual login_only=true correctly SKIPPED Account jobs in Run #88. Login production audit PASS with 0 Moderate/High/Critical, but new CI contract helper falsely matched >= ranges and blocked the separate Login frozen/build/unit job before install. After Run #88, parser narrowed to exact >glob/>minimatch selectors; not CI-verified. Default login_only=false still preserves the full Account/Login workflow. No second P05-SEC-02 run or production deployment. See docs/P05-SEC-02.md.

P05-SEC-01: .gitea/workflows/p05-security-acceptance.yml is manual-only with independent Account frozen build + negative access regressions, Login frozen Nx build + Vitest, Account production audit and Login production audit. Run #87: Account build, Login build/1219 unit tests, Account security audit PASS; Login audit FAIL on 2 Moderate transitive glob/minimatch findings (0 High/Critical) as required by strict tests/ci/security_advisory_gate.py. No source auth changes or production deployment. See docs/P05-SEC-01.md.

P05-CI-03: p05-backend-acceptance.yml runs only the isolated backend job with tests/ci/backend_acceptance.sh and always-run backend_cleanup.sh. Gitea Run #86 SUCCESS on 03fb589: portless config, all four services, restart persistence, ready/discovery/JWKS, negative cases and complete cleanup passed. No Account/Login build rerun; no production. See docs/P05-CI-03.md.

Run #81 evidence: backend's first revision failed during checkout because Alpine had no Git. Added a pre-checkout Git installation afterward; the corrected backend job remains UNVERIFIED until a separately approved CI rerun. See docs/P05-CI-01.md.

A green job indicates only its executed steps. Full CI acceptance also needs end-to-end OIDC session/callback, real login/MFA, admin console and session controls in a disposable environment, documented separately.

See notes/P05-CI-01.md and tests/ci/.

P05-SEC-02-A01 ACCEPTED: Manual Login-only Run #89, tested ff4c58ed861474061c8f045be3a9f0752caf6ca0, overall SUCCESS. Login frozen install/build/upstream 1219/1219 unit regressions job #194 PASS, Login production zero-Moderate/High/Critical audit job #196 PASS, Account jobs #193/#195 intentionally SKIPPED. Corrected transitive_override_contract.py verified exact seven parent overrides without false-positive >= parsing; no dependency lock/manifest/source change. Human OIDC/MFA remains unverified.

P05-OIDC-01: New p05-oidc-acceptance.yml is manual-only with one disposable Docker job and always() owned cleanup. New tests/ci/oidc_e2e/** uses a short-lived ZITADEL IAM_OWNER PAT for official project/real client/test human provisioning, private portless browser network, original Login V2 Chromium username/password and real Auth.js callback/positive protected identity/negative access, with strict run-labeled browser/secret/Compose teardown. No Account/Login source, package, P02 developer Compose, real user or production change. Actual Gitea runtime result pending, no false PASS. See docs/P05-OIDC-01.md and project/OIDC-E2E-ARCHITECTURE.md.

P05-OIDC-01 final result: Gitea Run #90 on cbcd60e FAILURE. Manual-only P02 backend 4/4 healthy and host-portless PASS; run-labeled private localhost:8080 TCP forwarder readiness FAILED before any official OIDC client/human provisioning and before Chromium browser/auth callback. always() cleanup PASS (ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS, ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS). No repeat CI cycle. Next narrowly approved P05-OIDC-02 needed to determine whether sidecar exited, failed installing socat or could not bind/forward/rout; no authenticated OIDC E2E proof.