Re-express ward upgrade (brew self-update) as a ward-kdl exec-dialect grant (after pkg brew #94/#95) #173

Closed
opened 2026-06-18 07:44:01 +00:00 by coilysiren · 3 comments
Owner

What

cmd/ward/upgrade.go runs a hand-rolled, audited brew sequence (brew update + brew upgrade coilyco-flight-deck/tap/ward, or brew outdated under --dry) via verb.Spec + (*Runner).WrapVerb + the egress-proxied exec path. It is the ward-specific twin of coily upgrade.

This is the same brew-exec surface that ward#95 ("re-express ward pkg brew as ward-kdl") and ward#94 (pkg passthroughs -> ward-kdl exec-dialect guardfile) convert. Once the brew exec dialect exists, ward upgrade is a thin, fixed-argv exec-dialect grant (or a delegation to the pkg-brew guardfile pinned to the coilyco-flight-deck/tap/ward formula), not a hand-rolled verb.Spec.

Asked-for change

  • After ward#94/#95 land, re-express ward upgrade as a ward-kdl exec-dialect grant: fixed brew update + brew upgrade coilyco-flight-deck/tap/ward, --dry -> brew outdated.
  • Keep the egress-row + stderr-tail audit capture (or confirm the ward-kdl exec transport already captures it).
  • Drop the bespoke upgradeAction / runUpgrade Go once parity is proven.

Dependency: ward#94 and ward#95 (the brew exec dialect must exist first).

Part of the coily -> ward -> ward-kdl consolidation (epic ward#91, milestone #6).

## What `cmd/ward/upgrade.go` runs a hand-rolled, audited brew sequence (`brew update` + `brew upgrade coilyco-flight-deck/tap/ward`, or `brew outdated` under `--dry`) via `verb.Spec` + `(*Runner).WrapVerb` + the egress-proxied exec path. It is the ward-specific twin of `coily upgrade`. This is the same brew-exec surface that ward#95 ("re-express `ward pkg brew` as ward-kdl") and ward#94 (pkg passthroughs -> ward-kdl exec-dialect guardfile) convert. Once the brew exec dialect exists, `ward upgrade` is a thin, fixed-argv exec-dialect grant (or a delegation to the pkg-brew guardfile pinned to the `coilyco-flight-deck/tap/ward` formula), not a hand-rolled `verb.Spec`. ## Asked-for change - After ward#94/#95 land, re-express `ward upgrade` as a ward-kdl exec-dialect grant: fixed `brew update` + `brew upgrade coilyco-flight-deck/tap/ward`, `--dry` -> `brew outdated`. - Keep the egress-row + stderr-tail audit capture (or confirm the ward-kdl exec transport already captures it). - Drop the bespoke `upgradeAction` / `runUpgrade` Go once parity is proven. Dependency: ward#94 and ward#95 (the brew exec dialect must exist first). Part of the coily -> ward -> ward-kdl consolidation (epic ward#91, milestone #6).
Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

  • P3 - Re-express ward upgrade as a ward-kdl grant, concrete, blocked on #94/#95.
  • consult - Blocked on the brew exec dialect, human-gated until those land.
<!-- goose-triage --> **Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Re-express ward upgrade as a ward-kdl grant, concrete, blocked on #94/#95. - **consult** - Blocked on the brew exec dialect, human-gated until those land.
Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

  • P3 - Re-express ward upgrade as a ward-kdl grant, concrete, blocked on #94/#95.
  • consult - Blocked on the brew exec dialect, human-gated until those land.
<!-- goose-triage --> **Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Re-express ward upgrade as a ward-kdl grant, concrete, blocked on #94/#95. - **consult** - Blocked on the brew exec dialect, human-gated until those land.
coilysiren added
P4
and removed
P3
labels 2026-07-01 04:29:55 +00:00
Member

Stays consult: gated on the pkg-brew ward-kdl conversion (#94/#95); becomes a thin exec-dialect grant once those land. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

Stays consult: gated on the pkg-brew ward-kdl conversion (#94/#95); becomes a thin exec-dialect grant once those land. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.
Sign in to join this conversation.
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#173
No description provided.