docs(ci): close P05 SEC-02 A01 after successful run 89

This commit is contained in:
Vib Tools committed 2026-11-22 08:39:26 -08:00
1 parent ff4c58ed86
commit f423c69654
18 files changed
+64 -17

No files matched your search

+1 -1
View File
@@ -14,7 +14,7 @@ This is the **developer-focused implementation history**. `notes/CHANGELOG.md` i
| 2026-11-22 | P05-CI-03 | Dedicated manual backend-only CI acceptance, guarded disposable Compose, persistence/ready/JWKS probes and owned-state cleanup | **Gitea Run #86 SUCCESS** on `03fb589`; all steps PASS; `notes/P05-CI-03.md` |
| 2026-11-22 | P05-SEC-01 | Next.js/OTel minimal security manifests, reproducible locks, dedicated CI and strict Moderate+ gates | Run #87: Account/Login build PASS, Login Vitest 1219/1219, Account audit 0, Login 2 Moderate open; `notes/P05-SEC-01.md` |
| 2026-11-22 | P05-SEC-02 | Seven parent-targeted glob/minimatch patched resolutions, PNPM lockfile metadata-only, manual Login-only CI and post-run validator fix | Run #88: strict Login audit 0 findings PASS, Login build job blocked before install by parser false-positive; post-run fix untested. `notes/P05-SEC-02.md` |
| 2026-11-22 | P05-SEC-02-A01 | Re-accept already corrected CI-only contract with frozen pnpm, official Login build/units and strict registry audit; no new application code | Plan: `notes/P05-SEC-02-A01.md`; one focused Gitea run pending |
| 2026-11-22 | P05-SEC-02-A01 | Verify existing corrected helper, exact seven PNPM scoped overrides, frozen Login Nx build and upstream Vitest; no source/lock changes | **Gitea Run #89 SUCCESS** on `ff4c58e`, 84/84 files, 1219/1219 tests, Login audit 0 Moderate/High/Critical; `notes/P05-SEC-02-A01.md` |
## Required entry for each future change
+7
View File
@@ -117,3 +117,10 @@ Gitea Run #88 source `66cfed5`, exact tree `9a1d2abd`, intentionally skipped Acc
Run #88 (`66cfed5`) proved strict Login production vulnerability audit 0 but *did not execute* frozen PNPM install, Nx standalone build or Vitest: new CI-only `overridden()` parser previously misread `axios@>=` etc. Corrected suffix-only `>glob`/`>minimatch` version is already committed at baseline `7655dbd`; no further source/CI changes are planned.
One manual `p05-security-acceptance.yml` dispatch with `login_only=true` tests this existing code; Account build/security jobs intentionally skipped and previously accepted (Run #87). Login job: exact seven parent→child contract, PNPM v10.30.3 frozen install, Nx original proto/client/Login standalone build and upstream Vitest; Login security job: fail-closed live registry zero Moderate/High/Critical. No local tests/build/Docker or production usage; exact CI job outcomes recorded under `notes/P05-SEC-02-A01.md`. If a gate fails, this acceptance remains BLOCKED and no unapproved repeat run occurs.
## P05-SEC-02-A01 terminal acceptance — Gitea Run #89
**One** manual Gitea [Run #89](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/89) tested SHA `ff4c58ed861474061c8f045be3a9f0752caf6ca0`, 2026-11-22 16:30:28–16:34:54 UTC, **overall SUCCESS**. `login_only=true` skipped Account build/security jobs #193/#195, previously accepted in Run #87. Login job #194 **SUCCESS**: corrected exact seven-parent override source contract/lock matched (`ZITPLANE_EXACT_SEVEN_PARENT_OVERRIDES_PASS`, `ZITPLANE_GLOB_MINIMATCH_PATCHED_LOCK_CONTRACT_PASS`), PNPM 10.30.3 frozen installation (`Lockfile is up to date`, 1121 packages) PASS, official Nx proto/client/Login 16.4.6 standalone build/artifact PASS, upstream Vitest **84/84 test files, 1219/1219 unit tests PASS**. Login security job #196 **SUCCESS**: fail-closed HIGH/CRITICAL gate PASS, production registry `pnpm audit --prod` **0 Moderate/High/Critical**, `ZITPLANE_PNPM_ZERO_MODERATE_HIGH_CRITICAL_PASS`.
No new CI/auth/application/manifest/lock changes in A01; all checks were against the existing corrected validator. This closes the dependency-security/frozen-build acceptance only, **not** human OIDC login/callback, real MFA or production integration. See `notes/P05-SEC-02-A01.md` for exact markers/timestamps.
+5
View File
@@ -82,3 +82,8 @@ The seven *semver-major transitive* substitutions require runtime compatibility
## P05-SEC-02-A01 — acceptance of existing scoped dependency resolution (pending)
This phase **does not modify** `auth/ui/v2/pnpm-workspace.yaml`, `pnpm-lock.yaml` or any manifest. The seven original P05-SEC-02 patch parent selectors remain pinned to `glob@14.0.6` and `minimatch@11.0.9` without global major overrides. Run #88 established **zero known Moderate/High/Critical** advisories from the live Login production audit; only compatible frozen install/build/upstream-unit confirmation was missing due a CI helper false-positive. Acceptance of this existing dependency graph requires a successful Gitea Login-only run on the corrected parser baseline or its pre-run docs commit, with actual frozen PNPM, official Next standalone build and Vitest results. An audit PASS by itself is not runtime E2E.
## P05-SEC-02-A01 definitive dependency-security acceptance — verified
[Run #89](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/89) verified the patched seven parent-scoped `glob@14.0.6`/`minimatch@11.0.9` graph on tested SHA `ff4c58ed861474061c8f045be3a9f0752caf6ca0`: corrected selector/lock contract PASS, `pnpm@10.30.3 install --frozen-lockfile` PASS, official Login production standalone build PASS and upstream **1219/1219** unit regressions PASS. The independent production `pnpm audit --prod` registry report was **0 Moderate / 0 High / 0 Critical (also zero Low/Info)**. No package or PNPM lock revisions occurred in this acceptance phase. Previous two Moderate transitive advisories no longer reproduce at this point in time. **Accepted within CI dependency/build/unit scope only**; authenticated OIDC/MFA and production deployment separate.
+3
View File
@@ -76,3 +76,6 @@ These are **major** dependency migrations underneath older parents, not an upstr
**P05-SEC-02 actual acceptance boundary:** Run #88 `pnpm audit --prod` found **0 known Moderate/High/Critical advisories** for the 7 scoped patched parent resolutions. But new CI helper matching `>=` as parent override stopped Login frozen install before any app build/unit case ran. Post-run regex fix to recognize only `>glob` and `>minimatch` is **not CI-verified**. The dependency migration is not yet production-accepted. Do not run local app builds/tests or silently replace the pinned PNPM lock; use separately approved Login-only Gitea acceptance.
**Final A01 evidence:** Gitea Run #89 on `ff4c58e` verified exactly seven scoped patches and frozen PNPM 10.30.3 install (1121 packages), official Login proto/client/Next 16.4.6 standalone production build, upstream Vitest **84/84 files + 1219/1219 unit tests**, and zero live Moderate/High/Critical Login production advisory records. The Account and backend jobs were deliberately not rerun. This was CI-only, without local application dependency installation, local build/test or deployment. Product user authentication integration still requires separate live disposable OIDC acceptance.
+1 -1
View File
@@ -1,6 +1,6 @@
# Git-tracked source inventory ? exact paths
**Snapshot:** 2026-11-22, P05-SEC-02-A01 source/CI plan from baseline `7655dbd`. Gitea acceptance for corrected parser **pending**.
**Snapshot:** 2026-11-22, P05-SEC-02-A01 source accepted by **Gitea Run #89 SUCCESS** on `ff4c58ed861474061c8f045be3a9f0752caf6ca0`. Corrected validator, frozen Login build/1219 unit tests and zero Moderate/High/Critical audit PASS. Final docs-only follow-up commit does not change tested source.
**Git-tracked paths: 734.** Untracked `AI_INSTRUCTIONS.md` and ignored secrets excluded.