#314 scrubbed BRAVE_API_KEY per test file, which leaves the next research
test free to reintroduce the leak. A bun test preload now deletes every
setting the research providers and the gateway backend read, for every run
started from the repo root. Tests that need one still set their own value.
- scripts/test-preload.ts: the scrub.
- bunfig.toml: [test] preload.
- core/test/clean-room.test.ts: a probe suite started with all six settings
exported must see none of them.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The 2.0.0-2.3.0 entries described the Phase 6-9 mechanisms as working
flows ("stop needing a human passphrase", "hot-swap its own binaries").
A symbol search over packages/*/src finds no caller for the machine key,
the staging pipeline, the prompt optimizer, the canary runner or lease
acquisition, and run-dag plus the canary live in the private fleet package.
- CHANGELOG: each intro now names what is reachable; 2.3.0 lists reachable,
library-only and not-in-npm pieces, and records that 1.6.1-2.2.0 were
never published and ship in 2.3.0.
- README status line: same correction.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
With BRAVE_API_KEY exported in the developer shell, fires-research and
research booted hosts whose provider chain reached the live Brave API
before the local SearXNG fake: six tests went red and each run spent the
real key. Both files now remove BRAVE_API_KEY and FIRECRAWL_API_KEY for
their lifetime and restore them afterwards, as failover-chain.test.ts
already does. The degradation block closes through bootHost's handle so
the restore runs there too.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
`bun run check` could not pass in a checkout that holds the gitignored
review/ reference repos. `biome check .` stopped on their nested root
configs, and the bare `packages/web` test filter also matched
review/*/packages/web, so third-party suites ran and the workspace suite
never started. CI and ticket worktrees have no review/, which hid it.
- package.json: the test script passes ./packages/<dir> paths, not filters.
- bunfig.toml: test discovery starts at packages/.
- biome.json: force-ignore review, evals/results and nested checkout roots.
- tsconfig.base.json: exclude review and evals/results.
- core/test/clean-room.test.ts: runs the real root config against a tree
with planted intruders, one test per layer.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
BillyOutlast