- new context minimax-m31-flash/v1 (model pin; no thinking-budget init, Flash
ignores it); four composites switch from minimax-m3-max/v1 (kept for rollback)
- models + registry for minimax-m31-flash-{max,medium}; removes the dangling
model-registry/minimax.yaml (endpoint "minimax" never existed)
- tiers, harness-roles, minimax-* task templates and the *-review-loop@1
workflows use the Flash slugs (MiniMax silently maps unknown names to M3, so
the provider-id translation lands in agent-runtimes)
22 lines
722 B
YAML
22 lines
722 B
YAML
# agent-runtime-framework — model-registry/ (CRS tag: model-registry)
|
|
# Max-effort Flash; replaces minimax-m3-max in planning/draft-heavy and explicit-model nodes.
|
|
# PLACEHOLDER scores/costs: scores are copied from the M3 entry this replaces and
|
|
# costs are set just below it so cheapest-wins (tiers.yaml) selects Flash over
|
|
# the retained M3 entries. Revisit with observed scores and published pricing.
|
|
name: minimax-m31-flash-max
|
|
endpoint: minimax-m31-flash-max
|
|
provider: minimax
|
|
family: minimax
|
|
scores:
|
|
complexity: 10
|
|
test_pass_rate: 9
|
|
creativity: 10
|
|
spec_adherence: 9
|
|
cost_efficiency: 5
|
|
context_utilisation: 10
|
|
cost_per_1k_tokens:
|
|
input: 0.0025
|
|
output: 0.0125
|
|
source: benchmark
|
|
harness_version: null
|