Reset Cursor ACP in bb

How Cursor ACP works in bb (read this first)

ACP = Agent Client Protocol, an open standard from Zed. bb is the client, Cursor CLI is the server.
bb's provider-acp plugin spawns one cursor-agent acp subprocess per thread, on demand, owned by a bb-provider-bridge-worker process. They talk JSON-RPC over stdin/stdout.
There is no global Cursor ACP server. Nothing to keep alive with launchd or a watchdog. Never build one.
Config (rules, skills, .cursor/mcp.json) is read when the subprocess starts. Reload = spawn a new subprocess.
bb thread stop <id> releases the runtime and kills the subprocess. The thread history is kept. The next message spawns a fresh cursor-agent acp.

Resolve scripts/reset-cursor-acp.sh relative to this SKILL.md. Run: