skynet/agent-runtime-framework
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

minimax: move to MiniMax-M3.1-Flash-Preview; drop bare minimax/minimax-m2 slugs

Browse Source 
- 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)
This commit is contained in:
Paul O'Reilly
2026-10-13 10:55:03 +13:00
parent c8c9e7f7d0
commit d7decc1dec
21 changed files with 121 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
harnesses/composites/best-practices-minimax-repo/v1/harness.yaml
View File

@@ -6,6 +6,6 @@ description: "Best practices review agent on MiniMax M3 (max effort) + repo clon
layers:
- context: best-practices/v1
- context: minimax/v1
- context: minimax-m3-max/v1
- context: minimax-m31-flash/v1
- context: gitea-ssh/v1
- context: agent-repo/v1