Make the reservation folder disposable and safe to clear wholesale #1236
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1236
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1224"
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?
This change treats the reservation directory as disposable cache instead of fragile per-issue local state.
ward agent listnow self-heals a missing cache directory, stale rows prune themselves from durable issue-thread evidence and Docker reality, and theward agent reservations clearcommand gives operators a first-class wholesale cleanup path.closes #1224
ward.workflow: pull-request-and-merge
ward agent reservationsas a meta command.ward exec testpassed.pre-commit run --all-filespassed.This PR is not mergeable yet:
ward agent pr status coilyco-flight-deck/ward#1236reports the pull_request test check failing. Leaving it open for a repair pass rather than merging red.WARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
Implemented the reservation cache as disposable local state, added whole-folder clear, and taught
ward agent listto prune stale cache rows from durable issue state and live Docker state.Validation:
pre-commit run --all-filespassed.go test ./cmd/ward ...passed.ward exec testis blocked by an unrelatedsyncGitReffailure in the existing suite.Retrospective: the cache split was straightforward, but the full-suite failure is outside the reservation path and still needs follow-up.
Confidence: medium.
Follow-up: stabilize the existing
syncGitReftest path, then rerunward exec test.WARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: review gate intentionally skipped by the temporary ward default pending brokered QA
The reservation cache work is validated locally, and PR #1236 is green, but Forgejo's merge endpoint is returning 405 after repeated settle attempts. That blocks landing even though the branch itself is clean.
Validation:
ward exec testpassed.pre-commit run --all-filespassed.Retrospective: the implementation felt straightforward. The remaining blocker is merge-queue pressure, not the reservation cache path.
Confidence: medium.
Surprise: Forgejo's merge queue can still refuse a green PR with a transient 405, and the available API surface does not expose a rerun path.
Follow-up: retry the merge later or have the director sweep the PR once the queue clears.
WARDED_WORKFLOW: blocked 🛑
details
manual close/update snapshot at 2026-07-15T08:00:33Z is newer than the latest ward acknowledgement at 2026-07-15T01:21:53Z
This action is blocked until the feedback is visibly acknowledged.
— Claude (she/her), via
ward agentWARDED_WORKFLOW: blocked 🛑
details
manual close/update snapshot at 2026-07-15T08:00:33Z is newer than the latest ward acknowledgement at 2026-07-15T01:21:53Z
This action is blocked until the feedback is visibly acknowledged.
— Claude (she/her), via
ward agent