Files
agent-runtime-framework/harnesses/composites/integration-direct/v1/harness.yaml
Paul O'Reilly d7decc1dec minimax: move to MiniMax-M3.1-Flash-Preview; drop bare minimax/minimax-m2 slugs
- 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)
2026-10-13 10:55:03 +13:00

16 lines
563 B
YAML

kind: composite
name: integration-direct
version: 1
description: "Integration harness — cherry-picks from agent fork and pushes directly to main after test verification"
layers:
- context: integration/v1
# MiniMax M3 (bulk coding-plan subscription) instead of the Anthropic
# personal-subscription OAuth — integration runs are frequent/mechanical
# and were draining the interactive 5-hour window (2026-09-02).
- context: minimax/v1
- context: minimax-m31-flash/v1
- context: gitea-ssh/v1
- context: agent-repo/v1
- context: direct-push/v1