feat(agents): bump pi-acp release pin to 0.0.32

[ChristianLuciani]

Summary

• Bump the ACP Registry npx release pin for Pi from pi-acp@0.0.31 → pi-acp@0.0.32 in crates/aionui-runtime/resources/acp-registry-npx-lock.json.
• Runtime still resolves DB args ["-y","pi-acp"] to the locked version via pin_registry_npx_args (migration 025 left args unversioned on purpose).
• Migration 029: advertise session_capabilities.delete: {} on the Pi builtin row so seeded agent_capabilities match the live ACP handshake from pi-acp#76 (released in v0.0.32).

This unblocks AionUi users of the builtin Pi agent from getting session/delete (and the rest of the 0.0.32 fixes) without manual agent setup.

Why not edit migration 023?

Historical seed stays intact. The pin of record is the release lock; DB command/args remain the stable package identity.

Behavior notes from pi-acp 0.0.32 (for QA)

Beyond session/delete:

• Startup info can include project-level packages in the extensions list
• Bash tools render as terminals in ACP clients
• Extension notifications can carry severity via _meta

The long “available skills” list on first turn is intentional pi-acp startup info (disable with quietStartup: true in pi settings), not an AionUi bug.

Test plan

• cargo test -p aionui-runtime registry_npx_lock
• cargo test -p aionui-db --test pi_acp_agent_migration
• cargo test -p aionui-ai-agent --lib resolve_agent_command_spec_flattens_bare_npx_command
• cargo test -p aionui-ai-agent --lib manual_check_persists_command_not_found
• cargo fmt --all -- --check
• cargo clippy -p aionui-runtime -p aionui-db -- -D warnings
• CI green on this draft
• Optional: live smoke against npx -y pi-acp@0.0.32 + Pi CLI handshake

Related

• Prior: AionCore #618 (Pi builtin @ 0.0.31)
• Upstream feature: svkozak/pi-acp#76 / v0.0.32

Thanks for maintaining AionCore — happy to adjust the migration or PR shape if you prefer a lock-only change.