move (much) more of entrypoint.sh into ward golang code

coilysiren commented

2026-07-03 02:46:20 +00:00

Owner

Which surface

The agent driver (ward agent / warded)

What happened

//

What you expected

//

Steps to reproduce

//

ward version

//

OS and install method

//

Before filing

I searched existing issues and this is not a duplicate.
This is not a security vulnerability (those follow SECURITY.md).

### Which surface The agent driver (ward agent / warded) ### What happened // ### What you expected // ### Steps to reproduce // ### ward version // ### OS and install method // ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This is not a security vulnerability (those follow SECURITY.md).

coilyco-ops added the

consult

P1

labels

2026-07-03 17:30:05 +00:00

coilysiren commented

2026-07-03 18:20:01 +00:00

Author

Owner

Not a bug - a refactor (the title is the spec). Ignore the empty bug-report template body. The ask: continue porting entrypoint.sh bash into ward Go.

Headless-ready with scope guidance: follow the established porting precedent - warmSubstrate / warmSubstrateRepo in cmd/ward/container_bootstrap.go are already ported entrypoint.sh functions ("ports warm_substrate_repo"). Port the next coherent tranche of entrypoint.sh into methods on Runner, with ward exec test as the guard, rather than boiling the ocean in one run. Leave clearly-shell-shaped glue (exec/env wiring that has no clean Go home) in bash and say what was left and why.

**Not a bug - a refactor (the title is the spec).** Ignore the empty bug-report template body. The ask: continue porting `entrypoint.sh` bash into ward Go. **Headless-ready with scope guidance:** follow the established porting precedent - `warmSubstrate` / `warmSubstrateRepo` in `cmd/ward/container_bootstrap.go` are already ported entrypoint.sh functions ("ports warm_substrate_repo"). Port the **next coherent tranche** of entrypoint.sh into methods on `Runner`, with `ward exec test` as the guard, rather than boiling the ocean in one run. Leave clearly-shell-shaped glue (exec/env wiring that has no clean Go home) in bash and say what was left and why.

coilyco-ops added

headless

and removed

consult

labels

2026-07-09 18:25:08 +00:00

coilyco-ops commented

2026-07-09 18:25:09 +00:00

Member

Consult interrogation: this is now headless-ready. The issue has a concrete implementation target and acceptance criteria, with no remaining human decision needed before an engineer can carry it.

coilyco-ops commented

2026-07-09 18:30:12 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T18:30:09Z). 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#541 · branch issue-541 · harness codex · workflow pull-request
Run: engineer-codex-ward-541 · ward v0.493.0 · dispatched 2026-07-09T18:30:09Z
Comment thread: 2 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilysiren (2026-07-03T18:20:01Z), @coilyco-ops (2026-07-09T18:25:09Z)

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-541` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T18:30:09Z). 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#541` · branch `issue-541` · harness `codex` · workflow `pull-request` - **Run:** `engineer-codex-ward-541` · ward `v0.493.0` · dispatched `2026-07-09T18:30:09Z` - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilysiren (2026-07-03T18:20:01Z), @coilyco-ops (2026-07-09T18:25:09Z) 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 18:40:48 +00:00

refactor: stage Go bootstrap binaries for container entrypoint #851

coilyco-ops commented

2026-07-09 18:47:29 +00:00

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request; review summary: skipped by ~/.ward/config.yaml default (review gate skipped by ~/.ward/config.yaml default)
felt: the Go-bootstrap staging path fit the existing launch seam cleanly after the lint cleanup.
confidence: high
surprises: Forgejo exposed the failing job summary in HTML before the raw log payload, so I reproduced lint locally to fix it.
follow-ups: none.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request; review summary: skipped by ~/.ward/config.yaml default (review gate skipped by ~/.ward/config.yaml default) felt: the Go-bootstrap staging path fit the existing launch seam cleanly after the lint cleanup. confidence: high surprises: Forgejo exposed the failing job summary in HTML before the raw log payload, so I reproduced lint locally to fix it. follow-ups: none. </details>

coilyco-ops commented

2026-07-09 20:12:24 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T20:12:22Z). 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#541 · branch issue-541 · harness codex · workflow direct-to-main
Run: engineer-codex-ward-541 · ward v0.522.0 · dispatched 2026-07-09T20:12:22Z
Comment thread: 3 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilysiren (2026-07-03T18:20:01Z), @coilyco-ops (2026-07-09T18:25:09Z), @coilyco-ops (2026-07-09T18:47:29Z)
- stripped: @coilyco-ops (2026-07-09T18:30:12Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-541` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T20:12:22Z). 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#541` · branch `issue-541` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-ward-541` · ward `v0.522.0` · dispatched `2026-07-09T20:12:22Z` - **Comment thread:** 3 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilysiren (2026-07-03T18:20:01Z), @coilyco-ops (2026-07-09T18:25:09Z), @coilyco-ops (2026-07-09T18:47:29Z) - stripped: @coilyco-ops (2026-07-09T18:30:12Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

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

Merge remote-tracking branch 'origin/main' into issue-541

coilyco-ops closed this issue

2026-07-09 20:16:47 +00:00

coilyco-ops commented

2026-07-09 20:17:17 +00:00

Member

WARD-OUTCOME: done

details

workflow: pull-request; review summary: skipped by ~/.ward/config.yaml default. felt: mechanical merge repair after integrating current main. confidence: high. surprises: only the docs/FEATURES merge conflict. follow-ups: none.

WARD-OUTCOME: done <details><summary>details</summary> workflow: pull-request; review summary: skipped by ~/.ward/config.yaml default. felt: mechanical merge repair after integrating current main. confidence: high. surprises: only the docs/FEATURES merge conflict. follow-ups: none. </details>

coilyco-ops referenced this issue

2026-07-09 20:21:37 +00:00

Complete the actual entrypoint.sh to Go port requested by #541 #866

coilyco-ops referenced this issue

2026-07-09 20:21:52 +00:00

refactor: stage Go bootstrap binaries for container entrypoint #851

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