chore(security): Baseline-Update Prüfstempel und release-checks

Makefile und scripts/security/stamp.py aus cj/security-baseline, leere
docs/RELEASE-AUSNAHMEN.md, AGENTS.md-Abschnitt zu Stempeln und Release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Grovy311 2026-10-17 10:46:29 +02:00
parent ad9ca4cae5
commit e2cc00dccc
4 changed files with 392 additions and 4 deletions

View file

@ -821,3 +821,14 @@ When uncertain, choose the simplest implementation that preserves the domain mod
Do not add libraries unless there is a clear reason.
Do not introduce global state management unless needed.
## Check stamps & release (baseline update 2026-10-17)
- `make stamp` shows which checks are validly green for HEAD (`reports/stamps/`, local only). Stamped
checks are skipped by `make prepush` and `make release-checks`. Valid only for a clean working tree;
docs-only commits afterwards keep the stamp valid.
- Before deploy via `pre-release-gate`: `make release-checks` (check + mutation, with `IMAGE=` also
container). ZAP/fuzz run after the deploy against our own instance and do not block the Go.
- Deliberately accepted H/M items: `docs/RELEASE-AUSNAHMEN.md` (reason + review date, never K items,
entries only after CJ decides).
- After deploy: record `docs/releases/<date>-<commit>.md` (`make release-report`) and tag
`release-<date>` on the deployed commit.