ci: add isolated backend-only P05 runtime acceptance
This commit is contained in:
1 parent
4857558005
commit
03fb58954d
22 files changed
+370
-27
No files matched your search
@@ -1,6 +1,6 @@
|
||||
# ZitPlane - Actual feature availability / limitations
|
||||
|
||||
Snapshot: 2026-11-22, P05-CI-02 Gitea Run #83 on source SHA `c27fe3d` (3 PASS / 1 FAIL); post-run CI-only portless patch remains unverified. **SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION**.
|
||||
Snapshot: 2026-11-22, P05-CI-03 backend-only verification source prepared on baseline `4857558`; Gitea Run #83 (3 PASS / 1 FAIL) is historical. **P05-CI-03 run not yet executed.** **SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION**.
|
||||
|
||||
| Feature | Source present | CI/build verified | Live/deployed |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -18,7 +18,7 @@ Snapshot: 2026-11-22, P05-CI-02 Gitea Run #83 on source SHA `c27fe3d` (3 PASS /
|
||||
| Global ZITADEL SSO logout | No | N/A | No |
|
||||
| Subscriptions, payments and SaaS billing | Outside ZitPlane scope | N/A | No |
|
||||
| Gitea Actions CI verification workflow | Yes, P05 manual dispatch | Run #83: 3 PASS / 1 FAIL; Docker proxy 8080 collision, cleanup PASS | Not deployed |
|
||||
| Gitea Actions CI and isolated integration tests | Negative tests/ready/persistence probe source prepared; full interactive OIDC E2E absent | Run #83: Postgres/ZITADEL API/Login healthy; proxy port collision prevented persistence/OIDC smoke; runtime BLOCKED | No |
|
||||
| Gitea Actions CI and isolated integration tests | Backend-only manual workflow, portless/persistence/discovery/cleanup scripts prepared; interactive E2E absent | Run #83 historical: Postgres/ZITADEL API/Login healthy; full backend acceptance blocked pending P05-CI-03 | No |
|
||||
| Coolify production stack, TLS, routing and backups | No | No | No |
|
||||
| Public `auth.vib.tools/login` URL | Proposed only | No | No |
|
||||
| Public `account.vib.tools` account website | Proposed only | No | No |
|
||||
|
||||
@@ -9,6 +9,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [USER-GUIDE.md](USER-GUIDE.md) | Source-grounded Account Portal page/button-by-button manual | DOCS-01 / active; runtime pending |
|
||||
| [P05-CI-01.md](P05-CI-01.md) | Gitea Actions manual verification workflow, gates, limitations and real run evidence | P05-CI-01 / Run #81 complete, acceptance blocked |
|
||||
| [P05-CI-02.md](P05-CI-02.md) | TypeScript remediation, Gitea CI verification, dependency risk and isolation evidence | P05-CI-02 / run #83 done; Docker acceptance blocked |
|
||||
| [P05-CI-03.md](P05-CI-03.md) | Isolated backend-only Gitea CI procedure, checks and exact run outcomes | P05-CI-03 / acceptance pending |
|
||||
| [SETUP-GUIDE.md](SETUP-GUIDE.md) | Operator/developer prerequisites, configs, activation and safety | DOCS-01 / active; runtime pending |
|
||||
| [FEATURES-STATUS.md](FEATURES-STATUS.md) | Exact implemented/unavailable/unverified feature matrix | DOCS-01 / active |
|
||||
| [TROUBLESHOOTING.md](TROUBLESHOOTING.md) | Known blockers and safe diagnosis based on source status | DOCS-01 / active |
|
||||
|
||||
@@ -0,0 +1,38 @@
|
||||
# P05-CI-03 — Backend-only Gitea CI Acceptance
|
||||
|
||||
**Date:** 2026-11-22
|
||||
**Approved baseline:** `485755800504a7dea6e4c303e6b39ec9cc610b54`
|
||||
**Status:** Source prepared; no P05-CI-03 workflow run yet.
|
||||
|
||||
## Objective and user-visible effect
|
||||
|
||||
Verify the existing official ZITADEL v4.20.4 + PostgreSQL + prebuilt Login V2 + Traefik local development stack in an **isolated Gitea Actions runner**. This is NOT an application feature release or an authentication redesign. It does not start the app on your PC, configure public domains, modify credentials/users, or deploy anything.
|
||||
|
||||
## How to launch the backend-only workflow
|
||||
|
||||
In Gitea `vibtools/ZitPlane`, open **Actions → ZitPlane P05-CI-03 Backend Acceptance → Run workflow → main**. Only one manual `workflow_dispatch` is authorized for this phase. The new workflow is `.gitea/workflows/p05-backend-acceptance.yml`; prior Account and Login V2 build suites are deliberately **not rerun**.
|
||||
|
||||
The runner needs its registered `ubuntu-latest` label, a functional Docker daemon/socket, Docker Compose v2 with support for `!reset`, access to pinned image registries and enough storage/time for four images. Do not run it on shared hosts with existing `zitplane-backend-dev-internal` network or an identical CI Compose project name.
|
||||
|
||||
## Required verification
|
||||
|
||||
1. Git checkout / Docker Engine / Compose preflight; refuse existing named network, project containers, or named volumes.
|
||||
2. Generate fresh disposable local secrets in ignored `.env`. Merge the **read-only** P02 Compose with `tests/ci/compose.portless.override.yaml`; inspect effective proxy config to ensure **no host port publishing**, including TCP 8080.
|
||||
3. Start and wait for PostgreSQL, ZITADEL API, prebuilt Login V2 and Traefik. Confirm first three healthy and proxy running.
|
||||
4. Write synthetic marker in disposable Postgres `postgres` database; restart Postgres; check marker survives after health recovery.
|
||||
5. From a disposable probe container within the CI-owned Docker network, check `/debug/ready`, exact local issuer `http://localhost:8080`, OIDC discovery endpoint URLs and a nonempty JWKS. Run malformed issuer/JWKS negative fixtures.
|
||||
6. In a separate always-run step, stop **only CI-owned Compose project**, remove its disposable volumes, then check that no CI network/container/volume remains. Report any cleanup failure instead of claiming success.
|
||||
|
||||
Expected markers: `ZITPLANE_CI_PORTLESS_CONFIG_PASS`, `ZITPLANE_FOUR_SERVICES_READY_PASS`, `ZITPLANE_POSTGRES_RESTART_PERSISTENCE_PASS`, `ZITPLANE_OIDC_NEGATIVE_CONTRACTS_PASS`, `ZITPLANE_BACKEND_OIDC_READY_DISCOVERY_JWKS_PASS`, `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`.
|
||||
|
||||
**Do not claim backend acceptance unless each required check actually executes and passes.** Before the run, all are PENDING.
|
||||
|
||||
## Out of scope / known boundaries
|
||||
|
||||
Account Portal real authenticated login/callback and protected positive session; ZITADEL Admin Console human login, MFA, passkey, global SSO logout; Moderate dependency remediation (18 Login records plus 1 Account affected package); production ZITADEL, Coolify, DNS, TLS, backups and user data. Existing P02 developer Compose, Login V2 source and Account Portal must remain unchanged.
|
||||
|
||||
## Actual acceptance ledger
|
||||
|
||||
**PENDING:** After the single Gitea run, record run ID, tested source SHA, job conclusion, each marker, Docker service state, Postgres persistence, exact issuer/JWKS results, cleanup outcome and reproduced blockers. If any gate fails, label acceptance BLOCKED/FAILED and propose a focused next phase. Gitea workflow source-only changes or historical P05 runs are not proof of this phase.
|
||||
|
||||
Developer details: [project/CI-ARCHITECTURE.md](../project/CI-ARCHITECTURE.md). Pre-change plan and final log: [notes/P05-CI-03.md](../notes/P05-CI-03.md).
|
||||
@@ -46,6 +46,13 @@ Implement one explicitly approved phase at a time. Keep out-of-scope files, exis
|
||||
- B01 Auth.js TypeScript TS2345: real subject string narrowing, preserve PKCE/state/nonce, expiry and protected identity guard. B02: verify in-CI Docker checkout, disposable ZITADEL, PostgreSQL restart persistence and OIDC discovery/JWKS. B03: report real Moderate advisory IDs/package/fix; HIGH+ security threshold remains a failure gate. B04: negative OIDC metadata and anonymous Account Portal checks, with interactive user E2E explicitly deferred.
|
||||
- **One** manual Gitea Run #83: Account Portal, Login V2, security gates PASS; Docker health progressed to PostgreSQL/ZITADEL API/Login V2 healthy, but runner host 8080 collision blocked proxy, database persistence and discovery. Full CI acceptance BLOCKED. Post-run CI-only `tests/ci/compose.portless.override.yaml` clears inherited host port, **not CI-verified**. 18 Moderate Login + 1 Moderate Account audit record still open, no package changes. Exact evidence in `notes/P05-CI-02.md`, `docs/P05-CI-02.md`.
|
||||
|
||||
## P05-CI-03 - Backend Runtime Final Acceptance (APPROVED 2026-11-22)
|
||||
- Baseline `485755800504a7dea6e4c303e6b39ec9cc610b54`; prior Run #83 had 3 job PASS and backend FAIL due to runner host TCP 8080 collision.
|
||||
- **Exact Write Scope:** optional `.gitea/workflows/p05-backend-acceptance.yml`, narrow existing P05 workflow if justified, focused `tests/ci/**`, notes/project/docs, associated workflow README/MINIFEST and root navigation if needed. Core backend, developer Compose, Login V2, Account Portal, dependencies/locks and production config all READ ONLY.
|
||||
- **Manual backend-only** Gitea Actions acceptance: effective Compose proxy portless check, four-service health, disposable Postgres restart marker persistence, ZITADEL readiness/discovery/JWKS, malformed issuer/JWKS negative contracts and verified CI-only cleanup.
|
||||
- One focused isolated run after source commit/push, no local test/build/Docker, no repeated Account/Login suites, no real users/secrets or production deployment. Full interactive login/MFA remains a separate phase.
|
||||
- Evidence: `notes/P05-CI-03.md`, `docs/P05-CI-03.md`. Backend PASS only after all gates and cleanup are proven in Gitea.
|
||||
|
||||
## P05 - Full Integration (proposed, NOT approved)
|
||||
Shared design system, production-safe Compose topology and verified Login/Account OIDC wiring. No live deployment; separate approval.
|
||||
|
||||
|
||||
+2
-2
@@ -2,7 +2,7 @@
|
||||
|
||||
**Purpose:** the Git-tracked, **user-facing** knowledge base: real functions, pages, controls, account behavior, prerequisites, how to use each available capability, troubleshooting and limitations.
|
||||
|
||||
**Current product status:** P02 local backend Compose, P03 imported Login V2 source, P04 account portal source. No integrated deployed product yet; Account Portal dependency installs/builds, login and health checks remain unverified. **Do not claim pages/buttons are working in production merely because source exists.**
|
||||
**Current product status:** P02 local backend Compose, P03 imported Login V2 source, P04 account portal source. No integrated deployed product yet; Gitea Run #83 verified Account Portal and Login V2 builds, but real user login and full backend runtime acceptance remain unverified. **Do not claim pages/buttons are working in production merely because source exists.**
|
||||
|
||||
## What to read
|
||||
|
||||
@@ -26,4 +26,4 @@
|
||||
Full update policy is in root [AGENTS.md](../AGENTS.md). A list of available docs is in [MINIFEST.md](MINIFEST.md).
|
||||
|
||||
|
||||
For manual Gitea runner verification and its limitations, see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
For backend-only isolated runtime verification see [P05-CI-03.md](P05-CI-03.md); for initial full workflow and its limitations see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
@@ -68,3 +68,8 @@ Refer to [FEATURES-STATUS.md](FEATURES-STATUS.md), [TROUBLESHOOTING.md](TROUBLES
|
||||
|
||||
|
||||
**P05-CI-02 status (2026-11-22):** Run #83 verified Account Portal build/typecheck and negative auth checks, Login V2 1219/1219 unit tests and a successful high/critical dependency threshold (Moderate issues still open). Disposable Postgres/ZITADEL API/Login V2 became healthy, but host TCP 8080 prevented proxy startup; cleanup succeeded. The workflow now has a **CI-only** portless override to allow internal-Docker-network probing on a shared runner, **not yet rerun**. See `docs/P05-CI-02.md`. This is not a production deployment guide.
|
||||
|
||||
|
||||
## P05-CI-03 backend-only runtime verification (Gitea only)
|
||||
|
||||
In Gitea `vibtools/ZitPlane` → **Actions** → **ZitPlane P05-CI-03 Backend Acceptance** → **Run workflow** → `main`. It uses the existing `ubuntu-latest` Linux Docker-capable runner; no Account or Login V2 production build suites are rerun. All credentials are generated in the disposable runner and are never used for production accounts. It checks portless effective Compose, four container states, a synthetic PostgreSQL restart marker, backend readiness, OIDC issuer/discovery and JWKS, and always-owned-resource cleanup. Results must come from the exact Gitea Actions run, not source presence. See `docs/P05-CI-03.md`. **This is not full interactive login, Coolify or production deployment.**
|
||||
Reference in new issue
Block a user