docs: align dependency hardening guidance

README.md

@@ -95,6 +95,9 @@ Deployment profiles and hardening references:
 
 - Added an executable production dependency boundary check that detects forbidden ownership
   direction, cycles, and dynamic-import drift without importing application modules.
+- Patched high-severity transitive frontend development dependencies and made local full-test,
+  pre-push, and CI security paths rebuild the exact lockfile tree before blocking high/critical
+  findings across production and development dependencies.
 - Startup health now exposes typed, redacted phase, readiness, retry, fatal, timing, and optional
   warmup outcomes.
 - Process-static deployment and security decisions now resolve once into an immutable,
@@ -814,7 +817,8 @@ The SOP already defines:
 
 - the docs-only exception for strictly documentation/planning/SOP changes
 - one-command full test scripts for Windows and Linux/WSL
-- supply-chain hardening checks and lockfile-driven frontend dependency installation
+- supply-chain hardening checks, lockfile-driven frontend dependency installation, and blocking
+  high/critical audits across production and development dependencies
 - pinned incremental Ruff/Mypy debt enforcement and deterministic scale regression baselines
 - the CI-parity backend coverage workflow with the governed 55% floor, retained release-cycle
   evidence, and required hotspot ownership
@@ -856,7 +860,10 @@ The connector currently remains an **optional attached subsystem inside this rep
 
 Read [SECURITY.md](docs/SECURITY.md) before exposing any endpoint beyond localhost. The project is designed to be secure-by-default (deny-by-default auth, SSRF protections, redaction, bounded outputs), but unsafe deployment can still create risk.
 
-Repository maintenance workflows also include supply-chain controls: CI/local validation scans declared dependencies and selected workspace persistence surfaces for known malicious indicators, frontend installs are lockfile-driven, and dependency manifest changes receive PR-time review.
+Repository maintenance workflows also include supply-chain controls: CI/local validation scans
+declared dependencies and selected workspace persistence surfaces for known malicious indicators,
+frontend installs are lockfile-driven, high/critical findings across production and development
+dependencies block acceptance, and dependency manifest changes receive PR-time review.
 
 ### Security Deployment Guide
 

docs/RELEASE_CHECKLIST.md

@@ -39,24 +39,28 @@ If the deployment enables remote control or bridge features, it must also pass *
 
 ### 3. Validation (Must Pass)
 
-Run the full regression suite:
+Run the complete OS-specific regression gate:
+
+```powershell
+# Windows
+powershell -File scripts/run_full_tests_windows.ps1
+```
 
 ```bash
-# 1. Secret Scanning
+# Linux / WSL
-./.venv/Scripts/python.exe -m pre_commit run detect-secrets --all-files
+bash scripts/run_full_tests_linux.sh
-
-# 2. Lint & Formatting
-./.venv/Scripts/python.exe -m pre_commit run --all-files --show-diff-on-failure
-
-# 3. Backend Unit Coverage Gate
-MOLTBOT_STATE_DIR="$(pwd)/moltbot_state/_local_unit" ./.venv/Scripts/python.exe scripts/run_backend_coverage.py --start-dir tests --pattern "test_*.py" --enforce-skip-policy tests/skip_policy.json --coverage-json .tmp/coverage/backend_unit_coverage.json
-
-# 4. Frontend E2E (Unit/Integration)
-# Ensure Node 18+
-node -v
-npm test
 ```
 
+These scripts execute the authoritative `tests/TEST_SOP.md` sequence, including fresh
+lockfile reconciliation with `npm ci`, the blocking
+`npm audit --audit-level=high` check across production and development dependencies,
+secret scanning, pre-commit hooks, governance and backend lanes, adaptive adversarial
+validation, and frontend Playwright E2E. A standalone `npm test` result is not a
+substitute for the complete release gate.
+
+If staged/manual execution is required, follow the explicit command order in
+`tests/TEST_SOP.md`; do not maintain a shortened release-only sequence here.
+
 ---
 
 ## Gate B: Bridge / Remote Control Safety (Conditional)

docs/SECURITY.md

@@ -12,10 +12,10 @@
 
 Only the latest version of ComfyUI-OpenClaw is supported for security updates.
 
-| Version | Supported          |
+| Version                  | Supported          |
-| ------- | ------------------ |
+| ------------------------ | ------------------ |
-| Latest  | :white_check_mark: |
+| Latest published release | :white_check_mark: |
-| < 0.2.0 | :x:                |
+| All earlier releases     | :x:                |
 
 ## Reporting a Vulnerability
 

docs/release/recent_updates.md

@@ -12,6 +12,10 @@ Newest entries appear first.
 - Added a dependency-light production source verifier to pre-commit. It parses tracked Python
   imports without importing application modules and fails on unknown ownership, forbidden
   dependency direction, cycles, and unreviewed dynamic imports.
+- Patched transitive frontend development dependencies `ws`, `postcss`, and resolver-owned
+  `nanoid` without changing the root manifest or runtime dependency boundary. Windows/Linux
+  full-test, pre-push, and CI security paths now run a fresh `npm ci` and block high/critical
+  findings across the complete production and development dependency tree.
 - Replaced coarse startup reporting with typed, redacted phase and state outcomes, bounded retry
   and timing metadata, and explicit optional warmup results.
 - Consolidated process-static deployment and security decisions into one immutable, secret-free