项目文件夹

文件
Codex 7bb4e13b96
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(priorities): refresh architect queue after failure hardening
2026-06-30 16:50:03 +00:00

2.3 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. Emit OpenTelemetry spans for agent RunInfo timelines (#3455) — the Now-phase getting-started and cross-provider harness contracts are already covered in CI, and #3461/#3464 closed the immediate failure-semantics queue item. The highest-value remaining seam is production observability for agents: translating RunInfo / run timeline events into spans closes the operability gap across agent runs, tool calls, model calls, retries, failures, and checkpoint/resume events without changing public APIs.

  2. Complete end-to-end chat and A2A streaming coverage (#3456) — provider streaming conformance and A2A fallback work recently shipped, but the mission is one runtime where agents can operate as services, which means streaming must be dependable through the whole path: provider tokens → chat / Agent.Chat → A2A. This remains behind observability because it is a Next-phase depth item, but it is the next user-visible seam in the developer inner loop and interop story.

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