chore(acp): bump codebuddy and dimcode registry pins to probed versions - #943
Merged
Conversation
11 tasks
kaizhou-lab
added a commit
that referenced
this pull request
Aug 31, 2026
…ry pins to probed versions (#957) ## Summary Scheduled ACP Registry version sync, covering three days of drift (the 2026-08-30 and 08-31 runs did not execute; the state file's last checked tag was `v2026.08.28-e9b1b2d`). Six npx pins drifted since #943, each backed by a fresh serial ACP probe of the exact pinned version. The diff is the lock file plus the one lock-derived test assertion that embeds codebuddy's version. | backend | package | old → new | initialize | session/new | |---|---|---|---|---| | codebuddy | `@tencent-ai/codebuddy-code` | 2.141.0 → **2.142.0** | ok (protocolVersion 1) | auth required (`-32000`, `data.category: auth`) | | dimcode | `dimcode` | 0.3.22 → **0.3.25** | ok (agentInfo version 0.3.25) | auth required (`-32000`, "Provider credentials are required") | | dirac | `dirac-cli` | 0.5.1 → **0.5.2** | ok (agentInfo dirac 0.5.2) | **succeeded** unauthenticated | | glm-acp-agent | `glm-acp-agent` | 1.6.1 → **1.7.0** | ok (protocolVersion 1) | **succeeded** unauthenticated | | grok | `@xai-official/grok` | 1.0.12 → **1.0.13** | ok (protocolVersion 1) | auth required (`-32000`, "no auth method id provided") | | kilo | `@kilocode/cli` | 7.5.5 → **7.5.6** | ok (agentInfo Kilo 7.5.6) | **succeeded** unauthenticated | All six meet the release-lock criterion: `initialize` succeeds, and `session/new` either succeeds or returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials, and every entrypoint is unchanged from the previous snapshot. glm-acp-agent is the one bump crossing a minor version (1.6.x → 1.7.0), so its entrypoint was exercised rather than assumed: the Registry distribution still declares a bare `glm-acp-agent` invocation with no arguments, and that exact call completed `initialize` and opened a session advertising thought_level, mode, and model options. It also continues to self-report `agentInfo.version` as `1.0.0` while the package is 1.7.0 — a standing vendor quirk, not an AionCore defect. dimcode likewise still reports `agentInfo.title` "DimAgent" against a public listing that says "DimCode". No session catalog is persisted (skill step 11 leaves those columns to the runtime), and no metadata changes ride along. **Derived assertion updated:** `registry_npx_lock.rs` pins codebuddy's exact version inside a `--package`-form argument list, so it moves with the lock — `2.141.0` → `2.142.0`. All six outgoing versions were grepped across `crates/**/*.rs` before staging; codebuddy's was the only real assertion. The other hits were verified false positives from substring and wildcard matching: `0.3.22` inside a `@anthropic-ai/claude-agent-sdk 0.3.220` comment, `0.5.1` inside `"block005-1111"` and a Discord snowflake timestamp, `1.6.1` inside npm `11.6.1` version-parser fixtures. `npx_cache_repair.rs` keeps its own version literals: those are cache-path hash fixtures, not lock assertions, and changing them would break their hash expectations. The other 5 Registry-pinned packages (autohand, deepagents, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none. `mimo-code` remains the one non-Registry builtin (no `registry_json_id`), excluded from drift reconciliation. ## Registry snapshot - Audit pinned to release tag [`v2026.08.31-f6fdb56`](https://cdn.agentclientprotocol.com/registry/v1/v2026.08.31-f6fdb56/registry.json) of `agentclientprotocol/registry`, fetched via the versioned CDN path for reproducibility. - 39 ids in the raw snapshot: no newly listed and no delisted agents versus the baseline. (`antigravity-acp` remains listed and deferred as binary-only since 2026-08-21; `fast-agent` and `minion-code` remain listed but uvx-only and therefore out of scope.) ## Validation - `just migration-check` — pass - `just lint-fix` (`cargo fix` + `clippy --fix --workspace -D warnings`) — clean - `just fmt` — clean - **Local `cargo nextest` intentionally skipped, by standing policy for lock-only bumps** (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to. ## Logging No logging changes: lock version bumps plus one test assertion; existing startup/session error paths already identify a failing agent by backend. Co-authored-by: zk <>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scheduled ACP Registry version sync. Two npx pins drifted since #941, each backed by a fresh serial ACP probe of the exact pinned version. The diff is the lock file plus the one lock-derived test assertion that embeds codebuddy's version.
@tencent-ai/codebuddy-code-32000,data.category: auth)dimcode-32000, "Provider credentials are required")Both meet the release-lock criterion:
initializesucceeds andsession/newreturns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials, and both entrypoints (--acpfor codebuddy,acpfor dimcode) are unchanged from the previous snapshot.Derived assertion updated:
registry_npx_lock.rspins codebuddy's exact version inside a--package-form argument list, so it moves with the lock —2.140.0→2.141.0. Both outgoing versions were grepped acrosscrates/**/*.rsbefore staging: codebuddy's was the only real assertion, and0.3.21's single hit was a false positive (a"003421"string literal inpairing.rs, matched because.is a regex wildcard).npx_cache_repair.rskeeps its own version literals: those are cache-path hash fixtures, not lock assertions, and changing them would break their hash expectations.The other 9 Registry-pinned packages (autohand, deepagents, dirac, glm-acp-agent, grok, kilo, nova, pi, sigit) match the snapshot exactly. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none.
mimo-coderemains the one non-Registry builtin (noregistry_json_id), excluded from drift reconciliation.dimcode continues to self-report
agentInfo.titleas "DimAgent" against a public listing that says "DimCode" — a standing observation since #814; no metadata change.Registry snapshot
v2026.08.28-e9b1b2dofagentclientprotocol/registry, fetched via the versioned CDN path for reproducibility.antigravity-acpremains listed and deferred as binary-only since 2026-08-21;fast-agentandminion-coderemain listed but uvx-only and therefore out of scope.)Validation
just migration-check— passjust lint-fix(cargo fix+clippy --fix --workspace -D warnings) — cleanjust fmt— cleancargo nextestintentionally skipped, by standing policy for lock-only bumps (established 2026-08-11). The Test check on this PR is the authority for this change: the merge decision depends on CI rather than the local run, and this host's load only manufactures timeout-shaped test failures, which nothing in the local steps above is subject to.Logging
No logging changes: lock version bumps plus one test assertion; existing startup/session error paths already identify a failing agent by backend.