Add scoop install to readme #1111

New issue

Closed

opened 2026-07-11 15:05:21 +00:00 by coilysiren · 3 comments

coilysiren commented

2026-07-11 15:05:21 +00:00

Owner

The problem

And Linux I guess

Proposed change

Alternatives considered

No response

Before filing

I searched existing issues and this is not a duplicate.
This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

### The problem And Linux I guess ### Proposed change // ### Alternatives considered _No response_ ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

coilysiren commented

2026-07-11 15:06:45 +00:00

Author

Owner

Also just, make the section less noisy, and show the child from source variant

coilyco-ops commented

2026-07-14 06:35:53 +00:00

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1111 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-14T06:35:53Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation 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#1111 · branch issue-1111 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1111 · ward v0.667.0 · dispatched 2026-07-14T06:35:46Z
Comment thread: 1 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilysiren (2026-07-11T15:06:45Z)

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

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1111` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T06:35:53Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` 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#1111` · branch `issue-1111` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1111` · ward `v0.667.0` · dispatched `2026-07-14T06:35:46Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilysiren (2026-07-11T15:06:45Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.667.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-14 06:39:16 +00:00

docs: add Scoop install to README #1228

coilyco-ops closed this issue

2026-07-14 06:40:19 +00:00

coilyco-ops commented

2026-07-14 06:40:55 +00:00

Member

WARDED_WORKFLOW: #1228

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
felt: narrow and straightforward
confidence: high
surprise: none
follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1228 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: narrow and straightforward confidence: high surprise: none follow-ups: none </details>