chore(actions): define TTL cleanup for Forgejo Actions task volumes #801

Closed
opened 2026-06-17 21:55:27 +02:00 by codex · 0 comments
Collaborator

Summary

RS2000 reclaimables classification found Forgejo Actions task volumes as likely CI-temp cleanup candidates, but they must not be deleted through blanket docker volume prune.

Scope

  • Define a safe prefix/age rule for Forgejo Actions task volumes.
  • Add dry-run inventory output before any deletion path exists.
  • Keep persistent app volumes and rollback material out of scope.
  • If a live cleanup is proposed, require explicit operator approval and rollback/evidence notes.

Spec sources (whitelist)

  • state/reports/rs2000-docker-reclaimables-classification-2026-06-17.md
  • runbooks/rs2000-disk-hygiene.md
  • runbooks/forgejo-actions-runner.md

Do NOT read

  • Docker volume contents.
  • Secret-bearing runner config or env values.
  • Full repo unless the whitelist points to a specific owner/source file.

Extracted context

Observed candidate class:

FORGEJO-ACTIONS-TASK-*_WORKFLOW-*_JOB-* 1.8G observed

The classification report explicitly keeps docker volume prune out of the default path.

Acceptance criteria

  • Dry-run command lists candidate Forgejo Actions task volumes with age, size, and reason.
  • Deletion command, if added, requires an explicit --execute flag and refuses unknown prefixes.
  • Runbook documents safe rollback/evidence expectations.
  • No persistent app volumes match the cleanup selector.

Hard stops

  • No blanket docker volume prune.
  • No live deletion without explicit operator approval.
  • No reading volume contents or secret-bearing runner config.

Source

Created from #799 follow-up classification.

## Summary RS2000 reclaimables classification found Forgejo Actions task volumes as likely CI-temp cleanup candidates, but they must not be deleted through blanket `docker volume prune`. ## Scope - Define a safe prefix/age rule for Forgejo Actions task volumes. - Add dry-run inventory output before any deletion path exists. - Keep persistent app volumes and rollback material out of scope. - If a live cleanup is proposed, require explicit operator approval and rollback/evidence notes. ## Spec sources (whitelist) - `state/reports/rs2000-docker-reclaimables-classification-2026-06-17.md` - `runbooks/rs2000-disk-hygiene.md` - `runbooks/forgejo-actions-runner.md` ## Do NOT read - Docker volume contents. - Secret-bearing runner config or env values. - Full repo unless the whitelist points to a specific owner/source file. ## Extracted context Observed candidate class: ```text FORGEJO-ACTIONS-TASK-*_WORKFLOW-*_JOB-* 1.8G observed ``` The classification report explicitly keeps `docker volume prune` out of the default path. ## Acceptance criteria - Dry-run command lists candidate Forgejo Actions task volumes with age, size, and reason. - Deletion command, if added, requires an explicit `--execute` flag and refuses unknown prefixes. - Runbook documents safe rollback/evidence expectations. - No persistent app volumes match the cleanup selector. ## Hard stops - No blanket `docker volume prune`. - No live deletion without explicit operator approval. - No reading volume contents or secret-bearing runner config. ## Source Created from #799 follow-up classification.
Sign in to join this conversation.
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
1 participant
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#801
No description provided.