micro--go-micro
4bd181fc21
The framework's depth is strong but the on-ramp is the adoption gap, and the architect queue had filled entirely with internal hardening. Steer the architect to weight the developer on-ramp/DX (first-agent tutorial, discoverable examples, docs wayfinding, install friction, debugging) at least as highly as internal work — a developer succeeding on their first agent matters more than another conformance/observability increment. Adoption issues filed: #3561-#3565. Also add loop-release.yml: a daily patch release that tags v6.MINOR.PATCH+1 when master has new commits (pushed with the PAT so goreleaser fires), so the installable framework tracks the loop's daily improvements instead of lapsing. Minor/major bumps stay with the human. Co-authored-by: Claude <noreply@anthropic.com>