Migrate Grok Build from Claude Workaround

Move Grok Build projects from a temporary --provider claude deployment to grok-build

Move Grok Build projects from temporary Claude deployment

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.

If Grok Build was previously configured through `the provider option claude`, keep `WORKSPACE.md` as the source of shared guidance. Preview the existing-project adoption transaction if needed with the agent-owned regenerate operation, then apply it only after reviewing its file plan. Existing operator text in `AGENTS.md` and `CLAUDE.md` belongs to the operator.

Deploy the agent-owned use operation, run the agent-owned regenerate operation, and confirm the agent-owned build-verify operation plus `grok inspect` in a trusted project. The native skill directory is `.grok/skills`; `.agents/skills` and Claude files are compatibility surfaces, not a substitute for this check. If Claude Code is also used, retain its generated hook and project assets. Remove only AIWG-owned obsolete Claude artifacts through a reviewed dry-run uninstall. This migration does not move Grok Bot (`grokbot`) state or Grok web Build content.