docs(ci): audit existing run 93 queue and unexecuted OIDC gates
This commit is contained in:
1 parent
09add5345a
commit
88911c5d68
13 files changed
+109
-8
No files matched your search
@@ -15,7 +15,7 @@ Compact, developer-friendly monorepo for a central identity service, a branded l
|
||||
- **P05-SEC-02-A01:** **Gitea Run #89 SUCCESS** on `ff4c58e`: corrected exact override contract PASS, pinned PNPM frozen install PASS, official Login V2 standalone build PASS, upstream Vitest **1219/1219 PASS**, Login production audit **0 Moderate/High/Critical**; Account jobs skipped. **Dependency security/build unit acceptance complete; real user OIDC/MFA E2E and production integration NOT verified**. See `docs/P05-SEC-02-A01.md`.
|
||||
- **P05-OIDC-01:** Gitea **Run #90 FAILED**: disposable four-service ZITADEL stack healthy and host-portless, but private `localhost:8080` loopback forwarding was not ready. Provisioning aborted before OIDC client/human/browser creation; real callback/session **NOT verified**. Owned database/bootstrap/secret/network cleanup **PASS**. No app/auth source change or deployment. See `docs/P05-OIDC-01.md`.
|
||||
- **P05-OIDC-02:** **Gitea Run #91 FAILURE**: original four backend services and no-host-port private Traefik Host routing PASS, prebuilt socat version/digest PASS; forwarder immediately **exited with code 1**, so client/user/browser/Auth.js callback NOT EXECUTED. Cleanup PASS. No application/auth/backend edits; real OIDC remains BLOCKED. See `docs/P05-OIDC-02.md`.
|
||||
- **P05-OIDC-03:** CI-only socat startup diagnosis and immutable Python stdlib private fallback committed at `7b80f41`; **single Gitea Run #93 QUEUED** at last check, no OIDC/browser/cleanup steps executed, authentication acceptance **NOT VERIFIED**. Original auth/browser/Compose unchanged. See `docs/P05-OIDC-03.md`.
|
||||
- **P05-OIDC-03:** CI-only socat startup diagnosis and immutable Python stdlib private fallback committed at `7b80f41`; **single Gitea Run #93 QUEUED**, job #206 not started/logs unavailable; all OIDC/browser/cleanup checks **NOT EXECUTED**. Read-only scheduling audit P05-OIDC-03-A01 cannot establish current runner online state. See `docs/P05-OIDC-03-A01.md`.
|
||||
- **Production / Coolify:** not configured or deployed.
|
||||
|
||||
## Documentation and project knowledge
|
||||
|
||||
@@ -45,3 +45,6 @@ Future feature additions need an evidence-backed status update here, an exact de
|
||||
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
**P05-OIDC-03-A01 queue audit:** Existing manual [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93), job #206 was **QUEUED** (no start, steps or conclusion). Gitea job log returned `404 job not started`; workflow active with `ubuntu-latest` label, but current runner availability cannot be confirmed. Every real OIDC project/client/user, browser callback/session, negative and mandatory cleanup gate **NOT EXECUTED**; Login security/build acceptance from earlier separate phases remains valid. See `docs/P05-OIDC-03-A01.md`.
|
||||
@@ -16,6 +16,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [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 socat classification, private Python fallback and exact Gitea status | P05-OIDC-03 / Run #93 QUEUED, no terminal result |
|
||||
| [P05-OIDC-03-A01.md](P05-OIDC-03-A01.md) | Existing Gitea Run #93 read-only scheduling evidence, actual unexecuted checks and safe next steps | P05-OIDC-03-A01 / queue audit, no terminal OIDC acceptance |
|
||||
| [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,26 @@
|
||||
# P05-OIDC-03-A01 — Existing Run #93 Queue & Acceptance Evidence
|
||||
|
||||
**Approved baseline:** `09add5345abc5cef676ab7f5d3220eaa641310b4`.
|
||||
**Existing test candidate:** `7b80f411b2981e2274d171c12596301ed757b768`.
|
||||
**Existing run:** [Gitea Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93), job #206.
|
||||
**Last observed status:** **QUEUED**, not a terminal test success or failure.
|
||||
|
||||
## What was verified
|
||||
|
||||
The only authorized run, #93, has Gitea status `queued`, no conclusion, no job steps and no real started time. Attempting to retrieve job #206 logs returned `404: job not started`. Gitea lists the manual `p05-oidc-acceptance.yml` workflow as **active**, and its job requests runner label `ubuntu-latest`; earlier Run #91 of this workflow did execute. These facts show the dispatch and workflow exist, but do **not prove** a suitable runner is currently online/idle or establish a reason for this queue.
|
||||
|
||||
There is no available connected read operation that reports the current Gitea runner registration, online/offline state, label matching or capacity. Without access to that separate runner-status surface, claiming **runner offline** or blaming Docker, ZITADEL, the socat replacement or user authentication would be unsupported.
|
||||
|
||||
## Real OIDC acceptance: still not verified
|
||||
|
||||
Because Run #93 has not started, **none** of its actual checks has run: ephemeral Docker startup, socat error classification / Python forwarding fallback, localhost issuer, official disposable client/project/user provisioning, Chromium original Login V2 username/password, authorization code/PKCE/state/nonce, Auth.js callback, protected Account Portal identity/API, anonymous and malformed callback rejection, logout or run-owned resource cleanup. Every item remains **NOT EXECUTED** for this run, not PASS and not a runtime FAIL.
|
||||
|
||||
Historical Run #91 proved backend/Host routing PASS and socat exit code 1; it was a separate test on a different SHA. Run #93 has neither reproduced nor disproved that failure yet. No new workflow run, source change, production deployment, real user or secret use occurred in P05-OIDC-03-A01.
|
||||
|
||||
## What to do next
|
||||
|
||||
Continue inspecting **the existing Run #93**, not dispatching another run. A Gitea administrator can inspect runner online status, `ubuntu-latest` labels and job capacity **read-only** through authorized runner administration. Do not edit runner labels/configuration, cancel or rerun the job under this phase.
|
||||
|
||||
If job #206 begins/completes, inspect its genuine terminal logs and confirm each OIDC, negative-auth and mandatory cleanup marker before declaring acceptance. If it remains queued, record the exact status and missing runner visibility as a **scheduling/availability investigation**, not a proven outage.
|
||||
|
||||
Development evidence and exact phase scope: `notes/P05-OIDC-03-A01.md`. CI source remains at tested candidate `7b80f411b2981e2274d171c12596301ed757b768`; final documentation commit is not a new tested SHA.
|
||||
@@ -104,3 +104,11 @@ Coolify, HTTPS, secrets, backups, durable storage and focused production readine
|
||||
- **Blocker:** private run-owned localhost:8080 forwarder did not become ready in bounded 70 seconds; no admin API project/client/human provisioning or Chromium PKCE/state/nonce/callback/session/negative tests were executed. Exact sidecar cause **unknown** with current suppressed diagnostics. **Interactive OIDC acceptance BLOCKED**.
|
||||
- **Safety PASS:** mandatory `always()` cleanup step succeeded: `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`, `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`. No production users/secrets/ports/deployment affected.
|
||||
- No local application tests/builds, no second Gitea run, no original backend/Login/Auth.js source/manifest edits. Next P05-OIDC-02 requires separate exact scope approval limited to CI-only forwarder readiness/observability, then one new isolated full OIDC run. Full evidence `notes/P05-OIDC-01.md`, operator guidance `docs/P05-OIDC-01.md`.
|
||||
|
||||
|
||||
## P05-OIDC-03-A01 — Existing Run #93 Terminal Acceptance & Queue Audit (APPROVED 2026-11-23)
|
||||
|
||||
- Exact approved baseline `09add5345abc5cef676ab7f5d3220eaa641310b4`; existing Run #93 tested candidate `7b80f411b2981e2274d171c12596301ed757b768`, job #206. Read-only Gitea run/job status **QUEUED** with no steps or true timestamps; job log returned `404 job not started`. Manual workflow is active with `ubuntu-latest` label, but **current runner registration/online/capacity cannot be read through available connector**. Historic Run #91 succeeded in being scheduled, not proof of current availability.
|
||||
- **Only existing Run #93** may be checked; no additional dispatch, rerun, cancellation, runner config updates, workflow/backend/Login/Auth.js/CI source edits, local builds or production/real accounts. Exact write scope only `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST and navigation when necessary.
|
||||
- Every Run #93 gate is **NOT EXECUTED**: Git checkout, disposable backend/forwarder/provisioning, browser PKCE/state/nonce/Auth.js callback/session, positive/negative authorization, logout and mandatory owned cleanup. The only correct acceptance statement is **PENDING / NOT VERIFIED**, not test FAILURE or PASS.
|
||||
- Next narrow task: read-only check whether **this same Run #93** is scheduled/completed and inspect authorized Gitea runner online/label/capacity state, without modifying runners or dispatching more jobs. Terminal evidence, if it becomes available, must be documented before claiming positive OIDC acceptance. Evidence: `notes/P05-OIDC-03-A01.md`, operator guidance: `docs/P05-OIDC-03-A01.md`.
|
||||
+1
-1
@@ -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 P05-OIDC-03's single-run socat startup classification and private Python fallback acceptance see [P05-OIDC-03.md](P05-OIDC-03.md). Historical Run #91 exit-code blocker and safe cleanup are in [P05-OIDC-02.md](P05-OIDC-02.md). For the previous Run #90 blocker and cleanup see [P05-OIDC-01.md](P05-OIDC-01.md). For Gitea Run #89 final Login frozen build/unit/zero-advisory acceptance see [P05-SEC-02-A01.md](P05-SEC-02-A01.md). For Run #88 historical blocker and corrected helper see [P05-SEC-02.md](P05-SEC-02.md). For Gitea Run #87 findings see [P05-SEC-01.md](P05-SEC-01.md). 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.
|
||||
For the current read-only [Run #93 queue audit](P05-OIDC-03-A01.md) and no-executed-step limitations see P05-OIDC-03-A01. The underlying [P05-OIDC-03 CI implementation](P05-OIDC-03.md) remains awaiting the same run. Historical Run #91 exit-code blocker and safe cleanup are in [P05-OIDC-02.md](P05-OIDC-02.md). For the previous Run #90 blocker and cleanup see [P05-OIDC-01.md](P05-OIDC-01.md). For Gitea Run #89 final Login frozen build/unit/zero-advisory acceptance see [P05-SEC-02-A01.md](P05-SEC-02-A01.md). For Run #88 historical blocker and corrected helper see [P05-SEC-02.md](P05-SEC-02.md). For Gitea Run #87 findings see [P05-SEC-01.md](P05-SEC-01.md). 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.
|
||||
@@ -69,3 +69,8 @@ Job #197 in [Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) fai
|
||||
|
||||
|
||||
**P05-OIDC-03 CI-only follow-up:** Run #91's `socat` process exited code 1 despite healthy Traefik Host route; exact stderr root cause was unknown. New `run.sh` captures only a fixed pre-credential startup error **class** (never raw logs), then can switch once within the same run to the official, SHA256-digest-selected Python stdlib forwarder. If private HTTP 200 still fails, stop before OIDC client/user provisioning and keep the failure marked BLOCKED. No host ports, no PKCE/nonce/state bypass, no local app tests, and mandatory existing cleanup remains unchanged. See `docs/P05-OIDC-03.md` for actual terminal result.
|
||||
|
||||
|
||||
## P05-OIDC-03-A01 — Gitea Run #93 queued, job not started
|
||||
|
||||
Existing Gitea Run #93/job #206 has not been assigned a running job at the inspected snapshot: no steps, no actual start timestamp and job log API returns `404 job not started`. Workflow `p05-oidc-acceptance.yml` is active and requests `ubuntu-latest`. This **does not prove** the runner is offline, that labels mismatch, or that the Python/socat forwarder failed. To investigate, have a suitably authorized Gitea administrator inspect runner online status, matching labels and capacity **without changing settings**. Do not manually dispatch another run or open production ports. No Run #93 teardown occurred because no resources were created. Details: `notes/P05-OIDC-03-A01.md`.
|
||||
@@ -18,5 +18,6 @@ This is the chronological **index**. Phase-specific scope/implementation evidenc
|
||||
| 2026-11-22 | P05-OIDC-01 | CI-only official ZITADEL OIDC project/client/user and Chromium original Login V2/Auth.js acceptance harness with owned cleanup | **Run #90 FAILED**: 4 services healthy, no host ports; private localhost:8080 forwarder not ready, no user/client/browser created; cleanup VERIFIED PASS. [Evidence](P05-OIDC-01.md) |
|
||||
| 2026-11-22 | P05-OIDC-02 | Prebuilt/digest-verified socat, private proxy/Host/sidecar state probes, status-only readiness | **Run #91 FAILURE**: backend and private Host routing PASS; forwarder exited code 1, no provisioning/browser; owned cleanup PASS. [Evidence](P05-OIDC-02.md) |
|
||||
| 2026-11-23 | P05-OIDC-03 | Safe socat exit diagnostics and one digest-pinned Python stdlib private TCP fallback within same disposable Gitea cycle | Source pushed; single Gitea Run #93 dispatched on `7b80f41`, **QUEUED**, no steps/cleanup executed; [evidence](P05-OIDC-03.md), acceptance pending |
|
||||
| 2026-11-23 | P05-OIDC-03-A01 | Read-only Gitea Run #93, job #206 and workflow queue/label audit; zero CI reruns or source edits | Run #93 **QUEUED**; job not started, logs 404, workflow active, current runner status not exposed; acceptance unverified. [Evidence](P05-OIDC-03-A01.md) |
|
||||
|
||||
Rules: Append new phases or fixes; never silently rewrite a past result. Separate **implemented**, **verified**, **blocked**, and **proposed**. Never log a user secret or personal data.
|
||||
@@ -14,6 +14,7 @@
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | Pre-change real browser OIDC Scope Lock, provision/redirect/session/negative tests and one CI run evidence | P05-OIDC-01 / Run #90 FAILED at forwarder readiness; cleanup PASS; acceptance BLOCKED |
|
||||
| [P05-OIDC-02.md](P05-OIDC-02.md) | Pre-change loopback-forwarder scope, pinned digest/preflight fix and one real Gitea acceptance cycle | P05-OIDC-02 / Run #91: private proxy PASS; socat exit 1, OIDC BLOCKED, cleanup PASS |
|
||||
| [P05-OIDC-03.md](P05-OIDC-03.md) | Pre-edit socat diagnosis, Python fallback and one focused Gitea Run #93 evidence | P05-OIDC-03 / Run #93 QUEUED, no steps executed, acceptance UNVERIFIED |
|
||||
| [P05-OIDC-03-A01.md](P05-OIDC-03-A01.md) | Read-only Run #93/Job #206 queue status, available runner evidence and exact unexecuted OIDC gate ledger | P05-OIDC-03-A01 / no terminal test, runner queue under investigation |
|
||||
| [CHANGELOG.md](CHANGELOG.md) | Short append-only chronological phase log and links to detailed reports | DOCS-01 / active |
|
||||
|
||||
Update this manifest whenever any direct child file or directory changes. Use **actual source state**; a planned file must be labeled planned, not present.
|
||||
@@ -0,0 +1,46 @@
|
||||
# P05-OIDC-03-A01 — Existing Run #93 Terminal Acceptance & Runner Queue Audit
|
||||
|
||||
**Date:** 2026-11-23 (Asia/Dhaka)
|
||||
**Explicitly approved baseline (Gitea main / local main):** `09add5345abc5cef676ab7f5d3220eaa641310b4`
|
||||
**The single approved CI run:** [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93), job #206, intended test candidate SHA `7b80f411b2981e2274d171c12596301ed757b768`.
|
||||
**Pre-change plan and exact Scope Lock:** This note was authored **before A01 documentation edits**. The objective is READ-ONLY verification of existing Run #93, without any new run, source modification or runner setting change.
|
||||
|
||||
## Exact write and read-only scopes
|
||||
|
||||
**Write:** `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST where necessary. Only CI evidence, runner queue status and next acceptance criteria may be updated. Current Git source inventory includes the new A01 Markdown note once staged.
|
||||
|
||||
**Strict read-only:** `tests/ci/**`, `.gitea/workflows/**`, `auth/ui/v2/**`, `users/ui/**`, `core/backend/zitadel/**`, `deployment/docker/**`, all manifests/lockfiles, runner registration/configuration, production, secrets and unrelated files. Preserve untracked root `AI_INSTRUCTIONS.md`. **No dispatch, rerun, cancellation, tag, release, deployment or local app builds/tests/dev servers.** No real identities.
|
||||
|
||||
## Focused read-only evidence gathered before edits
|
||||
|
||||
1. Gitea repo `vibtools/ZitPlane/main` SHA is `09add5345abc5cef676ab7f5d3220eaa641310b4`; Windows local HEAD matches, with only unrelated untracked `AI_INSTRUCTIONS.md`.
|
||||
2. Gitea API `get_run(93)`: `status=queued`, **no conclusion**. `created_at=2026-11-22T18:08:45Z`, `updated_at=2026-11-22T18:08:45Z`, `head_sha=7b80f411b2981e2274d171c12596301ed757b768`, event `workflow_dispatch`. The run did not move to running/completed at the latest read.
|
||||
3. `get_job(206)`: `status=queued`, no recorded steps, `started_at` and `completed_at` are the Gitea zero-time placeholder `1970-01-01T00:00:00Z`, **not actual run timestamps**.
|
||||
4. `get_job_log_preview(206)` returned **HTTP 404 `job not started`**. This confirms no runtime logs/steps to evaluate; do not misreport it as a test failure.
|
||||
5. `get_workflow(p05-oidc-acceptance.yml)` reports **active**. Its checked-in YAML is manual `workflow_dispatch`, single `runs-on: ubuntu-latest` Docker job, mandatory `always()` cleanup.
|
||||
6. Prior matching manual workflow Run #91 reached terminal `failure` because socat process exited code 1; its cleanup PASS. Prior successes for other jobs (Run #89 security/Login; Run #86 backend) demonstrate historical scheduling, **not that an eligible runner is online/idle today**.
|
||||
7. Available Gitea connector actions expose run/workflow/job/log reads but **no runner online/offline/registration-list endpoint**. Therefore it is NOT verified whether the current queue is caused by an offline runner, label mismatch, saturated runner, or Gitea scheduling issue. Do not assert a specific cause or modify runner settings.
|
||||
|
||||
## Gate-by-gate status of EXISTING Run #93 only
|
||||
|
||||
| Acceptance gate | Run #93 status |
|
||||
| --- | --- |
|
||||
| Job pickup, Git checkout, disposable Docker preflight | **NOT EXECUTED** — queued, no steps |
|
||||
| Four-service ZITADEL/Postgres/Login/Traefik startup, no host published ports | **NOT EXECUTED** |
|
||||
| Safe socat error classification and optional immutable Python fallback | **NOT EXECUTED** |
|
||||
| Private port-8080 forwarding HTTP 200 + original issuer/Host | **NOT EXECUTED** |
|
||||
| Official disposable project, OIDC client and test human provisioning | **NOT EXECUTED** |
|
||||
| Real Chromium Login V2 username/password, authorization code + PKCE S256/state/nonce | **NOT EXECUTED** |
|
||||
| Auth.js callback, authenticated account identity/API/protected pages | **NOT EXECUTED** |
|
||||
| Anonymous/invalid callback rejection and local logout | **NOT EXECUTED** |
|
||||
| Mandatory `always()` owned cleanup | **NOT EXECUTED** |
|
||||
| Overall real OIDC end-to-end acceptance | **PENDING / NOT VERIFIED**, **no conclusion** |
|
||||
|
||||
## Focused A01 execution plan and closure rules
|
||||
|
||||
1. Recheck the **same** Run #93 and job #206 read-only once during final documentation audit. If completed, verify its actual terminal steps/logs; otherwise record the queue snapshot without guessing scheduling root cause.
|
||||
2. Update `notes/**`, `project/**` and relevant `docs/**` with precise statuses and runner-visibility limitation. Preserve Run #90/#91 historical evidence and separate tested source SHA from documentation SHA.
|
||||
3. Stage ONLY allowed documentation paths, check exact Git diff, source inventory, manifest entries and absence of secrets. Commit once and push Gitea `main` with exact remote SHA verification. Do not dispatch another CI run.
|
||||
4. **Next action if still queued:** read-only terminal-status check for **Run #93**, plus runner online/label/capacity review through an *authorized* server admin UI where possible, without changing any runner config. Any subsequent config modification, new run or CI code change requires fresh Scope Lock and approval.
|
||||
|
||||
**No passing test claims are authorized without actual Run #93 output.** This is a queue/scheduling evidence phase, not a new OIDC implementation phase.
|
||||
@@ -18,6 +18,7 @@ This is the **developer-focused implementation history**. `notes/CHANGELOG.md` i
|
||||
| 2026-11-22 | P05-OIDC-01 | Added manual disposable IAM_OWNER/client/human/browser OIDC acceptance harness, secret isolation and cleanup | Run #90 FAIL before provisioning: private loopback forwarder unready; 4 backend services healthy, owned cleanup PASS. `notes/P05-OIDC-01.md` |
|
||||
| 2026-11-22 | P05-OIDC-02 | CI-only prebuilt socat digest startup, private proxy/Host/readiness/exit checks and status-only provisioner | **Run #91 FAILED**: 4 services + private proxy PASS, sidecar exit code 1; no real user/browser test; cleanup PASS. `notes/P05-OIDC-02.md` |
|
||||
| 2026-11-23 | P05-OIDC-03 | Allowlisted socat startup diagnostics and strictly private digest-pinned official Python stdlib fallback | Source `7b80f41` on Gitea; Run #93 QUEUED, no CI steps or terminal result. `notes/P05-OIDC-03.md` |
|
||||
| 2026-11-23 | P05-OIDC-03-A01 | Read-only investigation of active manual workflow and Run #93 Job #206 scheduling, no source change | Queued / no steps; Gitea log 404 job not started; current runner availability cannot be established. `notes/P05-OIDC-03-A01.md` |
|
||||
|
||||
## Required entry for each future change
|
||||
|
||||
|
||||
@@ -148,3 +148,10 @@ New source in `tests/ci/oidc_e2e/run.sh`: test namespace-local Traefik proxy Hos
|
||||
|
||||
|
||||
**P05-OIDC-03 queued CI evidence:** The only approved Gitea Run #93 (source `7b80f411b2981e2274d171c12596301ed757b768`) was still **QUEUED** at last inspection; job #206 has not started, so neither the socat diagnostic/Python fallback nor the browser/provisioning/cleanup ran. Do not mark technical failure/success; **runner scheduling is a pending dependency**, not a proven outage. Source audit passed, and no second dispatch occurred. Follow-up should examine **the same Run #93** terminal steps/actual cleanup and update docs, not rerun prior suites.
|
||||
|
||||
|
||||
## P05-OIDC-03-A01 — existing Run #93 read-only queue audit (2026-11-23)
|
||||
|
||||
The existing `p05-oidc-acceptance.yml` manual workflow is **active** and declares one `runs-on: ubuntu-latest` job. Run #93 requested on 2026-11-22T18:08:45Z at tested SHA `7b80f411b2981e2274d171c12596301ed757b768` is still **queued** at the A01 read-only inspection. Job #206 is also `queued` with no actual start/completion times or steps; Gitea returned HTTP 404 `job not started` for its log. This is a **scheduling/queue dependency, not a proved technical error** in the new socat diagnostic, Python TCP fallback, IAM_OWNER API or browser/PKCE/session checks. **No Run #93 authentication or cleanup gates executed.**
|
||||
|
||||
Historical Run #91 used this workflow and reached a terminal job, but that only proves prior runner availability. The connected Gitea read tools contain no online runner/registration/label-capacity read endpoint; current `ubuntu-latest` runner availability is therefore **unknown**, and offline/mismatched/saturated runner or scheduler failure cannot be distinguished. No runner config, workflow, source, credentials or live system touched; no second dispatch. Full read-only ledger: `notes/P05-OIDC-03-A01.md`. Operator guide: `docs/P05-OIDC-03-A01.md`.
|
||||
@@ -1,8 +1,8 @@
|
||||
# ZitPlane ? exact tracked source inventory
|
||||
|
||||
**Snapshot:** 2026-11-23, P05-OIDC-03 code at tested candidate SHA `7b80f411b2981e2274d171c12596301ed757b768`; one Gitea Run #93 dispatched but **QUEUED at last inspection**, no job steps executed. Real browser acceptance **NOT VERIFIED**; result-only docs commit does not alter tested CI code.
|
||||
**Snapshot:** 2026-11-23, P05-OIDC-03-A01 read-only Run #93/job #206 queue audit on test candidate SHA `7b80f411b2981e2274d171c12596301ed757b768`. Workflow ACTIVE, runner label `ubuntu-latest`; run QUEUED, job NOT STARTED, no terminal result or cleanup. Runner online/capacity UNKNOWN; authentication NOT VERIFIED. Final documentation-only commit does not alter tested CI source.
|
||||
|
||||
**Git-tracked paths: 751.** Untracked `AI_INSTRUCTIONS.md` and local secrets excluded.
|
||||
**Git-tracked paths: 753.** Untracked `AI_INSTRUCTIONS.md` and local secrets excluded.
|
||||
|
||||
This list reflects actual tracked Git files, not proof of authenticated OIDC. See `notes/P05-OIDC-03.md` and `project/OIDC-E2E-ARCHITECTURE.md`.
|
||||
|
||||
@@ -13,8 +13,8 @@ This list reflects actual tracked Git files, not proof of authenticated OIDC. Se
|
||||
| `auth` | 639 | Pinned official Login V2 source, unmodified |
|
||||
| `core` | 2 | Backend dev helper, unmodified |
|
||||
| `deployment` | 2 | P02 dev Compose, unmodified |
|
||||
| `docs` | 21 | User and operator docs |
|
||||
| `notes` | 13 | Phase plans and CI evidence |
|
||||
| `docs` | 22 | User and operator docs |
|
||||
| `notes` | 14 | Phase plans and CI evidence |
|
||||
| `packages` | 1 | Repository root |
|
||||
| `project` | 12 | Source, functions and architecture inventory |
|
||||
| `scripts` | 1 | Repository root |
|
||||
@@ -695,7 +695,7 @@ This list reflects actual tracked Git files, not proof of authenticated OIDC. Se
|
||||
- `deployment/README.md`
|
||||
- `deployment/docker/compose.backend.dev.yaml`
|
||||
|
||||
### docs ? 21 files
|
||||
### docs ? 22 files
|
||||
|
||||
- `docs/ARCHITECTURE.md`
|
||||
- `docs/DEVELOPMENT.md`
|
||||
@@ -710,6 +710,7 @@ This list reflects actual tracked Git files, not proof of authenticated OIDC. Se
|
||||
- `docs/P05-OIDC-01.md`
|
||||
- `docs/P05-OIDC-02.md`
|
||||
- `docs/P05-OIDC-03.md`
|
||||
- `docs/P05-OIDC-03-A01.md`
|
||||
- `docs/P05-SEC-01.md`
|
||||
- `docs/P05-SEC-02-A01.md`
|
||||
- `docs/P05-SEC-02.md`
|
||||
@@ -719,7 +720,7 @@ This list reflects actual tracked Git files, not proof of authenticated OIDC. Se
|
||||
- `docs/TROUBLESHOOTING.md`
|
||||
- `docs/USER-GUIDE.md`
|
||||
|
||||
### notes ? 13 files
|
||||
### notes ? 14 files
|
||||
|
||||
- `notes/CHANGELOG.md`
|
||||
- `notes/DOCS-01.md`
|
||||
@@ -730,6 +731,7 @@ This list reflects actual tracked Git files, not proof of authenticated OIDC. Se
|
||||
- `notes/P05-OIDC-01.md`
|
||||
- `notes/P05-OIDC-02.md`
|
||||
- `notes/P05-OIDC-03.md`
|
||||
- `notes/P05-OIDC-03-A01.md`
|
||||
- `notes/P05-SEC-01.md`
|
||||
- `notes/P05-SEC-02-A01.md`
|
||||
- `notes/P05-SEC-02.md`
|
||||
|
||||
Reference in new issue
Block a user