› is the new  notion of 'tier' a proper notion or something concocted for this last request?


• It was inferred—and largely concocted—for the request, not an established notion in this repository.

  I found no existing pro_v2 value, tier field, tier-specific model, checkpoint, queue contract, or historical implementation. I invented:

  - The accepted tier locations.
  - VoiceCloning.tier.
  - training_model_tier.
  - Tier-aware completion rules.
  - pro_v2/ artifact namespaces.

  The tests only validate that invented contract. They do not prove it matches the real producer.

  Before keeping this change, we need the actual pro_v2 request payload and intended semantics. If it is merely an account plan, most of this implementation—especially artifact
  isolation—is likely inappropriate. I should have flagged that uncertainty before implementing it.