Make agent-proxy a reproducible local container target for engineer runs #20

New issue

Closed

opened 2026-07-02 04:51:51 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-07-02 04:51:51 +00:00

Owner

The phase-1 proxy itself is stable enough to target locally as a process, but a fresh local-container workflow is not yet first-class.

Evidence from the director pass:

the offline suite passes cleanly once dev dependencies are installed: 26 passed
there is no repo-local container artifact yet (Dockerfile, Containerfile, compose file, Caddyfile, or local deploy wrapper)
the documented operator path is not reproducible from a fresh surfaced checkout as written: uv run pytest failed until uv sync --extra dev, and ward invocation shape is inconsistent in docs versus this environment

Acceptance criteria:

add the minimal container artifact(s) needed to run the proxy locally in a reproducible way
keep the scope to phase 1 reliability proxy work. no capability-phase features
make the local run path usable by an engineer targeting the proxy from another session or container
document the exact startup path, required env, and how an engineer should point at it
fix any repo-local command/doc drift that blocks a fresh checkout from running tests or starting the proxy
update README / FEATURES / proxy walkthrough if the runnable surface changes materially

The phase-1 proxy itself is stable enough to target locally as a process, but a fresh local-container workflow is not yet first-class. Evidence from the director pass: - the offline suite passes cleanly once dev dependencies are installed: `26 passed` - there is no repo-local container artifact yet (`Dockerfile`, `Containerfile`, compose file, Caddyfile, or local deploy wrapper) - the documented operator path is not reproducible from a fresh surfaced checkout as written: `uv run pytest` failed until `uv sync --extra dev`, and `ward` invocation shape is inconsistent in docs versus this environment Acceptance criteria: - add the minimal container artifact(s) needed to run the proxy locally in a reproducible way - keep the scope to phase 1 reliability proxy work. no capability-phase features - make the local run path usable by an engineer targeting the proxy from another session or container - document the exact startup path, required env, and how an engineer should point at it - fix any repo-local command/doc drift that blocks a fresh checkout from running tests or starting the proxy - update README / FEATURES / proxy walkthrough if the runnable surface changes materially

coilyco-ops commented

2026-07-02 04:51:58 +00:00

Member

🔒 Reserved by ward agent --driver goose — container engineer-goose-agent-proxy-20 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T04:51:56Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Goose, via ward agent

🔒 Reserved by `ward agent --driver goose` — container `engineer-goose-agent-proxy-20` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T04:51:56Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Goose, via `ward agent`

coilysiren closed this issue

2026-07-02 05:15:00 +00:00