coilyco-flight-deck/ward

Watch

Ward hardcodes my personal "inbox" concept #1488

New issue

Closed

opened 2026-07-21 01:00:36 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-07-21 01:00:36 +00:00

Owner

No description provided.

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-28 08:54:03 +00:00

coilyco-ops referenced this issue from a commit

2026-07-28 10:27:10 +00:00

Make route intake repo configurable

coilyco-ops closed this issue

2026-07-28 10:27:10 +00:00

coilyco-ops commented

2026-07-28 10:34:21 +00:00

Member

WARD-WORKFLOW: done ✅

details

workflow: merge-remote-main; review summary: skipped - the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA.

summary: Moved route intake from Go constants to bundled smart defaults (route-intake-repo); route filing, survey filtering, dry-run output, and target rejection now use that policy value. Removed personal inbox references from docs/tests except the explicit deployed default in .ward/defaults.kdl.

tests: ward exec test; ward exec build; ward exec vet; ward exec lint; WARD_DOCTOR_ALLOW_PLACEHOLDERS=1 ward doctor. Plain ward doctor still hits the existing placeholder fleet attribution check.

release: my promote run was superseded by a newer main push; current origin/main contains this work, promote run 2515 succeeded, and release run 2516 succeeded. Binary refresh skipped because Homebrew is not installed in this container.

felt: small but cross-cutting; the main friction was hook-shaped, not implementation-shaped.
confidence: high.
surprises: ward exec tidy wanted unrelated module metadata churn, so I reversed it before committing.
follow-ups: choose a non-personal deployment intake repo when one exists.

WARD-WORKFLOW: done ✅ <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped - the in-container review gate was intentionally skipped because the temporary ward default is pending brokered QA. summary: Moved route intake from Go constants to bundled smart defaults (`route-intake-repo`); route filing, survey filtering, dry-run output, and target rejection now use that policy value. Removed personal inbox references from docs/tests except the explicit deployed default in `.ward/defaults.kdl`. tests: `ward exec test`; `ward exec build`; `ward exec vet`; `ward exec lint`; `WARD_DOCTOR_ALLOW_PLACEHOLDERS=1 ward doctor`. Plain `ward doctor` still hits the existing placeholder fleet attribution check. release: my promote run was superseded by a newer main push; current `origin/main` contains this work, promote run 2515 succeeded, and release run 2516 succeeded. Binary refresh skipped because Homebrew is not installed in this container. felt: small but cross-cutting; the main friction was hook-shaped, not implementation-shaped. confidence: high. surprises: `ward exec tidy` wanted unrelated module metadata churn, so I reversed it before committing. follow-ups: choose a non-personal deployment intake repo when one exists. </details>

coilyco-ops reopened this issue

2026-07-28 10:34:28 +00:00

coilyco-ops commented

2026-07-28 10:34:28 +00:00

Member

WARD-WORKFLOW: blocked 🛑

salvage details

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #1488 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/ward
Salvage branch: ward-salvage/ward-a832df03
Pull request: not opened - salvage branch has no diff against main
Reason: merge conflict integrating onto main
Container uptime at reap: 17m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Cleanup diagnostics

--- reap diagnostics ---
ward version:      v0.823.0
version source:    pinned via WARD_VERSION/--ward-version (v0.823.0)
HEAD:              8879c360aef3
origin/main:       8879c360aef3
ancestry:          HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature)
decision gate:     provenance missing or unreadable on already-landed merge-remote-main run
reason:            merge conflict integrating onto main
provenance:        missing or unreadable
run-owned landed:  no
working tree:      clean
container uptime:  17m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-a832df03
git checkout -b ward-salvage/ward-a832df03 FETCH_HEAD

— Codex, via ward agent

WARD-WORKFLOW: blocked 🛑 <details><summary>salvage details</summary> An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #1488 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/ward` - **Salvage branch:** `ward-salvage/ward-a832df03` - **Pull request:** not opened - salvage branch has no diff against main - **Reason:** merge conflict integrating onto main - **Container uptime at reap:** 17m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Cleanup diagnostics ``` --- reap diagnostics --- ward version: v0.823.0 version source: pinned via WARD_VERSION/--ward-version (v0.823.0) HEAD: 8879c360aef3 origin/main: 8879c360aef3 ancestry: HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature) decision gate: provenance missing or unreadable on already-landed merge-remote-main run reason: merge conflict integrating onto main provenance: missing or unreadable run-owned landed: no working tree: clean container uptime: 17m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-a832df03 git checkout -b ward-salvage/ward-a832df03 FETCH_HEAD ``` </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-28 10:34:28 +00:00

Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-ward-1488 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: blocked 🛑`. `ward container reap` released container `engineer-codex-ward-1488` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-28 10:36:32 +00:00

Member

Director cleanup: closing this manually because the run completed despite the later false salvage notice. Proof from the archived run: posted WARD-WORKFLOW: done; current origin/main contains the work via 8879c360; promote #2515 and release #2516 succeeded; salvage branch had no diff against main. The false-salvage bug was fixed in coilyco-flight-deck/ward#1606, but this container reaped under old pinned Ward v0.823.

Director cleanup: closing this manually because the run completed despite the later false salvage notice. Proof from the archived run: posted WARD-WORKFLOW: done; current origin/main contains the work via 8879c360; promote #2515 and release #2516 succeeded; salvage branch had no diff against main. The false-salvage bug was fixed in coilyco-flight-deck/ward#1606, but this container reaped under old pinned Ward v0.823.

coilyco-ops closed this issue

2026-07-28 10:36:41 +00:00

No milestone

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

coilyco-flight-deck/ward#1488

No description provided.

Rows
Columns