Use coilysiren/example as ward real placeholder repo

coilyco-ops commented

2026-07-10 02:24:58 +00:00

Member

Use https://github.com/coilysiren/example as ward's placeholder/default example repo wherever ward needs a concrete repo that should actually resolve.

Context:

Kai identified coilysiren/example as the right placeholder target.
The repo is public on GitHub, owned by Kai, and its description is: example repo used as a placeholder ward repo authority target.
git ls-remote https://github.com/coilysiren/example.git HEAD resolves today to 3507bb340294a43d8a00dea798c34068d47863bc.
This gives ward a real GitHub-hosted target for examples and defaults instead of synthetic owners like example-owner.

Scope:

Replace non-resolving placeholder/default refs like example-owner, example-owner-a, example-owner-b, and docs examples that are meant to be runnable or resolvable with coilysiren/example or https://github.com/coilysiren/example.
Review baked/generated default authority behavior, first-run docs, trust-gate docs, GitHub-agent docs, and tests/fixtures so the default/example path consistently points at a real public GitHub repo.
Keep pure grammar metavars such as owner/repo#N when the text is teaching syntax rather than giving a runnable target.
Keep endpoint, token, and owner-glob placeholders in neutral ward-kdl authoring examples when they are intentionally abstract and not repo targets.
Coordinate with #929 so the default example does not preserve any dependency on runtime KDL/specgen for ward core behavior.

Acceptance:

A fresh/default ward build no longer surfaces example-owner as the trusted-owner example in user-facing paths.
User-facing first-run or trust-gate examples that are meant to resolve use coilysiren/example or the GitHub URL.
Tests cover the selected default/example authority target and preserve grammar-only placeholders where appropriate.
Docs explain that coilysiren/example is a real public GitHub placeholder target, not a deployment-specific requirement.

Use https://github.com/coilysiren/example as ward's placeholder/default example repo wherever ward needs a concrete repo that should actually resolve. Context: * Kai identified `coilysiren/example` as the right placeholder target. * The repo is public on GitHub, owned by Kai, and its description is: `example repo used as a placeholder ward repo authority target`. * `git ls-remote https://github.com/coilysiren/example.git HEAD` resolves today to `3507bb340294a43d8a00dea798c34068d47863bc`. * This gives ward a real GitHub-hosted target for examples and defaults instead of synthetic owners like `example-owner`. Scope: * Replace non-resolving placeholder/default refs like `example-owner`, `example-owner-a`, `example-owner-b`, and docs examples that are meant to be runnable or resolvable with `coilysiren/example` or `https://github.com/coilysiren/example`. * Review baked/generated default authority behavior, first-run docs, trust-gate docs, GitHub-agent docs, and tests/fixtures so the default/example path consistently points at a real public GitHub repo. * Keep pure grammar metavars such as `owner/repo#N` when the text is teaching syntax rather than giving a runnable target. * Keep endpoint, token, and owner-glob placeholders in neutral ward-kdl authoring examples when they are intentionally abstract and not repo targets. * Coordinate with #929 so the default example does not preserve any dependency on runtime KDL/specgen for ward core behavior. Acceptance: * A fresh/default ward build no longer surfaces `example-owner` as the trusted-owner example in user-facing paths. * User-facing first-run or trust-gate examples that are meant to resolve use `coilysiren/example` or the GitHub URL. * Tests cover the selected default/example authority target and preserve grammar-only placeholders where appropriate. * Docs explain that `coilysiren/example` is a real public GitHub placeholder target, not a deployment-specific requirement.

coilyco-ops added the

headless

P1

labels

2026-07-10 02:24:58 +00:00

coilyco-ops commented

2026-07-10 02:25:41 +00:00

Author

Member

Dispatch attempt from the read-only director surface was forwarded to the host broker at 2026-07-10T02:25:13Z, but no WARD-RESERVATION comment appeared after the follow-up read.

Host log path printed by the broker: /Users/kai/.ward/agent-logs/dispatch/20260710T022513Z-director-codex-zv98-coilyco-flight-deck-ward-930.log.

This looks like the same active dispatch blockage tracked in #929. The issue is labeled and ready for headless work once host dispatch can reserve again.

Dispatch attempt from the read-only director surface was forwarded to the host broker at 2026-07-10T02:25:13Z, but no WARD-RESERVATION comment appeared after the follow-up read. Host log path printed by the broker: `/Users/kai/.ward/agent-logs/dispatch/20260710T022513Z-director-codex-zv98-coilyco-flight-deck-ward-930.log`. This looks like the same active dispatch blockage tracked in #929. The issue is labeled and ready for headless work once host dispatch can reserve again.

coilyco-ops referenced this issue

2026-07-10 03:29:45 +00:00

Remove runtime KDL/specgen dependency from ward core paths #929

coilyco-ops referenced this issue

2026-07-10 04:42:59 +00:00

Add ward doctor config validation command #940

coilyco-ops commented

2026-07-10 17:19:01 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T17:19:00Z). 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#930 · branch issue-930 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-930 · ward v0.584.0 · dispatched 2026-07-10T17:19:00Z
Comment thread: 1 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T02:25:41Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-930` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T17:19:00Z). 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#930` · branch `issue-930` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-930` · ward `v0.584.0` · dispatched `2026-07-10T17:19:00Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T02:25:41Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 17:33:44 +00:00

Use coilysiren/example as ward real placeholder repo #1055

coilyco-ops commented

