vps-home-platform-infra dirty worktree on salvage branch #47

Closed
opened 2026-05-03 23:30:22 +02:00 by claude · 1 comment
Collaborator

Migrated from state/L3/OPEN_LOOPS.md (mentioned in 5+ Codex threads, never closed).

Source

state/L3/OPEN_LOOPS.md 'vps-home-platform-infra dirty worktree' section. Mentioned in Codex threads 4b46a4ae (Apr 1), 1302bc10 (Apr 1), 2609f6f0 (Apr 25), 305b0e67 (Apr 2), 019dcbbf (Apr 26).

What

The RS2000 /opt/vps-home-platform-infra/ repo is on branch codex/main-salvage-2026-04-11salvage mode, not stable main. Each thread historically punted to 'later'. Today operator confirms still on salvage.

Why this blocks

Platform repo (this repo) describes desired state. Runtime repo (vps-home-platform-infra on RS2000) holds compose definitions + env files. If runtime repo is on salvage branch, the source of truth for compose snippets cited in module manifests is itself fragile.

Owner action

TASK: clean up vps-home-platform-infra before Phase 03 (control-plane build) — platformctl will need to plan/apply against a stable runtime repo.

Acceptance criteria

  • Audit current state of vps-home-platform-infra (what's diverged on salvage branch vs main)
  • Decide: rebase salvage onto main, OR adopt salvage as new main, OR isolated cleanup PR
  • Get back to clean main branch with linear history
  • Issue closed when git status is clean + branch is main

Reference

Mentioned 5+ times in OPEN_LOOPS — this is a real recurring issue, not a one-time hiccup. Phase 03 cannot start cleanly without it.

Migrated from `state/L3/OPEN_LOOPS.md` (mentioned in 5+ Codex threads, never closed). ## Source `state/L3/OPEN_LOOPS.md` 'vps-home-platform-infra dirty worktree' section. Mentioned in Codex threads `4b46a4ae` (Apr 1), `1302bc10` (Apr 1), `2609f6f0` (Apr 25), `305b0e67` (Apr 2), `019dcbbf` (Apr 26). ## What The RS2000 `/opt/vps-home-platform-infra/` repo is on branch `codex/main-salvage-2026-04-11` — *salvage* mode, not stable main. Each thread historically punted to 'later'. Today operator confirms still on salvage. ## Why this blocks Platform repo (this repo) describes desired state. Runtime repo (`vps-home-platform-infra` on RS2000) holds compose definitions + env files. If runtime repo is on salvage branch, the source of truth for compose snippets cited in module manifests is itself fragile. ## Owner action TASK: clean up vps-home-platform-infra before Phase 03 (control-plane build) — platformctl will need to plan/apply against a stable runtime repo. ## Acceptance criteria - [ ] Audit current state of `vps-home-platform-infra` (what's diverged on salvage branch vs main) - [ ] Decide: rebase salvage onto main, OR adopt salvage as new main, OR isolated cleanup PR - [ ] Get back to clean `main` branch with linear history - [ ] Issue closed when `git status` is clean + branch is `main` ## Reference Mentioned 5+ times in OPEN_LOOPS — this is a real recurring issue, not a one-time hiccup. Phase 03 cannot start cleanly without it.
Collaborator

Codex Wave 1 M01 closeout — superseded by control-plane cutoff boundary

Role: executor
Action: closing as superseded

The original blocker assumed /opt/vps-home-platform-infra needed to become a clean active runtime repo before platformctl/Phase 03 could proceed. That premise is no longer current.

Current durable boundary:

  • /opt/pdurlej-platform/current is the operational control-plane source of truth.
  • /opt/vps-home-platform-infra is legacy rollback/data/config material, not the active control-plane repo.
  • Legacy cleanup is tracked by #387 and governed by ADR-0020 plus state/cutover/rs2000-post-soak-legacy-cleanup.md.

So the dirty/salvage worktree is no longer a Phase 03 blocker. Any remaining value/risk in that tree should be classified during #387 Phase 0 inventory before delete/move decisions.

No runtime mutation was performed.

## Codex Wave 1 M01 closeout — superseded by control-plane cutoff boundary **Role:** executor **Action:** closing as superseded The original blocker assumed `/opt/vps-home-platform-infra` needed to become a clean active runtime repo before platformctl/Phase 03 could proceed. That premise is no longer current. Current durable boundary: - `/opt/pdurlej-platform/current` is the operational control-plane source of truth. - `/opt/vps-home-platform-infra` is legacy rollback/data/config material, not the active control-plane repo. - Legacy cleanup is tracked by #387 and governed by ADR-0020 plus `state/cutover/rs2000-post-soak-legacy-cleanup.md`. So the dirty/salvage worktree is no longer a Phase 03 blocker. Any remaining value/risk in that tree should be classified during #387 Phase 0 inventory before delete/move decisions. No runtime mutation was performed.
codex closed this issue 2026-05-24 08:24:19 +02:00
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 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#47
No description provided.