项目文件夹

文件
Codex 0d9279cbdc
Run Tests / Unit Tests (push) Has been cancelled
govulncheck / govulncheck (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
Harness (E2E) / Harnesses (mock LLM) (push) Has been cancelled
Harness (E2E) / Provider harnesses (live LLM conformance) (push) Has been cancelled
Run Tests / Etcd Integration Tests (push) Has been cancelled
Refresh planner priorities for 4681
2026-07-11 09:43:09 +00:00

2.2 KiB

Priorities

The ranked work queue for the autonomous improvement loop. The architecture-review pass (the architect) owns this file: each run it turns the roadmap plus an internal scan (gaps in the services → agents → workflows lifecycle, API coherence, drift, tech debt, test and DX friction) into a single ordered list — highest-value first — and links each item to a tracking issue. The hourly continuous-improvement pass works the top item whose issue is still open. So the architect decides what, and the increment loop builds it.

Reading / editing. An item is done when its linked issue closes (the increment that builds it adds Closes #<issue>). Roadmap phase (Now → Next → Later) is the primary ordering; internal findings are interleaved by value, not kept in a separate list. The human can reorder this list — or the issues — at any time to redirect the loop; direction always wins.

Off-limits to the loop (the architect proposes these as notes, never as queue items the loop can auto-merge): brand/positioning copy, breaking public-API changes, architectural rewrites. Those go to the human.

Work queue (ranked)

  1. Stabilize first-agent CLI fixture registration wait (#4680) — Developer adoption is the current goal, and the first-agent chat/inspect fixture is part of the Now-roadmap getting-started contract. Make the provider-free fixture prove the assistant agent is registered before micro chat runs so scaffold → run → chat → inspect remains a reliable CI-verified on-ramp instead of a flaky promise.
  2. Harden agent provider failure resilience (#4650) — With scheduled cross-provider conformance closed by #4678, the next reliability seam is making timeouts, cancellation, rate limits, retry/backoff, and inspectable failure metadata predictable through the agent loop. Keep this scoped to existing behavior and tests; surface any breaking API or default changes as human review notes instead of queue work.

Seeded by Claude Code from the roadmap + open issues; thereafter maintained by the architecture-review pass.