P04-S01C: verified PostCSS security lock reconciliation and runtime advisory gate (#5)

fix(p04-s01c): accept scoped PostCSS reconciliation with CI #85 7/7 PASS [skip ci]

Preserve dependency graph and unrelated metadata; add runtime high/critical CI gate. Notes/001–006 document acceptance. Production release remains NO-GO.
This commit was merged in pull request #5.
This commit is contained in:
victorsteele428 committed 2026-11-22 17:19:06 +00:00
1 parent fac0934a00
commit 2d467ff149
9 files changed
+164 -26

No files matched your search

+22
View File
@@ -129,3 +129,25 @@ Baseline Gitea/GitHub `48fb277079b380fdbf1e58cd2da40afeed0b03ee`; GitLab baselin
**CI-08 security disposition:** `npm audit --json` full=26 affected packages (25 moderate, 1 high); runtime=24 (23 moderate, 1 high), **not counts of distinct advisories**. High-severity advisories [GHSA-6g55-p6wh-862q](https://github.com/advisories/GHSA-6g55-p6wh-862q), [GHSA-r28c-9q8g-f849](https://github.com/advisories/GHSA-r28c-9q8g-f849) affect Next 15.5.29's nested `postcss@8.4.31` despite patched root `postcss@8.5.33`; npm recommends major `next@16.4.6`. Direct `cloudcmd@19.24.0` carries moderate transitive issues (`dompurify`, `file-type`, `glob`, `minimatch`, `got`); npm recommends `cloudcmd@17.0.2` downgrade, not a verified safe pin. No speculative package pin, major upgrade or force fix; a separately tested compatible remediation is needed before release.
**Scope / release decision:** only `.gitea/workflows/datastack-ci.yml`, `.gitea/workflows/datastack-docker-ci.yml`, and `notes/001–006` changed. No `package.json`/lock, Dockerfile, application UI/UX, runtime, auth, SDK, database, Compose, production data, secret, shared Docker prune, deployment, migration, tag or release. P03 technical CI and advisory-triage acceptance verified by #77 non-Python jobs plus #78 Python; do **not** mislabel #77 overall as successful. Final phase publication requires one main commit and Gitea/GitHub/GitLab exact tracked tree parity. **Production release NO-GO** while runtime high advisory is unresolved; live production health, throughput and deployment remain unverified.
## P04-S01 blocked security reconciliation report
P04-S01 SEC-01 BLOCKED — 2026-11-22. Approved scoped `overrides.next.postcss=8.5.33` trialed in disposable Windows npm 10.9.8 workspace only. `npm install --package-lock-only` EXIT 0, but `npm ls --package-lock-only postcss --all` EXIT 1 (`ELSPROBLEMS`: Next nested `postcss@8.4.31` invalid; expected 8.5.33); npm dedupe also kept invalid dependency. Read-only `npm audit --omit=dev --json` EXIT 1, runtime high 1/moderate 23/critical 0. Lockfile regeneration caused unrelated churn (91 package entries added, 106 removed, 69 changed, including two lightningcss optional 1.33.0 -> 1.30.1). Fresh minimal Next 15.5.29 fixture with identical override resolves PostCSS 8.5.33, isolating failure to DataStack committed lock graph. `npm ci --dry-run` exit 0 does not prove real clean install. Exact stop rule applied: no dependency patch, no CI acceptance, no main commit, no GitHub/GitLab sync, no release/deploy; production NO-GO. Need separate explicit narrowly scoped lock reconciliation approval.
Root proof: `package-lock.json:10552-10560` Next pins 8.4.31; `:10602-10603` nested 8.4.31; `:11427-11428` root 8.5.33; advisories GHSA-6g55-p6wh-862q and GHSA-r28c-9q8g-f849.
## P04-S01B actual trial / release blocker — 2026-11-22
User explicitly approved P04-S01B stale-copy removal exception. In a clean disposable Windows npm 10.9.8 probe based on Gitea main `fac0934a00e6c15902738a3ffafb11b5ec2f0ac3`, remove ONLY the stale nested PostCSS 8.4.31 entry from the disposable lock copy and set `overrides.next.postcss=8.5.33`. `npm install --package-lock-only --ignore-scripts --no-audit --no-fund --prefer-offline` exited 0; `npm ls --package-lock-only postcss --all --depth=4` exited 0 and Next 15.5.29 used deduped 8.5.33. Read-only runtime audit on the **unpublished candidate** showed high=0, critical=0, moderate=22 (22 affected package entries); SEC-01 candidate mitigation confirmed but NOT accepted. The regenerated lock changed **67 unrelated package metadata entries** (36 `dev` and 29 `libc` field changes plus dependency order-only differences), despite zero unrelated version changes, and removed only the stale node. This violates explicit metadata preservation. STOP before real `npm ci`, Gitea CI, security-gate edit or main/mirror publication. No production release or security-clean claim for published baseline.
## P04-S01C verified candidate / Windows acceptance outstanding — 2026-11-22
Approved deterministic lockfile reconciliation fixed the **SEC-01 Next 15.5.29 nested PostCSS 8.4.31** candidate without touching any unrelated package metadata, versions, hashes, URLs or feature/runtime sources. Scoping: `package.json` scoped `overrides.next.postcss=8.5.33`; `package-lock.json` only 26-line removal of obsolete `node_modules/next/node_modules/postcss`; existing Gitea `security-audit` job adds runtime high/critical failure. Generated lockfile with deterministic baseline metadata restoration had SHA-256 `e6b5b362877627085dc04c9ded03c019971e07ef9f4af1e78057d58961a1c091` and Gitea branch bytes matched exactly. No unrelated package entry/metadata delta (0 added, 1 removed, 0 changed). Gitea [CI #85](https://dev.ivib.cc/vibtools/DataStack/actions/runs/85) candidate `c759be990c032c2474d2d0bad519c643dec11a3a`: Node 24/24, Python 14/14, strict TypeScript + ESLint, Next standalone, Docker 3/3 and runtime advisory gate all SUCCESS. Runtime audit **22 moderate, 0 high, 0 critical**; full audit **24 moderate, 0 high, 0 critical**. **Windows compatibility job still QUEUED at checkpoint; overall CI not yet terminal accepted, main and mirrors unchanged.** Production remains NO-GO pending Windows CI, 3-remote sync, remaining moderate advisories/live health.
## P04-S01C FINAL CI acceptance (7/7) — 2026-11-22
Gitea CI #85 https://dev.ivib.cc/vibtools/DataStack/actions/runs/85 COMPLETED/SUCCESS; tested implementation SHA c759be990c032c2474d2d0bad519c643dec11a3a; later changes to candidate are documentation only. All seven jobs terminal SUCCESS: node-regression (Linux committed-lock npm ci and exactly 24/24 TypeScript suites); python-regression (Ran 14 tests, OK); quality (strict tsc and ESLint); production-build (Next 15.5.29 standalone, 22/22 pages); docker-image-build (three isolated BuildKit ingestion/web/proxy images); windows-compatibility (Windows committed-lock npm ci and Node SDK build, job #182, terminal SUCCESS); security-audit (runtime moderate=22 high=0 critical=0; full moderate=24 high=0 critical=0; DATASTACK_RUNTIME_SECURITY_HIGH_CRITICAL_ZERO). Single Gitea acceptance run used, no additional broad reruns.
Scope: exactly nine approved paths: package.json scoped next->postcss 8.5.33 override; package-lock.json removes only old nested postcss@8.4.31 entry; existing .gitea/workflows/datastack-ci.yml security-audit job high/critical rejection; notes/001–006 evidence. Other package metadata, versions, integrity and resolved URLs match baseline. Next.js 15.5.29 and Cloudcmd 19.24.0 preserved. Final candidate package-lock SHA256 e6b5b362877627085dc04c9ded03c019971e07ef9f4af1e78057d58961a1c091 (verified byte-for-byte with Gitea). No API, auth, SDK, UI, application runtime, database, Compose, Dockerfile, tests or production data changes, deployment, migration, prune, tag, release.
CI fully accepted; publication not yet asserted in these pre-merge notes. Final phase CLOSED requires one squash merge of PR #5 into Gitea main and verified identical tracked content across Gitea/GitHub/GitLab; record actual new SHAs in terminal report. Production release remains NO-GO pending P04-S02 moderate vulnerability triage and separately authorized live readiness verification.