AIWG 2026.9.19 — Decision backends and provider handoffs

AIWG 2026.9.19 adds a structured decision runtime and two shared ways to prepare work for AI providers. It also makes stable npm releases keep `latest` and `next` on the same version.

What changed

• Decision backends: The opt-in `decision-engine` addon now accepts structured entries and interchangeable Jev or LLM-subagent evaluators through one contract. Receipt validation, retry handling, and rollback gates make evaluations easier to replay and inspect. Live Jev testing remains a separate, explicit smoke check.
• Bot handoffs: `aiwg bot-handoff --provider <id> --input proposal.json` drafts a routine, teammate, connector, or memory proposal for review. It reads the supplied proposal and prints Markdown; creating a provider object remains an operator action.
• Grok Bot adapters: Optional native adapter scaffolding now covers routines, teammates, connector install profiles, machine health, and memory references. The scaffolding guide describes the contract gates and current limits.
• Build readiness: `aiwg build-verify --provider <id>` checks AIWG deployment and discovery before a provider runs a build or CI task. Grok Build also checks its native `grok inspect` view. The CI system still runs deterministic tests and controls credentials.
• Release channels: The release flow now checks that `latest` and `next` resolve to the same stable version for `aiwg`, `@aiwg/cli`, and `@aiwg/cockpit` before completion.

Try it

Update with `npm install -g [email protected]`. For provider handoff examples, see the bot handoff guide. For CI setup, see build verification and Grok Build CI. The versioning guide describes the stable dist-tag policy.

The full change history is in the changelog.