docs: close P05 backend CI acceptance with run 86 evidence

This commit is contained in:
Vib Tools committed 2026-11-22 05:53:38 -08:00
1 parent 03fb58954d
commit 1a602551ad
17 files changed
+78 -27

No files matched your search

+6 -6
View File
@@ -1,12 +1,12 @@
# ZitPlane - Actual feature availability / limitations
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**.
Snapshot: 2026-11-22, **Gitea P05-CI-03 Run #86 backend-only SUCCESS** on `03fb589`; Account/Login build tests had passed in Run #83. Live production and interactive authenticated OIDC still NOT verified. **SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION**.
| Feature | Source present | CI/build verified | Live/deployed |
| --- | --- | --- | --- |
| Official ZITADEL Go backend image configuration | Yes, P02 | Run #83 ZITADEL API healthy in disposable Docker; full startup/proxy/OIDC acceptance blocked | No |
| Local PostgreSQL and loopback Traefik stack | Yes, P02 | Run #83 Postgres healthy, Traefik host 8080 collision; DB restart untested | No |
| Official prebuilt Login V2 service in local Compose | Yes, P02 configuration | No | No |
| Official ZITADEL Go backend image configuration | Yes, P02 | **Run #86 PASS:** ZITADEL API healthy, local backend ready, OIDC discovery/JWKS | No |
| Local PostgreSQL and loopback Traefik stack | Yes, P02 | **Run #86 PASS:** Postgres restart persistence and portless CI Traefik healthy; developer PC stack not tested | No |
| Official prebuilt Login V2 service in local Compose | Yes, P02 configuration | **Run #86 PASS:** official Login V2 container healthy; interactive login flow not tested | No |
| Official Login V2 customisable source | Yes, P03 v4.20.4 | Run #81 build + 1219/1219 unit tests PASS; integration not verified | No |
| Login V2 signup/password/OTP/MFA/passkey/IDP source routes | Present upstream | Run #81 unit suite PASS; real account flows NOT tested | No |
| Custom Account Portal Next.js app | Yes, P04 | Run #83 npm ci/typecheck/Next production build PASS | No |
@@ -17,8 +17,8 @@ Snapshot: 2026-11-22, P05-CI-03 backend-only verification source prepared on bas
| Mutable profile editing / device sessions / identity deletion | No | N/A | No |
| 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 | 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 |
| Gitea Actions CI verification workflow | Yes, P05 manual dispatch | Run #83 full workflow 3 PASS / 1 FAIL; **Run #86 backend-only SUCCESS**, without rerunning other jobs | Not deployed |
| Gitea Actions CI and isolated integration tests | Backend-only workflow; interactive identity E2E remains absent | **Run #86 PASS:** disposable backend OIDC ready/discovery/JWKS, Postgres persistence, cleanup; authenticated user E2E pending | 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 |
+1 -1
View File
@@ -9,7 +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 |
| [P05-CI-03.md](P05-CI-03.md) | Isolated backend-only Gitea CI procedure, checks and exact run outcomes | P05-CI-03 / Run #86 SUCCESS |
| [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 |
+7 -3
View File
@@ -2,7 +2,7 @@
**Date:** 2026-11-22
**Approved baseline:** `485755800504a7dea6e4c303e6b39ec9cc610b54`
**Status:** Source prepared; no P05-CI-03 workflow run yet.
**Status:** Backend-only Gitea Run #86 SUCCESS — all scoped gates including cleanup CI-verified.
## Objective and user-visible effect
@@ -25,7 +25,7 @@ The runner needs its registered `ubuntu-latest` label, a functional Docker daemo
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.
**Backend-only acceptance is confirmed for Run #86**, with each check and the always-run cleanup step executed successfully. Do not extend this result to real login/MFA or production deployment.
## Out of scope / known boundaries
@@ -33,6 +33,10 @@ Account Portal real authenticated login/callback and protected positive session;
## 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.
**CI VERIFIED — SUCCESS:** [Gitea Run #86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86), tested `03fb58954dec886128a4011b6121754cbcdd79ff`, manual `workflow_dispatch` on `main`, started 2026-11-22 13:47:58 UTC, concluded SUCCESS 13:48:56 UTC. Job #184 and all four steps SUCCESS: Git prerequisite, checkout, isolated backend acceptance and always-cleanup.
**Actual PASS markers:** `ZITPLANE_DOCKER_DAEMON_PREFLIGHT_PASS`; 3/3 P02 focused tests; `ZITPLANE_CI_PORTLESS_CONFIG_PASS`; `ZITPLANE_FOUR_SERVICES_READY_PASS` (PostgreSQL, ZITADEL API, Login V2, Traefik running/healthy); `ZITPLANE_POSTGRES_RESTART_PERSISTENCE_PASS` (synthetic row remains after database restart); `ZITPLANE_OIDC_NEGATIVE_CONTRACTS_PASS`; `ZITPLANE_BACKEND_READY_PASS`; `ZITPLANE_OIDC_DISCOVERY_PASS` (issuer `http://localhost:8080`); `ZITPLANE_OIDC_JWKS_PASS`; `ZITPLANE_BACKEND_ACCEPTANCE_CHECKS_PASS`; `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS` (network, containers and volumes removed).
**Acceptance verdict: P05-CI-03 backend-only disposable CI acceptance PASS.** The original host port 8080 collision no longer occurred; proxy was verified portless and healthy. No real authenticated Account Portal session, Admin Console human login, OAuth callback, MFA/passkey or global logout E2E was tested. The previously triaged 18 Moderate Login advisory records and 1 Moderate Account package remain **OPEN**. Production deployment and the developer PC were untouched. Exactly one backend-only CI run executed; Account/Login build suites were not rerun. Final docs-only commit is **not** a retested SHA; the tested source SHA is `03fb589`.
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).
+1 -1
View File
@@ -51,7 +51,7 @@ Implement one explicitly approved phase at a time. Keep out-of-scope files, exis
- **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.
- **Gitea Actions Run #86 SUCCESS** on `03fb58954dec886128a4011b6121754cbcdd79ff`: portless effective config PASS, all four services ready, disposable PostgreSQL marker persisted after restart, ZITADEL ready/OIDC issuer/discovery/JWKS and negative contracts PASS, CI-owned network/containers/volumes cleanup verified PASS. No Account/Login build rerun, no local build/Docker. Full interactive OIDC login/MFA and Moderate dependencies remain outside this phase. Evidence: `notes/P05-CI-03.md`, `docs/P05-CI-03.md`.
## P05 - Full Integration (proposed, NOT approved)
Shared design system, production-safe Compose topology and verified Login/Account OIDC wiring. No live deployment; separate approval.
+3
View File
@@ -73,3 +73,6 @@ Refer to [FEATURES-STATUS.md](FEATURES-STATUS.md), [TROUBLESHOOTING.md](TROUBLES
## 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.**
**P05-CI-03 verified result:** Gitea [Run #86](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/86) **SUCCESS** on source SHA `03fb589`. It confirmed the portless CI backend configuration, four-service readiness, PostgreSQL marker persistence after restart, ZITADEL OIDC discovery/JWKS and complete CI-owned cleanup. This **does not** mean the developer PC or production Coolify instance is configured, nor does it prove an authenticated user login/MFA. The run did not repeat earlier Account/Login builds. See `docs/P05-CI-03.md` for evidence.
+5 -5
View File
@@ -1,11 +1,11 @@
# ZitPlane — Troubleshooting and safe diagnostics
**Scope:** Only describe issues the current source or recorded phase evidence supports. No live environment has been verified.
**Scope:** Only describe issues the current source or recorded phase evidence supports. Run #86 verified an isolated disposable backend, but no developer-PC environment or production deployment has been verified.
| Symptom | Known possible cause | Safe next action |
| --- | --- | --- |
| `docker` command not found | Docker CLI/Desktop was missing on the previously inspected Windows host during P02 | Install supported Docker Engine/Desktop and run only in a local disposable environment; do not treat a source manifest as runtime acceptance |
| `docker compose config` / `up` fails | Dev Compose, h2c proxy, dependencies and image pulls were never integration-tested | Review Compose output after an approved isolated CI/dev verification, without revealing secrets; inspect P02 evidence |
| `docker compose config` / `up` fails | Local machine Docker/config differences or occupied port may differ from validated CI stack | Gitea Run #86 verified isolated portless CI Compose; check environment-specific logs with secrets redacted; do not confuse its portless override with P02 local loopback Compose |
| Admin Console login fails | First-instance bootstrap, Login V2 container/PAT, auth proxy or credentials not validated | Verify local health, first-init logs and policy in a secret-safe environment; do not reinitialize volumes casually |
| Account Portal shows no page | App dependencies are not installed; no Account Portal image, runtime or domain is configured | Complete reviewed lockfile/build/CI and explicit integration phase before troubleshooting live UI |
| Redirect/callback error after future login | OIDC issuer/callback URL, client type/secret, proxy headers, PKCE/state or allowed redirect may mismatch | Compare exact configured origins and registered callback; never weaken checks or wildcard redirects |
@@ -22,11 +22,11 @@ Include environment (local disposable vs CI vs production), exact phase/commit,
## P05-CI-02 verification and error boundaries
- Prior Account Portal `TS2345` at `src/auth.ts(14,61)` in Gitea Run #81 was caused by the callback returning a JWT subject not statically narrowed to `string`. P05-CI-02 source narrows it with `typeof`; it is not considered fixed until CI typecheck/build passes.
- Previous Alpine backend checkout missed Git; Run #83 verified the fix. Postgres/ZITADEL API/prebuilt Login V2 became healthy, but the runner had host TCP 8080 allocated and Traefik could not start. A CI-only portless Compose override was added after Run #83; it is **not verified** until a separately approved run. Database restart/persistence and OIDC discovery were not reached.
- Prior Account Portal `TS2345` at `src/auth.ts(14,61)` in Gitea Run #81 was fixed by verified JWT subject narrowing; Gitea Run #83 Account Portal typecheck/build **PASS**.
- Previous Alpine backend checkout missed Git; Run #83 verified the fix. Run #83 also exposed an occupied shared-runner host TCP 8080. **Run #86 verified the portless CI Compose overlay**: all four services ready, disposable Postgres restart persistence, ZITADEL ready/OIDC discovery/JWKS and complete CI-only cleanup PASS. This does **not** prove the separate P02 local PC Compose or real user login.
- A green HIGH/CRITICAL advisory audit gate still allows Moderate findings; the P05-CI-02 registry detail report records IDs/package/fix separately, without package upgrades.
- CI negative access tests do not simulate real login; actual OIDC app registration/authorized login/MFA must receive separate approval.
## Known limitations
No live integration verification, Account Portal lockfile, CI pipeline, Coolify production deployment, tested authentication redirects or production support guarantees exist as of P04. Before adding any diagnostic workaround, consult the Scope Lock in `notes/` and preserve ZITADEL's security boundaries.
Account Portal and Login V2 build CI passed in Run #83, disposable backend acceptance passed in Run #86, and dependency lockfiles/workflows exist. **Real authenticated OIDC callback/positive session, MFA/passkey, Admin Console human login, production Coolify/TLS/backup and production support remain UNVERIFIED.** Preserve the Scope Lock in `notes/` and ZITADEL security boundaries.