codex/increment-3952
3 次代码提交
| 作者 | SHA1 | 备注 | 提交日期 | |
|---|---|---|---|---|
 Asim Aslam
|
76961d503a |
feat(loop): go-micro runs on micro loop (dogfood its own tool) (#3657)
* feat(loop): go-micro now runs on `micro loop` (dogfood its own tool)
Replace go-micro's five hand-written loop workflows with ones generated by
`micro loop init --roles all`, making "go-micro builds itself with micro loop"
literally true rather than aspirational.
- Generate loop-planner/builder/triage/coherence/release.yml via the CLI with
go-micro's cadence and wiring (planner :59, builder :29, coherence 07:00,
release 23:00; CI gate "Harness (E2E)"; token CODEX_TRIGGER_TOKEN; base master;
tag prefix v). The old loop-architect.yml and loop-devrel.yml become
loop-planner.yml and loop-coherence.yml.
- Move the queue to .github/loop/PRIORITIES.md and add .github/loop/NORTH_STAR.md
(a concise steer pointing to internal/docs/THESIS.md), adopting the loop's
convention.
- Preserve go-micro's rich instructions as editable policy in
.github/loop/prompts/{planner,builder,triage,coherence}.md — the architect
founder-lens + adoption steer, the increment builder, harness-failure triage,
and the DevRel changelog/blog pass — faithfully ported from the old inline
prompts. Behavior is preserved; only the mechanism is now generated.
- CLI refinement the migration surfaced: prompts (and NORTH_STAR/PRIORITIES) are
now write-once — `micro loop init --force` refreshes workflow MECHANICS but
never clobbers customized POLICY. Added renderKeep + a test.
- Update internal/docs/CONTINUOUS_IMPROVEMENT.md (renamed workflows, moved queue,
the prompt-file model, and a note that these files are generated by micro loop).
Verified: build, go test ./cmd/micro/loop/..., golangci-lint (0 issues), gofmt;
`micro loop verify` passes; all generated workflows are valid YAML; re-running
init --force is idempotent and preserves policy.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
* loop: strip prompt editorial comments before posting to the agent
Verification of the migration surfaced that a dispatch workflow posted the
prompt file's leading <!-- editorial --> header to the agent, and __ISSUE__
inside it got substituted too (e.g. "Keep 4242 literal"). Harmless (invisible
in rendered markdown) but unclean and mildly confusing. The dispatch and triage
body construction now strips <!-- --> blocks with `sed '/<!--/,/-->/d'` before
substituting runtime tokens. Regenerated go-micro's workflows; added a test.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
---------
Co-authored-by: Claude <noreply@anthropic.com>
|
||
|
Asim Aslam
|
8e3ba68d58 |
loop-release: fix 403 on tag push (checkout token clobbered the PAT) (#3638)
goreleaser / goreleaser (push) Has been cancelled
* docs: complete Ollama provider surface (capability matrix, README, example fixes) Follow-up cleanup after merging the Ollama provider (#3636): - Add the `ollama` row to the AI provider capability matrix in the provider guide, and blank-import `ai/ollama` in provider_capabilities_test.go so the matrix stays enforced against the registry (the provider registers a stream but wasn't imported in that test, so its row went unchecked). - README: bump "7 LLM providers" → 8 and list Ollama (local + cloud); add its default model (`llama3.2`) to the model table. - Fix a fictional model name shipped in the example and package doc: `gemma4:31b-cloud` → `gpt-oss:120b`. gemma4 doesn't exist, and the `-cloud` suffix is for cloud models proxied through a local Ollama, not the direct ollama.com/v1 endpoint the example uses. - Record the provider and the new agent.BaseURL/micro.AgentBaseURL option in the CHANGELOG [Unreleased] section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL * loop-release: don't let checkout's persisted GITHUB_TOKEN clobber the PAT push The daily release job computed the next tag correctly but the tag push 403'd: "Permission to micro/go-micro.git denied to github-actions[bot]" (run 28554612450). Cause: actions/checkout persists the default GITHUB_TOKEN as an http.extraheader Authorization credential for github.com, which git sends on ALL requests to that host — including our manual `git push https://x-access-token:${PAT}@github.com/...`. The persisted header overrides the URL-embedded PAT, so the push authenticates as github-actions[bot], which can't push tags (the job only grants contents: read). Set persist-credentials: false so no extraheader is written and the PAT in the push URL is the only credential used. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
Asim Aslam
|
4bd181fc21 |
loop: point the architect at adoption + add a daily release action (#3566)
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> |