docs(ci): record OIDC run 93 queued with no executed gates

This commit is contained in:
Vib Tools committed 2026-11-22 10:13:54 -08:00
1 parent 7b80f411b2
commit 09add5345a
12 files changed
+36 -7

No files matched your search

+3
View File
@@ -42,3 +42,6 @@ Future feature additions need an evidence-backed status update here, an exact de
**P05-OIDC-03 planned CI acceptance:** A same-run, safe error-class socat diagnosis and digest-verified Python stdlib private TCP fallback is prepared. The prior Run #91 verified private proxy route and cleanup but **not** any client/user/browser login. Full authenticated OIDC positive/negative flow remains **UNVERIFIED** until one actual Gitea run reaches and passes those contracts. MFA/passkeys and production TLS remain out of scope.
**P05-OIDC-03 current CI evidence:** [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93) was dispatched on exact source `7b80f411b2981e2274d171c12596301ed757b768` but remains **QUEUED** at the last check; all actual OIDC/browser/fallback/cleanup checks **NOT EXECUTED**. The Python relay exists in source but its runtime compatibility is **NOT VERIFIED**. Run #91 remains last terminal evidence. No production login or MFA claimed.
+1 -1
View File
@@ -15,7 +15,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
| [P05-SEC-02-A01.md](P05-SEC-02-A01.md) | Gitea-only Login V2 full frozen-install/build/units/zero-advisory acceptance and status | P05-SEC-02-A01 / Run #89 SUCCESS |
| [P05-OIDC-01.md](P05-OIDC-01.md) | How isolated real OIDC Login V2 browser/session checks work; real CI status/limitations | P05-OIDC-01 / Run #90 BLOCKED before provisioning; cleanup PASS |
| [P05-OIDC-02.md](P05-OIDC-02.md) | Pinned prebuilt forwarder, safe private HTTP diagnostics and actual Run #91 evidence | P05-OIDC-02 / real OIDC BLOCKED by forwarder exit 1, cleanup PASS |
| [P05-OIDC-03.md](P05-OIDC-03.md) | Same-run allowlisted socat startup evidence, immutable Python TCP fallback and real OIDC acceptance | P05-OIDC-03 / CI pending |
| [P05-OIDC-03.md](P05-OIDC-03.md) | Same-run socat classification, private Python fallback and exact Gitea status | P05-OIDC-03 / Run #93 QUEUED, no terminal result |
| [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 |
+9
View File
@@ -18,3 +18,12 @@ The manual `.gitea/workflows/p05-oidc-acceptance.yml` and original backend/Login
**Full real-browser acceptance requires one actual successful Gitea CI run** proving the private network, official disposable ZITADEL project/client/verified human provisioning, real original Login V2 password, code + PKCE S256/state/nonce and Auth.js callback, authenticated subject and protected Account pages/API, anonymous/invalid callback rejection, local logout and complete `always()` cleanup. A forwarder-only pass or a mere discovery/JWKS response cannot be called authenticated login.
**No** local application tests/builds/Docker, real users, production HTTPS, MFA/passkeys, tags or deployment. See `notes/P05-OIDC-03.md` for pre-change scope and exact actual run ledger; `project/OIDC-E2E-ARCHITECTURE.md` for source/network boundaries.
## Real execution status — Gitea Run #93 queued, not yet accepted
A single approved [Gitea Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93) was dispatched on `main` using tested source SHA `7b80f411b2981e2274d171c12596301ed757b768`. Its job #206 was still **QUEUED** at the last status inspection; **no runner steps executed and no terminal conclusion exists**.
Therefore socat startup classification, official Python digest fallback, private HTTP 200, ZITADEL project/client/human creation, real Chromium Login V2/PKCE/state/nonce/Auth.js callback, protected API/session, negative cases, and mandatory cleanup are all **NOT EXECUTED / UNVERIFIED in Run #93**. This is **not** evidence of a source regression or successful OIDC. **No second CI run** is permitted by this phase.
Next work is read-only runner scheduling/status inspection plus **terminal evidence collection from the same Run #93** once it actually executes, then strict documentation-only closure. Original Login/Account/auth/Compose and dependencies remain unchanged; `AI_INSTRUCTIONS.md` was preserved. See `notes/P05-OIDC-03.md` for exact pre-edit Scope Lock and live snapshot.
+1 -1
View File
@@ -85,7 +85,7 @@ Implement one explicitly approved phase at a time. Keep out-of-scope files, exis
## P05-OIDC-03 — Forwarder Process Diagnosis and Real OIDC Acceptance (APPROVED 2026-11-23)
- Baseline `5f542a6aa376d06ba2c1fd3d46835baae9b8654e`. Gitea Run #91 proved 4 healthy services, private proxy Host route and prebuilt socat digest PASS, but socat exited 1; project/client/human/browser NOT EXECUTED; cleanup PASS. Actual socat stderr root cause unverified.
- Exact write scope: `tests/ci/oidc_e2e/run.sh`, optional new `forwarder.py` because Run #91 proved socat unreliable; `provision.py` / `cleanup.sh` ONLY if a separately reproduced narrow defect; `notes/**`, `project/**`, relevant `docs/**` and associated README/MINIFEST navigation. Original backend/Compose, Login V2, Account Portal, browser scripts, manifests/lockfiles and production READ-ONLY. Preserve untracked `AI_INSTRUCTIONS.md`.
- Single CI-only run plan: start pinned socat for safe error classification before credentials; only if unhealthy, remove its run-labeled container and use official `python:3.12-alpine` resolved immutable digest, copying a transparent 127.0.0.1:8080 → 127.0.0.1:80 stdlib relay; fail closed on forwarded HTTP/Host readiness. Continue unchanged official provisioning, original Chromium password/PKCE/state/nonce/Auth.js callback/session/negative tests and mandatory owned cleanup. **ONE manual Gitea cycle, no local tests or production deployment; real PASS only on actual browser & cleanup evidence.** `notes/P05-OIDC-03.md`, `docs/P05-OIDC-03.md`.
- **Actual dispatch:** one manual Gitea Run #93, tested SHA `7b80f411b2981e2274d171c12596301ed757b768`, job #206 **QUEUED at last inspection**, no job start, no steps/cleanup and no conclusion. Nothing authenticated verified yet. Source prepared with allowlisted socat startup error classification and one same-run immutable official Python TCP fallback; original provisioning/Chromium/PKCE/state/nonce/Account and cleanup untouched. **No second dispatch**, local app tests or production deployment. Read-only terminal evidence from this same run must determine PASS/FAIL. `notes/P05-OIDC-03.md`, `docs/P05-OIDC-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.