docs(prompts): add RS2000 dangling image prune handoff #232

Merged
pdurlej merged 1 commit from codex/rs2000-image-prune-prompt into main 2026-05-12 07:16:22 +02:00
Collaborator

Canary status: missing — Lite/docs review before merge

Canary Context Pack

Product story

RS2000 has accumulated dangling Docker images from prior build/deploy work. The operator needs a small, safe, copy-pasteable cleanup handoff that reduces image sprawl without turning into a broader prune or production mutation by an agent.

What changed

Added prompts/codex-rs2000-image-prune-2026-05-12.md, a narrow operator-run prompt for docker image prune -f on RS2000 with pre-checks, post-checks, safety boundaries, rollback notes, and explicit out-of-scope items.

Why it changed

This is P2 from prompts/codex-rs2000-close-2026-05-12.md: a quick win after P0 apply hardening and P1 recovery runbook batches.

Files touched

  • prompts/codex-rs2000-image-prune-2026-05-12.md

Relevant context

  • prompts/codex-rs2000-close-2026-05-12.md P2
  • prompts/06-prune.md for the broader Phase 06 scope this PR intentionally does not perform
  • ADR-0003 rule from the dispatch: Codex does not SSH-execute production mutations

Runtime evidence

No runtime command was executed by Codex. This PR only adds an operator handoff prompt.

Known constraints

Dangling image prune is non-reversible, but should not affect tagged images, running containers, compose files, or Docker volumes.

Explicit out-of-scope

  • docker system prune
  • docker image prune -a
  • --volumes
  • compose changes
  • container restarts
  • worktree cleanup
  • sunset-module cleanup
  • weekly prune timer / full Phase 06 policy

Requested decision

Approve this docs-only Lite PR if the handoff is clear and appropriately narrow.

Merge blockers

  • Any instruction that could delete volumes, tagged images, containers, or worktrees
  • Any suggestion that Codex should execute the SSH production mutation
  • Any ambiguity between this narrow dangling-image cleanup and the full Phase 06 prune wave

Spec sources read

  • prompts/codex-rs2000-close-2026-05-12.md — P2 requirement and hard rule against Codex SSH production mutation
  • prompts/06-prune.md — broader prune scope used to keep this prompt intentionally narrow
  • decisions/0007-risk-proportional-canary.md — Lite tier discipline

Test plan

  • git diff --check
  • Confirm prompt contains docker image prune -f and explicitly rejects docker system prune, docker image prune -a, and --volumes

Closes no issue directly; this is the P2 follow-up from issue #142 close-out.

Canary status: missing — Lite/docs review before merge ## Canary Context Pack ### Product story RS2000 has accumulated dangling Docker images from prior build/deploy work. The operator needs a small, safe, copy-pasteable cleanup handoff that reduces image sprawl without turning into a broader prune or production mutation by an agent. ### What changed Added `prompts/codex-rs2000-image-prune-2026-05-12.md`, a narrow operator-run prompt for `docker image prune -f` on RS2000 with pre-checks, post-checks, safety boundaries, rollback notes, and explicit out-of-scope items. ### Why it changed This is P2 from `prompts/codex-rs2000-close-2026-05-12.md`: a quick win after P0 apply hardening and P1 recovery runbook batches. ### Files touched - `prompts/codex-rs2000-image-prune-2026-05-12.md` ### Relevant context - `prompts/codex-rs2000-close-2026-05-12.md` P2 - `prompts/06-prune.md` for the broader Phase 06 scope this PR intentionally does not perform - ADR-0003 rule from the dispatch: Codex does not SSH-execute production mutations ### Runtime evidence No runtime command was executed by Codex. This PR only adds an operator handoff prompt. ### Known constraints Dangling image prune is non-reversible, but should not affect tagged images, running containers, compose files, or Docker volumes. ### Explicit out-of-scope - `docker system prune` - `docker image prune -a` - `--volumes` - compose changes - container restarts - worktree cleanup - sunset-module cleanup - weekly prune timer / full Phase 06 policy ### Requested decision Approve this docs-only Lite PR if the handoff is clear and appropriately narrow. ### Merge blockers - Any instruction that could delete volumes, tagged images, containers, or worktrees - Any suggestion that Codex should execute the SSH production mutation - Any ambiguity between this narrow dangling-image cleanup and the full Phase 06 prune wave ## Spec sources read - `prompts/codex-rs2000-close-2026-05-12.md` — P2 requirement and hard rule against Codex SSH production mutation - `prompts/06-prune.md` — broader prune scope used to keep this prompt intentionally narrow - `decisions/0007-risk-proportional-canary.md` — Lite tier discipline ## Test plan - `git diff --check` - Confirm prompt contains `docker image prune -f` and explicitly rejects `docker system prune`, `docker image prune -a`, and `--volumes` Closes no issue directly; this is the P2 follow-up from issue #142 close-out.
docs(prompts): add RS2000 dangling image prune handoff
All checks were successful
canary-required / collect-diff (pull_request) Successful in 3s
canary-required / canary (pull_request) Successful in 11s
76ecf57cd8
Author
Collaborator

Codex verification update

Role: executor

Verification for this P2 prompt PR:

  • git diff --check passes.
  • PR adds only prompts/codex-rs2000-image-prune-2026-05-12.md.
  • Prompt explicitly limits action to operator-run docker image prune -f.
  • Prompt explicitly forbids docker system prune, docker image prune -a, --volumes, compose changes, container restarts, tagged image deletion, volume deletion, and worktree cleanup.

Canary note: local canary attempt is blocked because Bitwarden is locked in the agent shell (BW status=locked). No SSH command was run against RS2000.

## Codex verification update **Role:** executor Verification for this P2 prompt PR: - `git diff --check` passes. - PR adds only `prompts/codex-rs2000-image-prune-2026-05-12.md`. - Prompt explicitly limits action to operator-run `docker image prune -f`. - Prompt explicitly forbids `docker system prune`, `docker image prune -a`, `--volumes`, compose changes, container restarts, tagged image deletion, volume deletion, and worktree cleanup. Canary note: local canary attempt is blocked because Bitwarden is locked in the agent shell (`BW status=locked`). No SSH command was run against RS2000.
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
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!232
No description provided.