vrr/ouroboros
2
0
Fork 0
mirror of https://github.com/razzant/ouroboros.git synced 2026-10-03 12:18:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
ouroboros/devtools
History
Ouroboros 61612a18dc tests: restore the process environment between tests; pin the container disclosure end to end 
`run_tb.apply_all_model` — and `main --all-model` through it — writes the
fixed-model contract into `os.environ` directly; that is the launcher's real
behaviour and stays. But a test exercising it handed the written
`OUROBOROS_REVIEWER_SLOTS` and forwarded slot keys to every later test of
the same xdist worker (`monkeypatch.delenv(raising=False)` records nothing
for a key that did not exist, so nothing removed it afterwards), which is
the `benchmark-scope-1` contamination that made scope-review identity tests
and the legacy metadata test fail depending on worker order — on the base
commit as much as here. The class is closed where the other between-tests
hygiene lives, `tests/conftest.py`: every test runs on a snapshot of the
process environment restored afterwards whatever it wrote, and the inherited
reviewer panel is scrubbed with the actor list and account pin, so a test
that pins the legacy comma-list branch (the metadata test in
test_devtools_benchmarks.py, a shrink-only byte-debt module that therefore
stays untouched) never reads the operator's shell. The TB methodology suite
lives outside tests/ and carries the same snapshot fixture itself.

The container-provenance disclosure is now pinned end to end through
`main` (command generation, no harbor): `run_manifest.json` carries
`extra.triad_rows_not_executable_in_container` with the session rows'
targets verbatim and in row order — including a target with its own `/`
(`cursor=openai/gpt-5`) — and `metadata.yaml` carries the same list as a
comment while declaring no session row as a model. The gate run for this
commit exported a poisoned shell `OUROBOROS_REVIEWER_SLOTS` on purpose and
stayed green.
2026-09-03 19:33:57 +00:00
..
benchmarks tests: restore the process environment between tests; pin the container disclosure end to end 2026-09-03 19:33:57 +00: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.