chore(acp): bump dimcode, dirac, grok and sigit registry pins to probed versions

[kaizhou-lab]

Registry snapshot

• Release tag: v2026.10.13-894756e
• CDN JSON: https://cdn.agentclientprotocol.com/registry/v1/v2026.10.13-894756e/registry.json
• Public page: https://agentclientprotocol.com/get-started/registry.md
• 41 listed agent ids; no new and no delisted entries against the previous audited snapshot (v2026.10.12-d570c6d).

Version drift

backend	package	old	new
dimcode	dimcode	0.5.16	0.5.17
dirac	dirac-cli	0.5.19	0.5.20
grok	@xai-official/grok	1.0.52	1.0.54
sigit	@smbcloud/sigit	1.6.7	1.6.8

The other Registry-pinned entries (autohand, codebuddy, deepagents, glm-acp-agent, kilo, minimax-code, nova, pi) match the snapshot. mimo-code is a non-Registry builtin and is excluded from drift reconciliation.

Probe evidence

Each package was probed serially at the exact new version with the Registry's declared argv, no inherited HOME and no credentials. All four completed ACP initialize at protocolVersion 1.

backend	probed argv	session/new	classification
dimcode	npx -y dimcode@0.5.17 acp	-32000 "Authentication required: Provider credentials are required"	auth required
dirac	npx -y dirac-cli@0.5.20 --acp	session created; modes plan/act	success
grok	npx -y @xai-official/grok@1.0.54 agent stdio	-32000 "Authentication required", data "no auth method id provided"	auth required
sigit	npx -y @smbcloud/sigit@1.6.8	session created; modes permission-mode-manual/-auto/-plan	success

Drifted but not upgraded: none.

sigit carries skip_version_probe: true, which exempts only the runtime --version subprocess; it was still ACP-probed here. Its stderr still announces the @smbcloud/sigit → @getsigit/sigit scope rename, but the Registry snapshot still declares @smbcloud/sigit, so the lock keeps the old scope.

Structural diff

The previous snapshot (v2026.10.12-d570c6d) was fetched from its versioned CDN path and diffed per agent. For every npx entry whose package moved, args and env are byte-identical. Beyond the four pins above, the changes are version churn in agents AionCore does not pin: factory-droid, github-copilot-cli, and binary artifacts for junie and kimchi. No distribution type was added or removed for any pinned backend.

Scope

Lock-only. A fixed-string scan (grep -rnF) for each outgoing version across crates/**/*.rs returned no match, so no lock-derived test assertion needed updating. The version literals in npx_cache_repair.rs are cache-path hash fixtures and are deliberately untouched.

Validation

• just migration-check: passed.
• just lint-fix (cargo fix + clippy --fix --workspace -D warnings): clean, no fixes produced.
• just fmt: clean.
• just _auto-commit-fixes: nothing to commit.
• Local cargo nextest run --workspace skipped by standing policy for a lock-only bump; the Test check on this PR is the authority.

Logging

No logging change. This is a resource-manifest version bump on an existing, already-instrumented spawn path.