项目文件夹

文件
Codex cca908abf6
Run Tests / Unit Tests (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
govulncheck / govulncheck (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 4633
2026-07-11 00:41:44 +00:00

2.4 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. Verify first-agent docs wayfinding against CLI commands (#4634) — PR #4632 merged the 0→hero inspect transcript check and #4627 is closed, so the top developer-adoption risk moves from proving transcript output to preventing the on-ramp map from drifting. README, the website docs index, the 0→hero guide, and the v6.3.15 blog all tell one story: install → scaffold/run → provider-free first agent → chat/inspect → workflows. Make that wayfinding CI-verifiable against real CLI commands and maintained examples so a new developer can still walk from 0→1 to 0→hero without provider keys.
  2. Harden atlascloud plan-delegate plan persistence (#4630) — Keep this Next/Now hardening item close behind adoption work: recent AtlasCloud repair fixes reduced provider brittleness, but plan/delegate durability still has a provider-specific persistence seam. Scope it to the existing plan/delegate harness and CI-verifiable behavior so services → agents → workflows remains reliable without broad public-API or architecture changes.

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