Provider-neutral build readiness verification

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.

the agent-owned build-verify operation checks that AIWG is deployed correctly before the selected provider performs a build or CI task. The command reuses the shared provider definitions and deployment verifier: artifact paths, installed bundle records, capability indexes, canonical context, provider wiring and available native inspection all remain in that common implementation.

Use AIWG to complete this documented outcome: the agent-owned build-verify operation the provider option <id checks that AIWG is deployed correctly before the selected provider performs a build or CI task. The command reuses the shared provider definitions and deployment verifier: artifact paths, installed bundle r
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Use the same commands with `claude`, `grok-build`, `grokbot`, or another registered provider. Without the provider option, normal active-provider resolution applies; ambiguous or invalid selections fail. In CI, select the provider explicitly.

The result is JSON with schema `aiwg.build.verify.v1`, `provider`, `status`, `verification`, restart guidance and findings. Missing project deployment or any blocking finding yields a nonzero exit. Advisory findings remain visible.

Verification level	Meaning
`deployment`	Shared file/configuration, registry and discovery checks; native runtime loading is not asserted.
`native-inspection`	A documented provider inspector also confirmed the deployed artifacts.

Where a native inspector is implemented, its absence or failure blocks this CI gate. Currently Grok Build uses `grok inspect`, checking this project's `AGENTS.md` and every deployed skill. Other providers retain deployment-level checks until a documented native inspector is integrated into the shared verifier. Ordinary the agent-owned use operation/status inspection retains its advisory behavior.

After verification, let the provider perform the requested task through its native prompt/configuration and execution tools. This command does not launch inference, invoke a compiler, run tests, implement scheduling or install plugins. A successful check does not prove that a model followed instructions. The CI system still owns job triggers, credentials, timeouts and deterministic tests.

See Grok Build CI for a concrete provider example and non-interactive installation for runner setup. Use bot-handoff for shared reviewable prompt proposals.