ACP Registry listing readiness: 8/10 — submission deferred

[Blankeos]

Status: registry submission intentionally deferred

Requested scope: fix ACP blockers, add discoverable login, and prepare compatible release artifacts. Do not submit a PR to agentclientprotocol/registry until explicitly authorized. Maintainer will tag/publish the release personally.

Provisional readiness: 8/10

Code and release packaging are prepared; listing is not submission-ready yet because the new version has not been published or tested against real client/provider login. This is an evidence-based readiness estimate, not registry acceptance or protocol certification.

Completed in #44 follow-up fixes

• Provider output limits/refusals/content filtering stop once, retain partial output and usage, and do not execute incomplete tool calls or issue extra model requests.
• ACP /btw participates in active-prompt/cancellation tracking.
• Cancellation persists partial assistant text, marks interrupted status, and cancels pending permission requests.
• Close/reopen waits for old turn finalization to prevent stale prompt ownership corrupting the reopened session.
• Delayed client-terminal creation is retained for eventual kill/release cleanup, including when kill is not acknowledged.
• Approval previews avoid reading protected external/sensitive files, including symlink escapes. Mixed protected patches omit the entire diff preview.
• Authoritative persisted totals include cache-read/cache-write tokens.
• Unknown load/resume IDs are rejected before model discovery.
• crabcode acp --login: login-only terminal flow sharing credential storage and OpenAI/xAI OAuth; hidden API keys for other/custom providers; local provider setup; saved credentials may be replaced; piped stdin rejected.
• Modern terminal-auth discovery appends --login; legacy registry _meta["terminal-auth"] discovery replaces args with acp --login. No auth flow advertised without the corresponding client opt-in.
• cargo-dist configured for .tar.gz on Unix and .zip on Windows. npm installer supports gzip plus 404-only legacy xz fallback, with diagnostics on stderr.
• Provider-free local check: python3 scripts/verify-acp-registry.py /path/to/crabcode.

Before submission

• Maintainer tags and publishes a release containing these fixes. Do not submit with older v0.0.13 artifacts.
• Verify GitHub release CI succeeds for all declared targets and published checksums match actual artifacts.
• Extract each supported artifact and record the executable path; cargo-dist tarballs may contain a target-named top-level directory.
• Run the official registry verifier against published binary distributions, in a clean home/state directory. Local helper verifies discovery only, not OAuth validity or full registry CI.
• Smoke-test a real OpenAI/xAI OAuth flow and an API-key login through an ACP client's terminal authentication; confirm reconnect and stale-credential replacement.
• Smoke-test Codync using its Custom command (/absolute/path/to/crabcode acp): prompt/tool/approval/cancel/load. Model selection remains separate from credential setup; choose a connected provider's model.
• Independently review readiness and resolve any remaining findings.
• Prepare crabcode/agent.json with a pinned stable version, license URL, platform artifact URLs/checksums, exact commands and args: ["acp"].
• Prepare crabcode/icon.svg: monochrome 16×16 SVG using currentColor.
• Validate manifest/icon and await explicit maintainer authorization before opening the registry PR.

Verification and known limitations

Validation results will be updated after final tests and GitHub checks. Full-suite runs reproduced two existing UI assertion failures on untouched #44 (Codex-style diff path fixture and input cursor color); do not call the entire suite green unless these are resolved independently. No paid provider calls or real OAuth login have been performed. The terminal-only flow accepts custom provider IDs; authentication presence does not certify provider key validity. Registry/current ACP terminal-auth conventions differ, so both are tested separately.

References

• https://agentclientprotocol.com/get-started/registry
• https://github.com/agentclientprotocol/registry/blob/main/CONTRIBUTING.md
• https://github.com/agentclientprotocol/registry/blob/main/AUTHENTICATION.md
• https://github.com/agentclientprotocol/registry/blob/main/FORMAT.md
• https://github.com/agentclientprotocol/registry/blob/main/.github/workflows/client.py
• https://agentclientprotocol.com/rfds/auth-methods
• feat(acp): complete capability matrix #44

[Blankeos]

Validation update: official registry client.py run_auth_check succeeds against the locally built executable with isolated HOME/state. Current-main integration: cargo check; 63 ACP unit tests; 42 request-loop tests; 7 stdio integration tests; fmt and SDK boundary checks passed. npm installer: 4 tests passed. Local Ollama login-only flow passed in isolated PTY with no provider requests. dist plan emits four Unix .tar.gz archives and one Windows .zip archive. Published artifacts, real OAuth/API-key validity and Codync end-to-end remain unchecked; maintainer will tag/publish. No registry PR submitted.

[Blankeos]

PR #44 is now merged through GitHub, merge commit 4ea57e3. Follow-up fixes are included. Registry readiness remains 8/10 pending maintainer publication and published-artifact/real-client checks. No tag or release was created and no registry PR was submitted.