Grok Build qualification receipts

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.

`linux.json` is a partial Linux PUW receipt for the released 1.0.38 binary. The official `@xai-official/[email protected]` npm archive matched its published SHA-512 integrity before the binary was extracted into an isolated temporary directory. An isolated npm install of `@xai-official/[email protected]` used the reviewed postinstall explicitly because the local npm script policy deferred it. The installed binary matched the independently extracted binary SHA-256. The same isolated npm prefix was updated to 1.0.40 and preserved operator state. The receipt records live `grok inspect the json option` and the agent-owned build-verify operation outcomes, plus project and user-scope deploy/removal, repeat, framework refresh, path safety, secret-canary, and compatibility observations. No authentication was established, so `authenticationMode` is `unverified`.

The public source commit and its internal `SOURCE_REV` are separate identifiers in the receipt. Neither is a verified mapping from this binary to a monorepo commit. The Linux recovery check records a controlled refresh failure and exact operator backup restoration; it does not claim automatic transactional rollback. Credentialed native surfaces and macOS, Windows PowerShell, and WSL qualification remain pending. Do not use this receipt to promote the provider to stable.

The same released 1.0.38 binary advertised only `grok.com` during ACP initialization. A sanitized ACP observation records the method ID; it does not establish a credentialed ACP session. AIWG therefore keeps ACP authentication fail-closed.