Make the reservation folder disposable and safe to clear wholesale #1236

Closed
coilyco-ops wants to merge 4 commits from issue-1224 into main
Member

This change treats the reservation directory as disposable cache instead of fragile per-issue local state. ward agent list now self-heals a missing cache directory, stale rows prune themselves from durable issue-thread evidence and Docker reality, and the ward agent reservations clear command gives operators a first-class wholesale cleanup path.

closes #1224

ward.workflow: pull-request-and-merge

  • The flag-tree doc now includes ward agent reservations as a meta command.
  • ward exec test passed.
  • pre-commit run --all-files passed.
This change treats the reservation directory as disposable cache instead of fragile per-issue local state. `ward agent list` now self-heals a missing cache directory, stale rows prune themselves from durable issue-thread evidence and Docker reality, and the `ward agent reservations clear` command gives operators a first-class wholesale cleanup path. closes #1224 ward.workflow: pull-request-and-merge - The flag-tree doc now includes `ward agent reservations` as a meta command. - `ward exec test` passed. - `pre-commit run --all-files` passed.
fix: make reservation cache disposable
Some checks failed
test / test (pull_request) Failing after 51s
c0098789eb
Author
Member

This PR is not mergeable yet: ward agent pr status coilyco-flight-deck/ward#1236 reports the pull_request test check failing. Leaving it open for a repair pass rather than merging red.

This PR is not mergeable yet: `ward agent pr status coilyco-flight-deck/ward#1236` reports the pull_request test check failing. Leaving it open for a repair pass rather than merging red.
Author
Member

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 list to prune stale cache rows from durable issue state and live Docker state.

Validation:

  • pre-commit run --all-files passed.
  • Targeted go test ./cmd/ward ... passed.
  • Full ward exec test is blocked by an unrelated syncGitRef failure 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 syncGitRef test path, then rerun ward exec test.

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> 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 list` to prune stale cache rows from durable issue state and live Docker state. Validation: - `pre-commit run --all-files` passed. - Targeted `go test ./cmd/ward ...` passed. - Full `ward exec test` is blocked by an unrelated `syncGitRef` failure 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 `syncGitRef` test path, then rerun `ward exec test`. <!-- ward-agent-signature --> </details>
fix: make reservation cache disposable
Some checks failed
test / test (pull_request) Failing after 10m15s
6407eef0ac
fix: classify reservation cache cleanup as meta
Some checks failed
test / test (pull_request) Failing after 49s
29cbe106a4
chore: retrigger pr checks
All checks were successful
test / test (pull_request) Successful in 1m45s
89e28ae654
Author
Member

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 test passed.
  • pre-commit run --all-files passed.

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><summary>details</summary> 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 test` passed. - `pre-commit run --all-files` passed. 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. <!-- ward-agent-signature --> </details>
coilysiren closed this pull request 2026-07-15 02:10:01 +00:00
coilyco-ops reopened this pull request 2026-07-15 07:49:42 +00:00
coilyco-ops closed this pull request 2026-07-15 08:00:33 +00:00
Author
Member

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 agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> 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. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Author
Member

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 agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> 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. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
All checks were successful
test / test (pull_request) Successful in 1m45s

Pull request closed

Sign in to join this conversation.
No description provided.