docs(infisical): record forgejo token recovery notes #718

Closed
codex wants to merge 1 commit from codex/issues/711-forgejo-token-recovery-notes into main
Collaborator

Canary status: missing — fire canary manually only if this docs-only recovery note is considered in canary scope.

Summary

  • update /home-platform/forgejo_accounts key-map after removing the retired GLM PAT secret from Infisical
  • document that Patchwarden is a bot/safety identity and should receive fresh PATs through Forgejo user-token API under explicit operator/admin gate, not through human login

Scope

Docs-only Infisical key-map correction after Wave C token recovery discussion.

Non-goals

  • no token generation
  • no Patchwarden credential rotation
  • no revocation of FORGEJO_API_TOKEN or FORGEJO_ADMIN_PAT_TEMP
  • no runtime/deploy changes

Spec sources read

  • AGENTS.md — Forgejo/Infisical operating contract
  • docs/forgejo-agent-operations.md — actor PAT and Forgejo write identity rules
  • docs/infisical/key-map.md — changed file
  • runbooks/forgejo-actions-runner.md — canary env/Patchwarden token mapping
  • .forgejo/workflows/patchwarden-pr-sanity.yml — current Patchwarden PR sanity token fallback behavior
  • .forgejo/workflows/automerge-pilot.yml — merge actor token boundary
  • docs/forgejo-baseline/access-profile-baseline.yaml — Patchwarden account profile

Tests / smoke

  • Docs-only diff reviewed.
  • Live metadata check before deletion showed p+glm@durlej.me was infisical-only, with zero runtime consumers and zero repo consumers.
  • Live metadata check after deletion showed glm_present=false; p+patchwarden@durlej.me remained present.

Rollback

  • Revert this docs commit if the map wording is wrong.
  • Recreating p+glm@durlej.me in Infisical would require a separate owner decision and a fresh valid GLM token.

Incident ledger

Refs #711.

Canary status: missing — fire canary manually only if this docs-only recovery note is considered in canary scope. ## Summary - update `/home-platform/forgejo_accounts` key-map after removing the retired GLM PAT secret from Infisical - document that Patchwarden is a bot/safety identity and should receive fresh PATs through Forgejo user-token API under explicit operator/admin gate, not through human login ## Scope Docs-only Infisical key-map correction after Wave C token recovery discussion. ## Non-goals - no token generation - no Patchwarden credential rotation - no revocation of `FORGEJO_API_TOKEN` or `FORGEJO_ADMIN_PAT_TEMP` - no runtime/deploy changes ## Spec sources read - `AGENTS.md` — Forgejo/Infisical operating contract - `docs/forgejo-agent-operations.md` — actor PAT and Forgejo write identity rules - `docs/infisical/key-map.md` — changed file - `runbooks/forgejo-actions-runner.md` — canary env/Patchwarden token mapping - `.forgejo/workflows/patchwarden-pr-sanity.yml` — current Patchwarden PR sanity token fallback behavior - `.forgejo/workflows/automerge-pilot.yml` — merge actor token boundary - `docs/forgejo-baseline/access-profile-baseline.yaml` — Patchwarden account profile ## Tests / smoke - Docs-only diff reviewed. - Live metadata check before deletion showed `p+glm@durlej.me` was `infisical-only`, with zero runtime consumers and zero repo consumers. - Live metadata check after deletion showed `glm_present=false`; `p+patchwarden@durlej.me` remained present. ## Rollback - Revert this docs commit if the map wording is wrong. - Recreating `p+glm@durlej.me` in Infisical would require a separate owner decision and a fresh valid GLM token. ## Incident ledger Refs #711.
docs(infisical): record forgejo token recovery notes
All checks were successful
canary-required / collect-diff (pull_request) Successful in 5s
canary-required / canary (pull_request) Has been skipped
base-is-main / guard (pull_request) Successful in 2s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 44s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / sanity (pull_request) Successful in 58s
978db0f40b
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

Patchwarden PR sanity

  • Status: eligible_sanity_clean
  • PR: 718
  • Commit: 978db0f40b7f2cd46285feeb620bbbb3594fafcc
  • Security-sensitive label: present
  • 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

  • low Future-dated removal note may indicate typo

    • Evidence: docs/infisical/key-map.md line adding 'p+glm@durlej.me was removed from Infisical on 2026-06-04' — if current year is pre-2026, this date is in the future
    • Next: Verify the date 2026-06-04 is intentional (project timeline convention or typo for 2024/2025). If typo, correct before merge.

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-718 --> # Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `718` - Commit: `978db0f40b7f2cd46285feeb620bbbb3594fafcc` - Security-sensitive label: `present` - 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` - **`low`** Future-dated removal note may indicate typo - Evidence: `docs/infisical/key-map.md line adding 'p+glm@durlej.me was removed from Infisical on 2026-06-04' — if current year is pre-2026, this date is in the future` - Next: Verify the date 2026-06-04 is intentional (project timeline convention or typo for 2024/2025). If typo, correct before merge. ### `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.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Author
Collaborator

No Patchwarden findings to render.

No Patchwarden findings to render.
Owner

PR-zero queue collapse: closing this parked/conflicted security-sensitive Infisical recovery-note PR without merge. The branch is stale and touches credential/trust-boundary documentation, so it should not be revived by conflict resolution. If the key map still needs correction, create a fresh smallest-coherent PR with current evidence and full security-sensitive review. No secret value was read or changed here.

PR-zero queue collapse: closing this parked/conflicted security-sensitive Infisical recovery-note PR without merge. The branch is stale and touches credential/trust-boundary documentation, so it should not be revived by conflict resolution. If the key map still needs correction, create a fresh smallest-coherent PR with current evidence and full security-sensitive review. No secret value was read or changed here.
pdurlej closed this pull request 2026-06-17 23:17:21 +02:00
All checks were successful
canary-required / collect-diff (pull_request) Successful in 5s
canary-required / canary (pull_request) Has been skipped
base-is-main / guard (pull_request) Successful in 2s
Required
Details
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 44s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / sanity (pull_request) Successful in 58s
Required
Details

Pull request closed

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!718
No description provided.