Skip to content

chore(acp): bump dimcode and grok registry pins to probed versions - #765

Merged
kaizhou-lab merged 1 commit into
mainfrom
chore/acp-lock-sync-20260804
Aug 3, 2026
Merged

chore(acp): bump dimcode and grok registry pins to probed versions#765
kaizhou-lab merged 1 commit into
mainfrom
chore/acp-lock-sync-20260804

Conversation

@kaizhou-lab

Copy link
Copy Markdown
Contributor

Summary

Scheduled ACP Registry version sync. Two npx pins drifted since #750, each backed by a fresh serial ACP probe of the exact pinned version. Lock-only change — two lines; no metadata, migration, or entrypoint edits, and no lock-derived test assertion embeds either version.

backend package old → new initialize session/new
dimcode dimcode 0.3.1 → 0.3.2 ok (agentInfo dimcode "DimCode" 0.3.2) auth required (-32000, "Provider credentials are required")
grok @xai-official/grok 0.2.118 → 0.2.119 ok (protocolVersion 1) auth required (-32000, "no auth method id provided")

Both meet the release-lock criterion: initialize succeeds and session/new returns a clearly classified authentication requirement. Probes ran serially with no inherited HOME or credentials.

The other 9 Registry-pinned packages (autohand, codebuddy, deepagents, dirac, glm-acp-agent, kilo, nova, pi, sigit) match the snapshot exactly — no drift. Package names and entrypoint args are unchanged for all 11. Drifted but not upgraded: none. The mimo-code and omp entries are non-Registry builtins (no registry_json_id) and are correctly excluded from drift reconciliation.

Registry snapshot

  • Audit pinned to release tag v2026.08.03-e5290cd of agentclientprotocol/registry (newest release at audit time), fetched via the versioned CDN path for reproducibility.
  • No newly listed and no delisted agents versus the previous baseline (38 ids).

Validation

Logging

No logging changes: lock-only version bumps; existing startup/session error paths already identify a failing agent by backend.

@kaizhou-lab
kaizhou-lab merged commit fc1352c into main Aug 3, 2026
6 checks passed
@kaizhou-lab
kaizhou-lab deleted the chore/acp-lock-sync-20260804 branch August 3, 2026 20:39
kaizhou-lab added a commit that referenced this pull request Aug 5, 2026
## Summary

Scheduled ACP Registry version sync. Two npx pins drifted since #765,
each backed by a fresh serial ACP probe of the exact pinned version.
Lock-only change — two lines; no metadata, migration, or entrypoint
edits, and no lock-derived test assertion embeds either version.

| backend | package | old → new | initialize | session/new |
|---|---|---|---|---|
| grok | `@xai-official/grok` | 0.2.119 → **0.2.120** | ok
(protocolVersion 1) | auth required (`-32000`, "no auth method id
provided") |
| kilo | `@kilocode/cli` | 7.4.17 → **7.4.19** | ok (agentInfo Kilo
7.4.19) | success |

Both 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.

The other 9 Registry-pinned packages (autohand, codebuddy, deepagents,
dimcode, dirac, glm-acp-agent, nova, pi, sigit) match the snapshot
exactly — no drift. Package names and entrypoint args are unchanged for
all 11. Drifted but not upgraded: none. The `mimo-code` and `omp`
entries are non-Registry builtins (no `registry_json_id`) and are
correctly excluded from drift reconciliation.

## Registry snapshot

- Audit pinned to release tag
[`v2026.08.04-c23c1ec`](https://cdn.agentclientprotocol.com/registry/v1/v2026.08.04-c23c1ec/registry.json)
of `agentclientprotocol/registry` (newest release at audit time),
fetched via the versioned CDN path for reproducibility.
- No newly listed and no delisted agents versus the previous baseline
(38 ids).

## Validation

- `cargo test -p aionui-runtime -p aionui-ai-agent` — pass (902 lib +
integration tests)
- Full `just push` gate (migration check, lint, fmt, `cargo nextest run
--workspace`) — pass
- Gate run with the host-injected `AIONUI_LOG_DIR` unset (pre-existing
environment sensitivity, see #695)
- Gate started only after host load fell below the pre-flight threshold;
the targeted test run had pushed the 12-core host to load 69, the
condition that produced spurious subprocess-spawn timeouts in #750's
history.

## Logging

No logging changes: lock-only version bumps; existing startup/session
error paths already identify a failing agent by backend.

Co-authored-by: zk <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant