docs: record P05 security run 87 and two moderate blockers
This commit is contained in:
1 parent
752d243ae8
commit
43eee54e7a
18 files changed
+77
-16
No files matched your search
+1
-1
@@ -14,6 +14,6 @@ No real credentials or production domains are used. Never print bootstrap PATs,
|
||||
- `backend_cleanup.sh` (P05-CI-03) is the workflow's `always()` cleanup script. It tears down only a marked run-owned Compose project and verifies that no project containers, volumes or fixed network remain. Unverified cleanup is an explicit failure.
|
||||
- Run from `.gitea/workflows/p05-backend-acceptance.yml` **only in isolated Gitea CI**, not on a production Docker host or local developer PC. **Run #86 PASS** on `03fb589`, including persistence and owned cleanup. No real user login/MFA E2E was run.
|
||||
|
||||
- `security_advisory_gate.py` (P05-SEC-01) takes npm or pnpm registry audit JSON, rejects missing/errored/inconsistent metadata and requires **zero Moderate/High/Critical findings**. It is independent of the existing HIGH+ audit command and `advisory_triage.py` detailed advisory ID report. Do not mark reported Moderate findings resolved without a green CI result. Dedicated `.gitea/workflows/p05-security-acceptance.yml` is manual only; frozen installs/builds run only on Gitea.
|
||||
- `security_advisory_gate.py` (P05-SEC-01) takes npm or pnpm registry audit JSON, rejects missing/errored/inconsistent metadata and requires **zero Moderate/High/Critical findings**. It is independent of the existing HIGH+ audit command and `advisory_triage.py` detailed advisory ID report. **Gitea Run #87** proved Account audit 0 and Login audit **2 Moderate** (`glob`, `minimatch`); strict Login gate correctly FAILED. Dedicated `.gitea/workflows/p05-security-acceptance.yml` is manual only; frozen installs/builds are CI-only and passed 1219/1219 Login unit regressions.
|
||||
|
||||
Add new CI checks and update `MINIFEST.md`, `project/`, `docs/`, and `notes/` in the same approved phase.
|
||||
Reference in new issue
Block a user