项目文件夹

文件
Codex 80f37cb61c
Harness (E2E) / Harnesses (mock LLM) (push) Has been cancelled
Harness (E2E) / Provider harnesses (live LLM conformance) (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
Run Tests / Unit Tests (push) Has been cancelled
Run Tests / Etcd Integration Tests (push) Has been cancelled
docs: refresh planner queue for 4422
2026-07-09 01:38:02 +00:00

2.1 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. Reconcile roadmap status with shipped agent resume and observability (#4423) — The lived code and recent PRs have moved durable agent checkpoint/resume and RunInfo/OpenTelemetry inspection forward, but the roadmap still reads as if those are wholly future work. Tighten the public status story so developer-adoption wayfinding reflects what actually shipped without turning this into a brand rewrite.
  2. Broaden provider streaming conformance (#4386) — The blog says Anthropic streaming shipped, but the roadmap still calls for provider-backed streaming across chat and A2A. Add a focused, provider-gated conformance slice so streaming stays end-to-end rather than becoming a one-provider success story.

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