Migrate Grok Bot fleets from the Cursor workaround

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

Audience: operators who previously ran the agent-owned use operation so Grok Bot could see AIWG artifacts. Related: #196, #210, `docs/architecture/adr-grokbot-provider-target.md`

What changes

Fleet	Provider flag	Notes
Grok Bot (multi-agent desktop assistant)	`the provider option grokbot`	First-class id; no bare `grok` alias
Cursor IDE	`the provider option cursor`	Unchanged — keep Cursor fleets on `cursor`

The Cursor workaround deployed into `.cursor/` paths Grok Bot does not auto-load and surfaced Cursor reload wording. `grokbot` writes a discover-first `AGENTS.md` bridge (+ shared `WORKSPACE.md` / `.aiwg/AIWG.md`) and never targets `.cursor/**`.

Migration steps (Grok fleets)

1. Confirm AIWG ≥ the release that includes the `grokbot` provider (experimental via #211; stable via #210). 2. From each project:

Use AIWG to complete this documented outcome: 1. Confirm AIWG ≥ the release that includes the grokbot provider (experimental via #211; stable via #210). 2. From each project
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

3. For user-scope / global skill copies, set an absolute skill root first (AIWG does not invent `~/.grokbot`):

Use AIWG to complete this documented outcome: 3. For user-scope / global skill copies, set an absolute skill root first (AIWG does not invent ~/.grokbot)
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

4. Start a new Grok Bot agent chat (or re-read skills). Do not expect Cursor “reload window” wording. 5. Optionally remove obsolete `.cursor/` AIWG copies only if that tree was created solely for the Grok workaround and is not used by Cursor IDE on the same machine.

Cursor IDE fleets

No migration. Continue:

Use AIWG to complete this documented outcome: No migration. Continue
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Verify

Use AIWG to complete this documented outcome: Verify
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Provider status is `stable` as of #210 (Linux PUW + security + migration + maintainer Linux-only waiver). Optional natives remain #209.