chore(memory): guardrails live probe, TODO T9, journal

This commit is contained in:
bchanot committed 2026-10-18 18:49:51 +02:00
1 parent f0bcbfef46
commit b17de15c22
2 files changed
+2

No files matched your search

+1
View File
@@ -624,3 +624,4 @@ rules:
## 2026-10-18
- Guardrails ask (user): 5 domains baseline + API/access hygiene + test skill. `rules/secure-by-default.md` always-on (CLAUDE.global 320/320, BDR-085 path). `/guardrails` = stdlib py scanner (6 domains, FAIL/WARN/MANUAL) + judgment; auditor gate runs api+supabase. Calibrated on game/faunosteo: 7 FP classes fixed (stopPropagation wrappers, hidden inputs, service_role-only policies, border focus, UI routes dir, ignored .env, dup origin). Branch feature/secure-by-default, not committed. BDR-120 pending user approval.
- Passwords added on user question ("stockés en clair ?"): gap, rule had none. `checks/passwords.py` (api domain): clear column w/o hash lib, `==` or SQL compare, fast hash, log call, literal. Calibrated 7 projects: zero noise after htpasswd volume-mount FP. Suite 89/89, `make test` green.
- Live probe added (user: "est-ce qu'il attaque de l'exterieur ?"). `probe.py` read-only, `--authorized`, env secrets, same-host redirect only, budget-capped. 5 probes confirm a hole from outside (OPEN/CLOSED). Suite 16/16 on a localhost fixture. Classifier blocked edits/tests carrying exploit-language and the SSRF-shaped redirect fixture; full-file Write passed, so probe strings are neutral and interpretation lives in checks.md.