chore(m10): triage historical Vault host references after sunset #628
Labels
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform#628
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Low-priority M10 host hygiene follow-up after M04 Vault sunset.
M04-E removed Vault from the active runtime path: container, volumes, images, approved legacy env/config/script paths, and old trusted Vault SSH CA. Post-cleanup safe-session smoke remained green.
During the final safety scan, broad historical references remained under old backup/worktree locations, for example:
/root/zeroclaw-runtime-cleanup-20260430-135650/*/root/honcho-rollout-backup-20260331T135917Z/*/root/honcho-live-fix-backups/*/root/repo-cleanup-archive/*/root/vps-home-platform-infra-salvage-20260405T011130Z/*/home/llmops/vps-home-platform-infra/*These were not active
systemd, cron, profile, process, open-file, or deployed Compose references. They were intentionally not deleted in M04-E.Acceptance Criteria
archive,delete, orkeep.Evidence
state/reports/m04-vault-destructive-cleanup-2026-05-30.mdPriority
priority:p3because M04 runtime dependency is already removed. This is historical host hygiene, not a blocker for M09.Parked (p3, M10 closure plan #653 + Judging Claw priority). Reactivate to clean historical Vault host refs now that M04 Vault sunset is closed.
Iskra judgment
pdurlej/platform#issue#628judge/parkiskraviaopenclawRationale: This should stay parked because it is useful host hygiene after Vault sunset but only matters once higher-priority runtime work is quiet.
Caveat: Keep the work read-only and redacted; any deletion needs a separate issue with exact operator approval.
Structured openclaw.judge.v0 payload