ci: introduce ZitPlane P05 verification foundation
This commit is contained in:
1 parent
7ecf531697
commit
42b79362c1
32 files changed
+1731
-471
No files matched your search
@@ -1,6 +1,6 @@
|
||||
# ZitPlane — Actual feature availability / limitations
|
||||
|
||||
Snapshot: 2026-11-22, baseline `40af500`. **SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION**.
|
||||
Snapshot: 2026-11-22, P05-CI-01 source preparation based on baseline `7ecf531`. **SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION**.
|
||||
|
||||
| Feature | Source present | CI/build verified | Live/deployed |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -17,7 +17,8 @@ Snapshot: 2026-11-22, baseline `40af500`. **SOURCE EXISTS != RUNNING != VERIFIED
|
||||
| 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 and isolated integration tests | No | No | No |
|
||||
| Gitea Actions CI verification workflow | P05 source added, manual dispatch | Not yet verified | Not deployed |
|
||||
| Gitea Actions CI and isolated integration tests | Verification scripts prepared; full OIDC E2E absent | 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 |
|
||||
|
||||
+2
-1
@@ -7,6 +7,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [README.md](README.md) | Documentation responsibilities, audience, navigation and change rules | DOCS-01 / active |
|
||||
| [MINIFEST.md](MINIFEST.md) | Direct-file manifest and phase ownership | DOCS-01 / active |
|
||||
| [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 / awaiting CI |
|
||||
| [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 |
|
||||
@@ -17,4 +18,4 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [P03-SOURCE-IMPORT.md](P03-SOURCE-IMPORT.md) | Exact ZITADEL upstream import source/blob audit and CI backlog | P03 / existing |
|
||||
| [P04-ACCOUNT-PORTAL.md](P04-ACCOUNT-PORTAL.md) | Account Portal source, security assumptions and pending CI | P04 / existing |
|
||||
|
||||
No new subfolders in `docs/` at DOCS-01. Future subfolders need their own `README.md` and `MINIFEST.md` if project-owned; do not rewrite upstream vendor directories merely to add documentation.
|
||||
No subfolders in `docs/` as of P05-CI-01. Future subfolders need their own `README.md` and `MINIFEST.md` if project-owned; do not rewrite upstream vendor directories merely to add documentation.
|
||||
@@ -0,0 +1,30 @@
|
||||
# P05-CI-01 — Gitea Actions verification
|
||||
|
||||
Date: 2026-11-22
|
||||
Source baseline: `7ecf53169776cc7f08af3dde6fe4b4492acf3ea1`
|
||||
State: **WORKFLOW SOURCE PREPARED; DISPATCH/RESULTS PENDING**.
|
||||
|
||||
## How to run
|
||||
|
||||
In Gitea `vibtools/ZitPlane`, open Actions > **ZitPlane P05 CI Verification** > Run workflow, select `main`. This is **manual only** and requires an existing `ubuntu-latest` runner with working Docker support. The workflow file is `.gitea/workflows/p05-ci.yml`.
|
||||
|
||||
No local PC tests, builds, Docker or dev servers are performed by this phase. The workflow jobs execute only inside Gitea runner job containers.
|
||||
|
||||
## Gates
|
||||
|
||||
- **account** — Account Portal pinned npm lock, dependency installation, TypeScript and Next.js production build.
|
||||
- **login** — upstream source's pinned pnpm frozen workspace install, Nx proto/client/Login V2 build and upstream Login unit suite.
|
||||
- **security** — npm/pnpm production advisory triage; HIGH/CRITICAL advisories fail the gate.
|
||||
- **backend** — disposable Docker preflight, P02 Python helper contracts, ZITADEL/PostgreSQL/prebuilt Login/Traefik stack and OIDC discovery/JWKS, then cleanup.
|
||||
|
||||
**Not proved even by all four jobs passing:** complete interactive Account Portal OIDC callback/session, new user signup/MFA/passkeys, Admin Console login, global logout, production host/TLS/routing. These need a separate explicitly approved and fully disposable end-to-end integration test phase.
|
||||
|
||||
## Safety
|
||||
|
||||
Runner creates ephemeral secrets only. No production credentials or live user data. CI refuses to touch an existing Docker network with the fixed P02 name. Always cleanup is configured; if the runner itself crashes, disposable resources may require operator cleanup **after confirming exact project ownership**. No push/PR trigger, publish, release or deploy.
|
||||
|
||||
## Results
|
||||
|
||||
**No results have been verified at documentation creation time.** Fill with actual Gitea run ID, SHA, individual gate results and exact failures; do not infer PASS from static source or use historical runs from other repositories as ZitPlane acceptance.
|
||||
|
||||
Developer map: `project/CI-ARCHITECTURE.md`. Phase notes and root-cause evidence: `notes/P05-CI-01.md`.
|
||||
+9
-2
@@ -33,8 +33,15 @@ Implement one explicitly approved phase at a time. Keep out-of-scope files, exis
|
||||
- Explicitly **no local builds, tests, dev server, Docker or deployment**. Source-level audit only, Git commit and approved Gitea main push. Gitea Actions testing deferred; no CI workflow in this scope.
|
||||
- Evidence and pending runtime acceptance: `docs/P04-ACCOUNT-PORTAL.md`.
|
||||
|
||||
## P05 — Integration (proposed, NOT approved)
|
||||
Local development, shared UI tokens as needed, production-safe Docker topology, routing drafts, tests/docs. No live deployment.
|
||||
## P05-CI-01 — Gitea Actions Verification Foundation (APPROVED 2026-11-22)
|
||||
- Baseline `7ecf53169776cc7f08af3dde6fe4b4492acf3ea1`.
|
||||
- Approved paths `.gitea/**`, `tests/ci/**`, narrow `users/ui/package.json` and lockfile, `auth/ui/v2/pnpm-workspace.yaml` and lockfile, `notes/**`, `project/**`, relevant `docs/**` and `README.md`; root `MINIFEST.md` is a documentation-maintenance exception. Backend/Account auth/UI source READ-ONLY.
|
||||
- Manual Gitea workflow: account reproducible build, Login frozen build, dependency audit, disposable Docker backend readiness/discovery. **No local tests/build/dev server.**
|
||||
- Full OIDC login/session/MFA/Admin Console interactive acceptance is not covered without disposable app/user provisioning; status remains BLOCKED/PENDING, not fabricated PASS.
|
||||
- Run evidence: `notes/P05-CI-01.md` and `docs/P05-CI-01.md`. No production deployment/release.
|
||||
|
||||
## P05 — Full Integration (proposed, NOT approved)
|
||||
Shared design system, production-safe Compose topology and verified Login/Account OIDC wiring. No live deployment; separate approval.
|
||||
|
||||
## P06 — UI redesign (proposed, NOT approved)
|
||||
Compact login and account UI, accessibility, responsive design and scoped regressions. Protected authentication semantics unchanged.
|
||||
|
||||
@@ -24,3 +24,6 @@
|
||||
- Never publish real personal user data, passwords, access tokens or secrets.
|
||||
|
||||
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.
|
||||
@@ -59,6 +59,9 @@ The Account Portal's profile page is currently **read-only**, and security page
|
||||
|
||||
ZITADEL Admin Console is distinct from the Account Portal. Never expose administrative API tokens or secrets to the browser. Identity administration should follow roles/policies, while billing/subscriptions/product permissions belong to individual SaaS applications.
|
||||
|
||||
## Gitea Actions verification (P05-CI-01)
|
||||
A manual-only workflow is defined in `.gitea/workflows/p05-ci.yml`. In Gitea go to `vibtools/ZitPlane` > Actions > **ZitPlane P05 CI Verification** > Run workflow (`main`). This runs on a registered Docker-capable `ubuntu-latest` runner, **not** your PC. See `docs/P05-CI-01.md` for its four gates and limitations. The CI workflow creates only disposable local test credentials and removes its own volumes; no real accounts, Coolify or production domains are accessed.
|
||||
|
||||
## Acceptance and configuration troubleshooting
|
||||
|
||||
Refer to [FEATURES-STATUS.md](FEATURES-STATUS.md), [TROUBLESHOOTING.md](TROUBLESHOOTING.md), `docs/P02-EVIDENCE.md` and `docs/P04-ACCOUNT-PORTAL.md`. Do not claim success on a missing-run check. Future changes must update all affected docs and developer records.
|
||||
Reference in new issue
Block a user