docs(security): record secret incident containment receipt #737

Merged
pdurlej merged 1 commit from codex/secret-incident-closure-receipt into main 2026-06-07 15:33:10 +02:00
Collaborator

Summary

  • add a 2026-06-07 secret incident containment receipt
  • link it from runbooks/platform-secret-recovery.md
  • explicitly distinguish immediate containment from full platform-wide all-clear

Scope

Documentation only. No runtime mutation, no credential rotation, no secret reads committed, no secret values, no fingerprints, no hashes, no DSNs.

Status

This is containment_complete_with_deferred_exceptions, not all_clear.

Retained exceptions remain:

  • FORGEJO_API_TOKEN
  • FORGEJO_ADMIN_PAT_TEMP

Deferred classes remain:

  • database passwords requiring Wave D
  • high-risk crypto/session secrets requiring Wave E
  • final Infisical audit tracked by #735

Spec sources read

  • AGENTS.md — repo operating rules and Forgejo identity discipline
  • docs/forgejo-agent-operations.md — Forgejo actor identity rules
  • runbooks/platform-secret-recovery.md — recovery waves and evidence requirements
  • scripts/security/secret_recovery_verify.py — verifier schema and scope
  • tests/test_secret_recovery_verify.py — verifier safety expectations
  • docs/incidents/2026-06-02-honcho-qwen-fix.md — incident doc style reference

Verification

  • Forgejo authenticated user checked as codex, non-admin
  • repo-only verifier command class run with no secret output:
    python3 scripts/security/secret_recovery_verify.py --repo-root . --format json
  • sanitized summary: schema platform_secret_recovery_report.v1, records 85, repo-only findings 0, waves B/C/D/E
  • grep check over touched docs for accidental secret-like patterns; only policy/prohibition words matched, not secret material

Rollback

Revert this PR. It changes only documentation.

Refs #735

## Summary - add a 2026-06-07 secret incident containment receipt - link it from `runbooks/platform-secret-recovery.md` - explicitly distinguish immediate containment from full platform-wide all-clear ## Scope Documentation only. No runtime mutation, no credential rotation, no secret reads committed, no secret values, no fingerprints, no hashes, no DSNs. ## Status This is `containment_complete_with_deferred_exceptions`, not `all_clear`. Retained exceptions remain: - `FORGEJO_API_TOKEN` - `FORGEJO_ADMIN_PAT_TEMP` Deferred classes remain: - database passwords requiring Wave D - high-risk crypto/session secrets requiring Wave E - final Infisical audit tracked by #735 ## Spec sources read - `AGENTS.md` — repo operating rules and Forgejo identity discipline - `docs/forgejo-agent-operations.md` — Forgejo actor identity rules - `runbooks/platform-secret-recovery.md` — recovery waves and evidence requirements - `scripts/security/secret_recovery_verify.py` — verifier schema and scope - `tests/test_secret_recovery_verify.py` — verifier safety expectations - `docs/incidents/2026-06-02-honcho-qwen-fix.md` — incident doc style reference ## Verification - Forgejo authenticated user checked as `codex`, non-admin - repo-only verifier command class run with no secret output: `python3 scripts/security/secret_recovery_verify.py --repo-root . --format json` - sanitized summary: schema `platform_secret_recovery_report.v1`, records `85`, repo-only findings `0`, waves `B/C/D/E` - grep check over touched docs for accidental secret-like patterns; only policy/prohibition words matched, not secret material ## Rollback Revert this PR. It changes only documentation. Refs #735
docs(security): record secret incident containment receipt
All checks were successful
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 22s
pyfallow / Pyfallow gate (control-plane) (pull_request) Successful in 18s
python-ci / Python 3.12 (pull_request) Successful in 44s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 55s
patchwarden-pr-sanity / sanity (pull_request) Successful in 1m57s
python-ci / Python 3.11 (pull_request) Successful in 42s
python-ci / Python 3.13 (pull_request) Successful in 43s
canary-required / canary (pull_request) Has been skipped
dd763f5397
First-time contributor

No Patchwarden findings to render.

No Patchwarden findings to render.
First-time contributor

Patchwarden PR sanity

  • Status: eligible_sanity_clean
  • PR: 737
  • Commit: dd763f5397f0a24adf4e2590fa5c18c2ff1f5589
  • Security-sensitive label: missing
  • Authority: advisory model review plus deterministic blockers only
  • 3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

global-glm / glm-5.1:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

global-deepseek / deepseek-v4-pro:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

redteam / kimi-k2.6:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

Policy notes

  • GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
  • Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
  • Auto-merge is not enabled here.
<!-- patchwarden-pr-sanity:pdurlej/platform:PR-737 --> # Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `737` - Commit: `dd763f5397f0a24adf4e2590fa5c18c2ff1f5589` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.
pdurlej deleted branch codex/secret-incident-closure-receipt 2026-06-07 15:33:11 +02:00
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!737
No description provided.