mirror of
https://github.com/garrytan/gbrain.git
synced 2026-07-27 22:15:33 +00:00
* fix(tests): root-cause two master test-infra flakes
gateway.test.ts: add afterAll(resetGateway) hook. The file's tests use
beforeEach(resetGateway) for per-test isolation, but the FINAL test was
leaving configureGateway({env: {OPENAI_API_KEY: 'openai-fake'}}) in the
gateway module state. Sibling files in the same bun shard (e.g.
test/ingestion/ingest-capture.test.ts) then triggered embed() against
the real OpenAI endpoint with the leaked fake key, wedging the shard
with 'Incorrect API key provided: openai-fake'.
header-transport.test.ts → .serial.test.ts: the file mutates RECIPES
(gateway's module-scoped recipe map) plus configureGateway, then asserts
fakeChatFetch was invoked. Under bun's intra-shard parallelism, sibling
files like test/ai/rerank.test.ts race the same state — chat would see
result.text === '[]' instead of 'ok' because another test called
resetGateway between this test's configureGateway and chat. Quarantining
as .serial.test.ts moves the file into the post-parallel serial pass
at --max-concurrency=1 per repo convention.
* refactor(doctor): extract buildChecks seam + behavioral coverage
src/commands/doctor.ts: extract buildChecks(engine, args, dbSource):
Promise<Check[]> from runDoctor. The check-building logic moves into
the new exported function; existing exported computeDoctorReport(checks)
at line 78 stays untouched. runDoctor becomes a thin wrapper:
buildChecks → computeDoctorReport → render + process.exit. All 10
process.exit sites stay in place. The two early-return paths drop
their inline outputResults+process.exit calls and return the partial
check list; the wrapper still produces identical observable output.
test/doctor-behavioral.test.ts (13 cases): pure pure-aggregation cases
pin computeDoctorReport math (3 fails → -60 points, score clamped at 0,
mixed outcome → unhealthy with fail dominating). Orchestrator cases
assert --fast flag honors the skip set, --json doesn't alter the list,
no-engine path returns partial without process.exit, and the snapshot
of load-bearing check names catches accidental drop-outs during
future refactors.
test/doctor-cli-smoke.serial.test.ts (1 case): subprocess smoke spawning
'bun run src/cli.ts doctor --json' against a fresh PGLite tempdir brain.
Catches render-path bugs that buildChecks-only tests miss — the class
the v0.38.2.0 partial-scan wave exposed. Quarantined as .serial because
PGLite write-locks don't play well with parallel runners; skippable via
GBRAIN_SKIP_SUBPROCESS_TESTS=1.
* feat(operations): trust-boundary contract test + filter-bypass shell guard
test/operations-trust-boundary.test.ts (14 cases): hybrid design per
plan D7. Pure assertions over all 74 ops cover the drift-detection
win (every op has a scope; every mutating op has a non-read scope;
hasScope(['read'], op.scope) correctly rejects 'admin' or 'write').
Plus the canonical filter contract: every localOnly: true op is
excluded from operations.filter(op => !op.localOnly). Plus targeted
handler-invocation cases for the two historically-broken HTTP-callable
classes: submit_job(name='shell', ctx.remote=true) MUST reject (F7b
HTTP MCP shell-job RCE class), and search_by_image(image_path,
ctx.remote=true) MUST reject (D18 P0 image-leak class). file_upload
and sync_brain are deliberately omitted from handler-invocation tests
because they're localOnly — calling their handlers directly tests an
impossible production path (codex CMT-3). All 7 localOnly ops are
snapshot-pinned by name to catch future flag-flips.
scripts/check-operations-filter-bypass.sh: greps src/ for any module
that imports the 'operations' value from core/operations.ts outside
the canonical filter site. Three import shapes detected: destructured,
aliased ('as ops'), namespace ('import * as'). Explicit allow-list of
10 known-safe importers with one-line rationale per entry. Plus a
filter-presence check on serve-http.ts that fails if the canonical
filter expression is refactored out. Codex /ship adversarial review
caught the original narrow regex missed aliased + namespace bypasses;
the expanded regex closes that class. Type-only imports of sibling
exports (sourceScopeOpts, OperationContext) are not flagged.
package.json: wires check:operations-filter-bypass into the verify
chain alongside check:jsonb and check:progress.
* refactor(cycle): export runPhaseLint+runPhaseBacklinks; add wrapper tests
src/core/cycle.ts: adds 'export' keyword to two existing phase
functions so behavioral tests can drive them without going through
runCycle's full setup cost. No body changes; no behavior change.
Documented as internal helpers exposed for test-only consumption —
downstream code should NOT take a dependency on them; existing
plan-eng-review D9 explicitly accepted the API-widening tax for
testability.
test/cycle-legacy-phases.test.ts (11 cases): combined file with two
describe blocks per plan D5 (DRY — shared setup, future phase
wrappers land as additional describes). Narrowed to result-mapping
+ error envelope per codex CMT-1 (legacy phases don't extend
BaseCyclePhase and don't take a progress reporter or AbortSignal
directly, so the contract surface is counter → status enum + try/catch
envelope). Cases: clean run → status='ok', partial fix → status='warn'
with dryRun in details, dry-run path doesn't write, throw-from-lib
→ status='fail' with envelope populated (no exception escape).
Verified runLintCore and runBacklinksCore both throw on missing dir,
so the throw-from-lib cases are deterministic.
* chore: bump version and changelog (v0.40.4.1)
E2E + unit test gap coverage wave. Closes 4 audit gaps with new
behavioral coverage (doctor orchestrator + subprocess smoke, operations
trust-boundary contract + filter-bypass guard, cycle phase wrapper
result-mapping). Verifies 3 audit gaps were already covered (ingestion
dedup/daemon/skillpack-load, phantom-redirect, ingestion test-harness).
Root-causes 2 pre-existing master flakes (gateway state leak, header-
transport cross-shard race). Files 5 follow-up TODOs from codex
adversarial-review findings.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: note v0.40.4.1 doctor.buildChecks + cycle phase exports in CLAUDE.md
Adds three Key-files entries pinning the v0.40.4.1 test-wave additions:
- doctor.ts extension: buildChecks seam + behavioral tests (13+1 cases)
- cycle.ts extension: runPhaseLint + runPhaseBacklinks exports (11 cases)
- operations-trust-boundary contract + check-operations-filter-bypass.sh
Regenerates llms-full.txt to match (CLAUDE.md edits require build:llms per
project rule, otherwise test/build-llms.test.ts fails in CI shard 1).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(tests): reset gateway in put_page write-through tests to skip embed in CI
CI failure mode: 9 tests in test/ingestion/put-page-write-through.test.ts
failed with `AIConfigError: [embed(zeroentropyai:zembed-1)] Unauthorized`
because put_page's handler at src/core/operations.ts:622 computes
`noEmbed = !isAvailable('embedding')`. When the gateway state has been
configured by a sibling test (or by the cli.ts module-load path reading
.env.testing) with a fake/stale ZEROENTROPY_API_KEY, isAvailable returns
true → put_page tries to embed → the real ZeroEntropy API returns 401.
Local dev passes because real ZE keys are present; CI doesn't have them.
Fix: call resetGateway() in beforeEach so isAvailable('embedding')
returns false → put_page's noEmbed path activates → no network call.
Also reset in afterAll to avoid leaking the cleared state to sibling
files in the same bun shard (the v0.40.4.1 gateway state-leak class
that motivated the earlier gateway.test.ts fix).
The test exercises write-through behavior, not embedding. No need for
a real or fake embed transport — bypass entirely.
* fix(tests): widen brain-writer partial-scan deadlines to absorb CI timing variance
CI failure: scanBrainSources partial-scan state > "hanging COUNT does not
exceed deadline — Promise.race timeout fires" failed once on a GitHub
Actions runner. The test asserted a 100ms deadline budget with a 500ms
bound; observed test duration was 187ms on CI (passes locally 20/20
runs at the original budget).
Root cause: Node.js timer drift under shard parallelism. The deadline
check at src/core/brain-writer.ts:503 uses strict `Date.now() > deadline`,
so when the setTimeout in Promise.race fires exactly at the boundary
(e.g. start+100ms when deadline is start+100ms), the post-await check
sees equality and skips the markRemainingSkipped branch. The test
also asserts elapsed < 500ms; CI overhead can push elapsed past that
bound when setTimeout drifts.
Fix: widen the deadline budget on both deadline-race tests proportionally
(keeps the same 2x ratio that proves "query exceeds deadline"). No
src/ changes — this is purely a test robustness widening.
- "hanging COUNT" test: 100ms → 500ms deadline, 500ms → 2500ms bound
- "slow COUNT" test: 50ms → 250ms deadline, 100ms → 500ms query delay
Verified locally: 20/20 stress runs at the widened budgets, no fails.
* fix(brain-writer): deadline check is >= not > (closes CI flake at boundary)
CI failure recurred: same "hanging COUNT does not exceed deadline" test
failed again at 588ms (past my previous 500ms deadline + 2500ms bound
widening). The root cause isn't test timing — it's an off-by-one in
the source.
src/core/brain-writer.ts had two deadline checks using strict `>`:
- line 445 (between-source abort)
- line 503 (post-COUNT-await re-check)
The Promise.race setTimeout resolves null at exactly `remainingMs` from
now, so post-await Date.now() OFTEN equals the deadline within
integer-ms precision. With `>`, the check skipped → scanOneSource ran
on the source whose budget had just been eaten → that source got
status='scanned' instead of 'skipped'. The test's `expect(firstSource
.status).toBe('skipped')` failed.
Fix: both checks now use `>=`. When Date.now() equals deadline exactly,
the budget IS exhausted — proceeding would let the next source eat its
own budget on top of what's already spent. Matches the boundary the
Promise.race's remainingMs <= 0 immediate-null path uses (line 481).
This is the real fix for the v0.40.x CI flakes; my earlier test-budget
widening papered over the symptom without closing the boundary. Kept
the wider 500ms deadline for headroom but added a comment pointing at
the operator fix as the load-bearing change.
Verified: 20/20 stress runs green locally after the operator fix.
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
116 lines
5.6 KiB
Bash
Executable File
116 lines
5.6 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# v0.39 — CI guard against bypassing the localOnly filter on the HTTP MCP
|
|
# surface. Lives alongside check-jsonb-pattern.sh / check-progress-to-stdout.sh
|
|
# in the bun run verify chain.
|
|
#
|
|
# Background: serve-http.ts builds the HTTP MCP tools/list response from
|
|
# `operations.filter(op => !op.localOnly)`. That filter is the only thing
|
|
# keeping localOnly ops (sync_brain, file_upload, file_list, file_url —
|
|
# any admin op the user EXPLICITLY marked as CLI-only) off the wire.
|
|
#
|
|
# If a future HTTP-exposing module imports `operations` from
|
|
# core/operations.ts WITHOUT applying the filter, the localOnly contract
|
|
# silently breaks: a write-scoped OAuth client could submit `sync_brain`
|
|
# or `file_upload` over HTTP. Codex outside-voice review of the e2e-test-
|
|
# wave (CMT-3) flagged this exact bypass class.
|
|
#
|
|
# The guard works by:
|
|
# 1. Listing every file that imports `operations` from core/operations.ts.
|
|
# 2. Comparing against an explicit ALLOWLIST of known-safe importers
|
|
# (each with a rationale below).
|
|
# 3. Failing if a new file is missing from the allowlist — forces the
|
|
# author to either (a) join the allowlist with an explicit rationale,
|
|
# or (b) apply the canonical filter at import.
|
|
#
|
|
# This is a structural defense. The runtime defense lives in
|
|
# test/operations-trust-boundary.test.ts (the canonical filter contract +
|
|
# handler-invocation cases for the historically-broken classes).
|
|
#
|
|
# To allow a new importer: add the relative path to ALLOWED below with a
|
|
# one-line comment explaining why localOnly isn't a concern there.
|
|
#
|
|
# Exit: 0 when no unknown importers, 1 when at least one is missing from
|
|
# the allowlist.
|
|
set -euo pipefail
|
|
|
|
ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
|
|
cd "$ROOT"
|
|
|
|
# Files allowed to import `operations` directly. Each entry must be
|
|
# accompanied by a one-line rationale (the comment on the same line).
|
|
ALLOWED=(
|
|
"src/cli.ts" # local CLI; user owns the machine, no trust boundary
|
|
"src/mcp/dispatch.ts" # shared dispatch; sets ctx.remote from caller, handlers self-gate
|
|
"src/mcp/server.ts" # stdio MCP; local-trusted (binary on user's box)
|
|
"src/mcp/http-transport.ts" # superseded by serve-http.ts; kept for back-compat tests
|
|
"src/mcp/tool-defs.ts" # pure helper; takes ops as parameter, never exposes them
|
|
"src/core/minions/tools/brain-allowlist.ts" # subagent registry; has its own opt-in allowlist (separate from localOnly)
|
|
"src/commands/capture.ts" # local CLI tool; not network-exposed
|
|
"src/commands/book-mirror.ts" # local CLI tool; not network-exposed
|
|
"src/commands/tools-json.ts" # gbrain --tools-json introspection; full op list IS the purpose
|
|
"src/commands/serve-http.ts" # MUST APPLY .filter(op => !op.localOnly) — verified by grep below
|
|
)
|
|
|
|
# Pattern: any import that brings the `operations` VALUE in from core/operations.ts.
|
|
# Three shapes the value can enter through; each must be caught:
|
|
# - destructured: import { operations } from '...core/operations.ts'
|
|
# - aliased: import { operations as ops } from '...core/operations.ts'
|
|
# - namespace: import * as opsModule from '...core/operations.ts'
|
|
# The original narrow regex only matched the destructured form — codex caught
|
|
# the bypass class during /ship adversarial review (aliased + namespace forms
|
|
# slipped through). The broadened regex below specifically requires `operations`
|
|
# inside the destructured clause OR a namespace import (`* as X`); type-only
|
|
# imports of sibling exports like `sourceScopeOpts` / `OperationContext` are
|
|
# left alone (those don't expose the op list to a transport surface).
|
|
PATTERN='import[[:space:]]+(\*[[:space:]]+as[[:space:]]+[a-zA-Z_$][a-zA-Z0-9_$]*|\{[^}]*\boperations\b[^}]*\})[[:space:]]+from[[:space:]]*['\''"][^'\''"]*core/operations\.ts['\''"]'
|
|
|
|
# Collect files that import `operations`. Use a while-loop over grep output
|
|
# instead of `mapfile` to stay compatible with macOS's default bash 3.2.
|
|
FOUND_FILES=""
|
|
while IFS= read -r f; do
|
|
[ -n "$f" ] && FOUND_FILES="$FOUND_FILES$f"$'\n'
|
|
done < <(grep -rlE --include='*.ts' "$PATTERN" src/ 2>/dev/null | sort -u || true)
|
|
|
|
FAIL=0
|
|
|
|
# Check 1: every found file is in ALLOWED.
|
|
while IFS= read -r file; do
|
|
[ -z "$file" ] && continue
|
|
rel="${file#"$ROOT/"}"
|
|
ok=0
|
|
for allowed in "${ALLOWED[@]}"; do
|
|
if [ "$rel" = "$allowed" ]; then
|
|
ok=1
|
|
break
|
|
fi
|
|
done
|
|
if [ "$ok" -eq 0 ]; then
|
|
echo "FAIL: $rel imports operations but is not in scripts/check-operations-filter-bypass.sh ALLOWED list."
|
|
echo " Either apply .filter(op => !op.localOnly) at the import boundary,"
|
|
echo " or add this file to ALLOWED with a one-line rationale."
|
|
FAIL=1
|
|
fi
|
|
done <<< "$FOUND_FILES"
|
|
|
|
# Check 2: serve-http.ts MUST contain the canonical filter expression near
|
|
# its operations import. Without the filter, the entire HTTP MCP surface
|
|
# leaks localOnly ops.
|
|
SERVE_HTTP="src/commands/serve-http.ts"
|
|
if [ -f "$SERVE_HTTP" ]; then
|
|
if ! grep -qE 'operations\.filter\(\s*op\s*=>\s*!op\.localOnly\s*\)' "$SERVE_HTTP"; then
|
|
echo "FAIL: $SERVE_HTTP no longer contains the canonical"
|
|
echo " operations.filter(op => !op.localOnly) expression. The HTTP MCP"
|
|
echo " surface depends on this filter to enforce localOnly. Restore"
|
|
echo " the filter or refactor the trust boundary explicitly."
|
|
FAIL=1
|
|
fi
|
|
fi
|
|
|
|
if [ "$FAIL" -eq 1 ]; then
|
|
echo ""
|
|
echo "Hint: see test/operations-trust-boundary.test.ts for the runtime contract."
|
|
exit 1
|
|
fi
|
|
|
|
exit 0
|