vrr/ouroboros
2
0
Fork 0
mirror of https://github.com/razzant/ouroboros.git synced 2026-08-06 09:09:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
ouroboros/devtools
History
Exact
Anton Razzhigaev 07dac4f644 fix(minimax): review findings — slash-form routing, docs pins, secret enums 
Triad/scope review of the reworked PR surfaced four issues, fixed here:

- pricing.infer_api_key_type: un-prefixed "minimax/..." ids now classify
  as OpenRouter. Unlike cloudru/gigachat, minimax IS a real OpenRouter
  vendor namespace and slash-form ids stay router-style by design; the
  removed branch made safety.py demand MINIMAX_API_KEY on OpenRouter
  installs with a minimax/ light model, silently skipping the LLM safety
  check (fail-open). Regression tests added for both spellings.
- tests/test_docs_sync.py pinned the pre-MiniMax direct-provider
  fallback sentence and failed deterministically after the ARCHITECTURE
  sync; the pin now carries the MiniMax-inclusive wording.
- Docs enumerations that decide review behavior now include MiniMax:
  DEVELOPMENT deep-slot EXCEPTION (512K guaranteed floor rationale),
  CHECKLISTS item 2h provider-independence list, ARCHITECTURE
  _REVIEW_ROUTE_BASE_URL_KEYS and unknown-pricing route lists.
- Benchmark/devtools secret and credential enumerations gained
  MINIMAX_API_KEY (+MINIMAX_REGION where the pattern carries routing
  keys): common/secrets, TB submission scrubber, isolated server_runner
  env allowlist, harbor agent secret keys, GAIA credential resolver —
  so a MiniMax key is masked/scrubbed like every other provider key and
  minimax:: models resolve their own credentials in bench lanes.

Co-authored-by: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com>
2026-08-04 16:09:57 +03:00
..
benchmarks fix(minimax): review findings — slash-form routing, docs pins, secret enums 2026-08-04 16:09:57 +03:00
__init__.py feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00
README.md feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00

README.md

Ouroboros Devtools

devtools/ contains operator-side and benchmark support code that should be versioned with Ouroboros without becoming part of the runtime core.

Rules:

  • Generated logs, datasets, run outputs, Docker layers, and secrets do not live here.
  • Default benchmark outputs go under /Users/anton/Ouroboros/bench_runs/.
  • Runtime modules must not import devtools.
  • This is not an immune-system bypass: touched files are reviewed normally.
  • Promote code out of devtools only through a separate reviewed runtime plan.