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

+30
View File
@@ -152,3 +152,33 @@ The authorized Windows PC attempted a **local disposable** `npm.cmd ci --ignore-
**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 security remediation kickoff — 2026-11-22
**Status: IN PROGRESS / NOT ACCEPTED.** User-approved baseline `fac0934a00e6c15902738a3ffafb11b5ec2f0ac3`. Scope `package.json`, npm-generated `package-lock.json`, existing Gitea CI `security-audit` job, `notes/001–006`. Root cause `node_modules/next` locks `postcss@8.4.31` while root is `8.5.33`; P03 runtime audit 1 high and 23 moderate package entries. Plan minimal nested npm override, lockfile-only regeneration, high/critical audit gate; preserve all runtime/UI/API/auth/SDK/DB/Compose/production. One focused CI acceptance and exact 3-remote tree equality required; DO NOT label closed before terminal results, publish or claim release-ready.
## 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.
Candidate branch `p04-s01-postcss-security-20261122` contains notes only. Gitea main stays `fac0934a00e6c15902738a3ffafb11b5ec2f0ac3`; no Gitea CI was dispatched and no phase acceptance established.
## P04-S01B run ledger — 2026-11-22
**P04-S01B = BLOCKED / stop rule.** Disposable Windows npm 10.9.8 only (not user project workspace). Verified baseline Gitea `fac0934a00e6c15902738a3ffafb11b5ec2f0ac3` and candidate notes branch `4abcc55fee927b5ae2c1193cea2b4585b8d00158` before test. With approved stale node deletion in disposable lock plus scoped manifest override, `npm install --package-lock-only` 0, `npm ls --package-lock-only postcss --all --depth=4` 0, audit high 0 / critical 0 / moderate 22. Next 15.5.29, Cloudcmd 19.24.0 and every unrelated package version unchanged; package entries added 0, removed 1 (stale `node_modules/next/node_modules/postcss`), existing entries with changed metadata 67 (36 dev, 29 libc, 2 dependency ordering overlaps). **Reject generated candidate due preservation of unrelated metadata requirement.** No real npm ci, regression, Docker, focused Gitea CI, security gate edit, application changes, main commit, GitHub/GitLab mirror or release. P03 CLOSED, P04-S01B NOT CLOSED, published production still NO-GO.
## P04-S01C verified six-job acceptance checkpoint — 2026-11-22
- User-approved baseline Gitea main `fac0934a00e6c15902738a3ffafb11b5ec2f0ac3` still unchanged; candidate source commit `c759be990c032c2474d2d0bad519c643dec11a3a`, PR #5 draft pending acceptance.
- Exact source diff: only `package.json` scoped override, `package-lock.json` delete stale nested PostCSS entry (one package), existing `.gitea/workflows/datastack-ci.yml` security-audit threshold. Updated notes six files only; no runtime/SDK/UI/test/Dockerfile/Compose source changes.
- [Gitea CI #85](https://dev.ivib.cc/vibtools/DataStack/actions/runs/85) results as of checkpoint: node-regression **SUCCESS** `CI_SUITE_SUMMARY total=24 failed=0` plus real Linux `npm ci`; python-regression **SUCCESS** `Ran 14 tests`, `OK`; quality tsc/ESLint **SUCCESS**; production Next standalone **SUCCESS**; Docker/BuildKit 3 images **SUCCESS** `DATASTACK_THREE_IMAGES_BUILD_PASS`; security-audit **SUCCESS** runtime high 0/critical 0, `DATASTACK_RUNTIME_SECURITY_HIGH_CRITICAL_ZERO`, full moderate 24/runtime moderate 22. Windows-compatibility **QUEUED** at checkpoint: no terminal proof; entire run must not be mislabelled success.
- **P04-S01C PENDING** terminal Windows acceptance, main squash commit, GitHub/GitLab parity. Production NO-GO; 22 moderate runtime package entries and live readiness remain unresolved.
## 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.