docs/ops-eco.md: correct stale native=Linux rescope to native=Windows-local + server=Linux-ssh #588

New issue

Closed

opened 2026-07-03 21:14:05 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-03 21:14:05 +00:00

Owner

Problem

ward#585 landed docs/ops-eco.md with a native=Linux-only rescope based on a misread - the run believed Eco was Linux-only and Windows-native was blocked on infrastructure#356.

Correction (per Kai + the corrected infra#461)

Eco is a Steam game that runs on both Linux and Windows. The server runs in both places, prod is the Linux server on kai-server, and Kai runs a Windows server locally for test. So the model is native=Windows-local exec + server=Linux-ssh, exactly the original ward#585 shape.

infrastructure#356 (Ansible role: converge the 5-agent stack on Windows tower hosts) gates only a warded AGENT running on the Windows tower - NOT Eco's ability to run on Windows, and NOT Kai driving the local test herself. So it is not a blocker for the design or the local-test flow.

Fix

Correct docs/ops-eco.md's native/target section to native=Windows-local + server=Linux-ssh, and fix the infra#356 framing to cover only the optional agent-on-tower path. Keep it consistent with the corrected infra#461.

ward#585 (the spec doc), infrastructure#461 (transport wiring, already corrected), infrastructure#356 (agent-tower, the only real infra#356 dependency).

## Problem ward#585 landed `docs/ops-eco.md` with a **native=Linux-only** rescope based on a misread - the run believed Eco was Linux-only and Windows-native was blocked on infrastructure#356. ## Correction (per Kai + the corrected infra#461) Eco is a **Steam game that runs on both Linux and Windows**. The server runs in both places, **prod is the Linux server on kai-server**, and Kai runs a **Windows server locally for test**. So the model is **native=Windows-local exec + server=Linux-ssh**, exactly the original ward#585 shape. infrastructure#356 (*Ansible role: converge the 5-agent stack on Windows tower hosts*) gates only a **warded AGENT running on the Windows tower** - NOT Eco's ability to run on Windows, and NOT Kai driving the local test herself. So it is not a blocker for the design or the local-test flow. ## Fix Correct `docs/ops-eco.md`'s native/target section to **native=Windows-local + server=Linux-ssh**, and fix the infra#356 framing to cover only the optional agent-on-tower path. Keep it consistent with the corrected infra#461. ## Related ward#585 (the spec doc), infrastructure#461 (transport wiring, already corrected), infrastructure#356 (agent-tower, the only real infra#356 dependency).

coilyco-ops commented

2026-07-03 21:14:16 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-588 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-03T21:14:10Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s 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).

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-588` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-03T21:14:10Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s 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).  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-03 21:23:20 +00:00

docs(eco): correct native=Windows-local + server=Linux-ssh (closes #588)

coilysiren closed this issue

2026-07-03 21:23:20 +00:00

coilysiren commented

2026-07-03 21:23:46 +00:00

Author

Owner

WARD-OUTCOME: done - docs/ops-eco.md corrected to native=Windows-local + server=Linux-ssh, landed on main.

Straightforward correction on the substance: the prior ward#585 landing had argued itself into a Linux-only rescope off a misread, so most of the work was replacing that whole "native premise correction" section with the true dual-OS model (Linux prod over ssh, Windows local test over native exec) and reframing infra#356 as gating only the optional agent-on-tower path.

What actually fought back was the 4000-char doc-size cap. The doc was authored at exactly 3999 chars, so every clause I added to carry the extra nuance (both OSes, a second infra issue) blew the cap, and I spent far more effort trimming the whole doc back under budget than on the correction itself. Landed at 3991. One de-linked issue ref also tripped the issue-refs hook, since I'd dropped the ward#585 URL to save space; reworded to "the original design shape" rather than re-inflate.

Confident in the result: content matches Kai's correction and the corrected infra#461, and the full pre-commit suite is green. One rough edge worth noting - this doc lives permanently pinned against the size cap, so the next edit will hit the same wall. Might be worth splitting ops-eco.md or raising its cap if it keeps growing.

WARD-OUTCOME: done - docs/ops-eco.md corrected to native=Windows-local + server=Linux-ssh, landed on main. Straightforward correction on the substance: the prior ward#585 landing had argued itself into a Linux-only rescope off a misread, so most of the work was replacing that whole "native premise correction" section with the true dual-OS model (Linux prod over ssh, Windows local test over native exec) and reframing infra#356 as gating only the optional agent-on-tower path. What actually fought back was the 4000-char doc-size cap. The doc was authored at exactly 3999 chars, so every clause I added to carry the extra nuance (both OSes, a second infra issue) blew the cap, and I spent far more effort trimming the whole doc back under budget than on the correction itself. Landed at 3991. One de-linked issue ref also tripped the issue-refs hook, since I'd dropped the ward#585 URL to save space; reworded to "the original design shape" rather than re-inflate. Confident in the result: content matches Kai's correction and the corrected infra#461, and the full pre-commit suite is green. One rough edge worth noting - this doc lives permanently pinned against the size cap, so the next edit will hit the same wall. Might be worth splitting ops-eco.md or raising its cap if it keeps growing.