Redesign Tiers administration workflow

[deltawi]

Summary

• redesign the Tiers catalog and detail workspace with compact Live/Draft status, pagination, filtering, and clearer version navigation
• add complete create-tier, model-policy, pricing, capacity-pool, activation-preview, archive, clone, and restore-as-draft workflows
• introduce guarded row-level Tier configuration APIs with revision checks, transactional cloning/bootstrap, provenance, and idempotency
• remove the superseded bulk-replacement and publish mutation routes and their dead client code
• integrate the Tiers workspace with the database-backed whitelabel theme merged on main
• update admin/API documentation and add backend, migration, repository, and UI helper coverage

Why

The previous workflow made active and archived versions effectively dead ends: administrators could not edit them, and creating, activating, archiving, and recovering versions was difficult to understand. Growing policy, pricing, pool, and Tier collections also needed bounded navigation.

User impact

Administrators can now:

• distinguish Live and Draft state directly in the Tier catalog
• create a Tier and immediately configure its initial draft
• navigate explicitly between drafts, the live version, and paginated archive history
• restore an archived version by cloning it into a new editable draft
• manage model access, request limits, pricing, and capacity pools through paginated editors
• review activation consequences before making a draft live
• receive revision-conflict feedback when another administrator changes the same draft
• retain configured brand colors across Tiers actions, focus states, pagination, and version navigation

Data and API changes

• add Tier configuration revisions and creator/source provenance
• add idempotent Tier bootstrap request tracking
• add transactional row-level model-policy and capacity-pool mutations
• add paginated Tier, version, policy, and capacity-pool reads
• preserve immutable active/archived versions and archive the prior active version during activation

Verification

• rebased onto latest main including UI whitelabeling
• backend focused suite: 191 passed, 2 skipped
• UI unit suite: 128 passed
• Ruff checks: passed
• TypeScript/Vite production build: passed
• git diff --check: passed

Known review follow-ups

This is intentionally a draft while the remaining review items are addressed:

• bind retained query data to the selected version/filter before enabling bulk mutations
• replace the unbounded callable-target selector with server-side autocomplete
• paginate current drafts independently so the live version cannot be hidden by the 100-row cap
• lazy-load the expanded Tier route to recover the initial bundle increase
• replace native destructive confirmations with the shared confirmation dialog

Cross-replica policy propagation normally occurs immediately through Redis; the accepted degraded case can remain stale until the periodic refresh (about five minutes by default).