2026-07-10 17:35:46 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
The in-container review gate was intentionally skipped because review gate skipped by ~/.ward/config.yaml default.
felt: steady but broad, because the positive-path default had to move across the baked bundle, fixtures, tests, and docs together.
confidence: high
surprises: unrelated ops and exec bundle placeholders still fail doctor, so the assertion had to stay scoped to repo authority.
follow-ups: none

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The in-container review gate was intentionally skipped because review gate skipped by ~/.ward/config.yaml default. felt: steady but broad, because the positive-path default had to move across the baked bundle, fixtures, tests, and docs together. confidence: high surprises: unrelated ops and exec bundle placeholders still fail doctor, so the assertion had to stay scoped to repo authority. follow-ups: none </details>

coilyco-ops commented

2026-07-10 18:13:09 +00:00

Author

Member

WARD-DISPATCH: failed ❌

failure details

This forwarded dispatch failed after the issue was already reserved.

Attempted harness: codex
Attempted run: ward agent engineer coilyco-flight-deck/ward#930 --harness codex --ward-version v0.584.0 --details Conflict-repair assignment from the director merge queue. Existing PR #1055 is blocked by file conflicts on branch issue-930. Start from that existing branch, update it against current main, resolve only the conflicts needed to make PR #1055 mergeable, run the repo allowed validation, and push the same branch. Do not open a replacement PR and do not broaden the feature scope.
Container: engineer-codex-ward-930
Container created: no running engineer was observed.
Host log: /Users/kai/.ward/agent-logs/dispatch/20260710T181302Z-director-codex-cz57-coilyco-flight-deck-ward-930.log
Failure: ward agent engineer --harness codex: issue coilyco-flight-deck/ward#930 is already reserved remotely (by @coilyco-ops at 2026-07-10T17:19:01Z); wait for it to finish or pass --force to override

Retry: choose another harness if the first one is down, or rerun with --force if the reservation is stale.

— Codex, via ward agent

WARD-DISPATCH: failed ❌ <details><summary>failure details</summary> This forwarded dispatch failed after the issue was already reserved. Attempted harness: `codex` Attempted run: `ward agent engineer coilyco-flight-deck/ward#930 --harness codex --ward-version v0.584.0 --details Conflict-repair assignment from the director merge queue. Existing PR #1055 is blocked by file conflicts on branch issue-930. Start from that existing branch, update it against current main, resolve only the conflicts needed to make PR #1055 mergeable, run the repo allowed validation, and push the same branch. Do not open a replacement PR and do not broaden the feature scope.` Container: `engineer-codex-ward-930` Container created: no running engineer was observed. Host log: `/Users/kai/.ward/agent-logs/dispatch/20260710T181302Z-director-codex-cz57-coilyco-flight-deck-ward-930.log` Failure: `ward agent engineer --harness codex: issue coilyco-flight-deck/ward#930 is already reserved remotely (by @coilyco-ops at 2026-07-10T17:19:01Z); wait for it to finish or pass --force to override` Retry: choose another harness if the first one is down, or rerun with `--force` if the reservation is stale. </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 19:30:46 +00:00

Author

Member

Post-mortem (director surface): PR #1055 for this issue was closed. It reintroduced .ward/ward-kdl/ specgen bundle files, which ward#1009 deleted and forbids restoring. This issue stays open. When the ward open-PR queue is under the backpressure threshold (6), re-cut a clean fix off current main that touches CONSUMER CODE ONLY and never restores .ward/ward-kdl/.

Post-mortem (director surface): PR #1055 for this issue was closed. It reintroduced `.ward/ward-kdl/` specgen bundle files, which ward#1009 deleted and forbids restoring. This issue stays open. When the ward open-PR queue is under the backpressure threshold (6), re-cut a clean fix off current main that touches CONSUMER CODE ONLY and never restores `.ward/ward-kdl/`.

coilyco-ops commented

2026-07-10 23:22:58 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-930 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-10T23:22: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#930 · branch issue-930 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-930 · ward v0.605.0 · dispatched 2026-07-10T23:22:57Z
Comment thread: 4 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T02:25:41Z), @coilyco-ops (2026-07-10T17:35:46Z), @coilyco-ops (2026-07-10T18:13:09Z), @coilyco-ops (2026-07-10T19:30:46Z)
- stripped: @coilyco-ops (2026-07-10T17:19:01Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-930` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T23:22: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#930` · branch `issue-930` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-930` · ward `v0.605.0` · dispatched `2026-07-10T23:22:57Z` - **Comment thread:** 4 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T02:25:41Z), @coilyco-ops (2026-07-10T17:35:46Z), @coilyco-ops (2026-07-10T18:13:09Z), @coilyco-ops (2026-07-10T19:30:46Z) - stripped: @coilyco-ops (2026-07-10T17:19:01Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.605.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 23:33:48 +00:00

Use coilysiren/example as ward real placeholder repo #1106

coilyco-ops closed this issue

2026-07-10 23:35:01 +00:00

coilyco-ops commented

2026-07-10 23:35:52 +00:00

Author

Member

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: review gate skipped because temporary ward default pending brokered QA
The in-container review gate was intentionally skipped because temporary ward default pending brokered QA.
felt: steady, with a narrow fix after merging current main and trimming the stale placeholder owner paths.
confidence: high
surprises: the branch already carried the newer bundle-shaped fixtures, so the remaining work was just aligning the last exact placeholder refs.
follow-ups: PR #1106 is open and green.

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped because temporary ward default pending brokered QA The in-container review gate was intentionally skipped because temporary ward default pending brokered QA. felt: steady, with a narrow fix after merging current main and trimming the stale placeholder owner paths. confidence: high surprises: the branch already carried the newer bundle-shaped fixtures, so the remaining work was just aligning the last exact placeholder refs. follow-ups: PR #1106 is open and green. </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

Use coilysiren/example as ward real placeholder repo #930