Skip to content

Refresh planner priorities for 4726 #4727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
asim merged 1 commit into from
Jul 11, 2026
+2 −3
Merged

Refresh planner priorities for 4726 #4727

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions .github/loop/PRIORITIES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,8 @@ changes, architectural rewrites. Those go to the human.

## Work queue (ranked)

1. **Align website first-agent on-ramp with debug recovery CLI** ([#4722](https://github.com/micro/go-micro/issues/4722)) — #4720 closed the first-agent debugging breadcrumb work in the CLI, but the website docs index/getting-started path still risks telling a different story than the README and v6.6.0 blog. Keep the adoption lane first by gating the website on-ramp order around `micro agent demo`, `micro agent quickcheck`/`debug`, examples, no-secret first agent, debugging, and 0→hero without broad copy or CLI redesign.
2. **Gate mock provider plan-delegate resume scenarios** ([#4713](https://github.com/micro/go-micro/issues/4713)) — #4709 closed the live AtlasCloud nested tool-call rejection gap, but the underlying agent-loop risk remains valuable enough to keep near the top: completed plan steps, notifications, unsafe fallback parsing, and resume semantics must stay deterministic without provider keys. Capture the recent provider failures in mock-based regression coverage before broadening into live-provider conformance.
3. **Migrate store/postgres from pgx/v4 to pgx/v5** ([#4556](https://github.com/micro/go-micro/issues/4556)) — Security upkeep matters to the service-framework half of the harness, and #4556 is the remaining open enhancement/security item. Keep it below the adoption and agent-loop contracts because it is narrower than the current developer-adoption goal, but do not let reachable dependency risk drift indefinitely.
1. **Gate mock provider plan-delegate resume scenarios** ([#4713](https://github.com/micro/go-micro/issues/4713)) — #4709 closed the live AtlasCloud nested tool-call rejection gap and #4725 closed the website first-agent wayfinding gap, so the highest-value remaining Now work is deterministic no-secret agent-loop coverage. Completed plan steps, notifications, unsafe fallback parsing, and resume semantics must stay stable without provider keys before broadening into live-provider conformance.
2. **Migrate store/postgres from pgx/v4 to pgx/v5** ([#4556](https://github.com/micro/go-micro/issues/4556)) — Security upkeep matters to the service-framework half of the harness, and #4556 is the remaining open enhancement/security item. Keep it below the agent-loop contract because it is narrower than the current developer-adoption goal, but do not let reachable dependency risk drift indefinitely.

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