[backtrack5r3 (tomflenner)]

Scope

Dedicated AI control-plane work, stacked on billing PR #3. The billing branch is unchanged; this PR contains only the AI command implementation, mocked regressions and documentation.

• Model catalogue CRUD and exact licence-version conversion-rule management/archive.
• Authored AI reserve/commit reports, inference history and open reservations; no inference execution or provider credentials.
• Stable value.transactionId, no numeric Idempotency-Key, exact decimal quantities and destructive confirmation.
• Fresh-read replacement updates preserve omitted settings/metadata/vendor costs and immutable identities.

Verification

Full root race/shuffled tests and go vet passed offline using the original pinned SDK and a private verification-only runtime override to cached v1.6.0. Real go.mod/go.sum are unchanged. Pinned runtime v1.3.1 verification remains unavailable locally.

Landing order

Merge billing #3 first, then retarget/rebase this dedicated AI PR onto main and rerun checks. Do not merge the AI commit into the billing PR. Fresh GET/PUT updates still have a race because the API has no CAS precondition.

All commits are signed off. No live/provider calls, runtime data writes, migrations or dependency installation were performed.

[backtrack5r3 (tomflenner)]

The AI-only PR is now stacked correctly on billing #3, and its CI branch filter was extended to test that stacked base. Build/tests pass; the AI command lint/format findings were fixed.

The remaining CI failure is inherited from billing's go.sum: go mod tidy removes the obsolete SDK pseudo-version v0.0.2-0.20261005202017-deeb018edc00 (two checksum lines), while go.mod already pins ...20261011094234-d1062715c9f4. Those stale lines are present in origin/feat/billing, not introduced by this AI PR. Dependency pins are unchanged; keep the billing metadata cleanup separate, then rerun this stack's checks before landing.