Remove ward package-manager update surfaces before release

coilyco-ops commented

2026-07-09 02:25:12 +00:00

Member

Remove the pre-release package-manager surfaces from ward:

Remove ward pkg brew and its brew sandbox shim.
Remove ward upgrade / self-update behavior, including brew and scoop paths.
Remove or simplify any agent upgrade gate that calls the removed update command.
Update docs and tests so release scope no longer advertises package-manager control.
Keep core ward agent, exec, ops, audit, and container behavior intact.

Rationale: this surface is host package management, not core ward release behavior. Pulling it reduces release scope without changing the agent dispatch contract.

Remove the pre-release package-manager surfaces from ward: * Remove `ward pkg brew` and its brew sandbox shim. * Remove `ward upgrade` / self-update behavior, including brew and scoop paths. * Remove or simplify any agent upgrade gate that calls the removed update command. * Update docs and tests so release scope no longer advertises package-manager control. * Keep core ward agent, exec, ops, audit, and container behavior intact. Rationale: this surface is host package management, not core ward release behavior. Pulling it reduces release scope without changing the agent dispatch contract.

coilyco-ops commented

2026-07-09 02:25:34 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-731 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T02:25:32Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#731 · branch issue-731 · harness codex · workflow pr
Run: engineer-codex-ward-731 · ward v0.470.0 · dispatched 2026-07-09T02:25:32Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-731` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T02:25:32Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#731` · branch `issue-731` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-ward-731` · ward `v0.470.0` · dispatched `2026-07-09T02:25:32Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 02:37:31 +00:00

Remove ward package-manager update surfaces before release #745

coilyco-ops commented

2026-07-09 02:37:43 +00:00

Author

Member

WARD-OUTCOME: done - removed ward pkg brew and ward upgrade from ward, pushed issue-731, and opened PR #745
Review: skipped because --skip-preflight / --no-preflight also skips review.
The removal was straightforward once the exec-mount collision was traced. go test ./cmd/ward passed. go test ./... still has unrelated failures in internal/agents/ollamaprobe and opencode.

WARD-OUTCOME: done - removed ward pkg brew and ward upgrade from ward, pushed issue-731, and opened PR #745 Review: skipped because --skip-preflight / --no-preflight also skips review. The removal was straightforward once the exec-mount collision was traced. `go test ./cmd/ward` passed. `go test ./...` still has unrelated failures in internal/agents/ollamaprobe and opencode.

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 02:37:58 +00:00

ward salvage: ward-salvage/ward-649addd7 #746

coilyco-ops commented

2026-07-09 02:38:00 +00:00

Author

Member

⚠️ Reopened: this run's work did not land on `main`

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

Repo: coilyco-flight-deck/ward
Salvage branch: ward-salvage/ward-649addd7
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: run workflow does not land on main (--workflow pr/patch-only)
Container uptime at reap: 12m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              ba097be2b5a8
origin/main:       8cab230822ab
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  12m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

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

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #731 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/ward` - **Salvage branch:** `ward-salvage/ward-649addd7` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 12m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: ba097be2b5a8 origin/main: 8cab230822ab ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 12m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/ward.git ward-salvage/ward-649addd7 git checkout -b ward-salvage/ward-649addd7 FETCH_HEAD ```  — Codex, via `ward agent`

coilyco-ops added the

headless

P1

labels

2026-07-09 07:26:55 +00:00

coilyco-ops commented

2026-07-09 07:26:56 +00:00

Author

Member

Director PR sweep, 2026-07-09T07:26Z:

The stale PR(s) for this issue were closed after a full open-PR sweep showed they carried old branch history from before the recovery merges. Fresh run should start from current main and reapply only this issue: remove ward package-manager update surfaces while keeping core agent/exec/ops/audit/container behavior intact.

Director PR sweep, 2026-07-09T07:26Z: The stale PR(s) for this issue were closed after a full open-PR sweep showed they carried old branch history from before the recovery merges. Fresh run should start from current `main` and reapply only this issue: remove ward package-manager update surfaces while keeping core agent/exec/ops/audit/container behavior intact.

coilyco-ops commented

2026-07-09 07:26:59 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-731 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T07:26:57Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#731 · branch issue-731 · harness codex · workflow pr
Run: engineer-codex-ward-731 · ward v0.474.0 · dispatched 2026-07-09T07:26:57Z
Comment thread: 3 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T02:37:43Z), @coilyco-ops (2026-07-09T02:38:00Z), @coilyco-ops (2026-07-09T07:26:56Z)
- stripped: @coilyco-ops (2026-07-09T02:25:34Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.474.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-731` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T07:26:57Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#731` · branch `issue-731` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-ward-731` · ward `v0.474.0` · dispatched `2026-07-09T07:26:57Z` - **Comment thread:** 3 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T02:37:43Z), @coilyco-ops (2026-07-09T02:38:00Z), @coilyco-ops (2026-07-09T07:26:56Z) - stripped: @coilyco-ops (2026-07-09T02:25:34Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.474.0). </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 15:54:26 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-731 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T15:54:23Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#731 · branch issue-731 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-731 · ward v0.493.0 · dispatched 2026-07-09T15:54:23Z
Comment thread: 3 included in the pre-flight read, 2 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T02:37:43Z), @coilyco-ops (2026-07-09T02:38:00Z), @coilyco-ops (2026-07-09T07:26:56Z)
- stripped: @coilyco-ops (2026-07-09T02:25:34Z), @coilyco-ops (2026-07-09T07:26:59Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-731` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T15:54:23Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#731` · branch `issue-731` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-731` · ward `v0.493.0` · dispatched `2026-07-09T15:54:23Z` - **Comment thread:** 3 included in the pre-flight read, 2 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T02:37:43Z), @coilyco-ops (2026-07-09T02:38:00Z), @coilyco-ops (2026-07-09T07:26:56Z) - stripped: @coilyco-ops (2026-07-09T02:25:34Z), @coilyco-ops (2026-07-09T07:26:59Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 16:09:19 +00:00

Remove ward package-manager update surfaces before release #809

coilyco-ops closed this issue

2026-07-09 16:28:52 +00:00

coilyco-ops commented

2026-07-09 16:29:40 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request-and-merge; review summary: skipped because --skip-review / --no-review-gate felt: the branch cleanup was straightforward after the stale gate test was updated confidence: high surprises: Forgejo CI briefly showed the older failed commit until the newer head finished follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because --skip-review / --no-review-gate felt: the branch cleanup was straightforward after the stale gate test was updated confidence: high surprises: Forgejo CI briefly showed the older failed commit until the newer head finished follow-ups: none </details>

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

Rows
Columns

Remove ward package-manager update surfaces before release #731

⚠️ Reopened: this run's work did not land on main

Reap diagnostics

Recover

⚠️ Reopened: this run's work did not land on `main`