mirror of
https://github.com/garrytan/gbrain.git
synced 2026-07-27 22:15:33 +00:00
* fix(doctor,entities): supervisor crash classification + bare-name resolver + stub guard - doctor.ts/jobs.ts: classify worker exits with code !== 0 as real crashes vs code === 0 clean restarts (separate counter); fixes false-positive WARN on healthy supervisors - entities/resolve.ts: prefix-expansion step between fuzzy match and slugify fallback catches bare first names that score too low on pg_trgm; picks highest-connection candidate as tiebreaker - facts/fence-write.ts: stub-creation guard refuses to spawn unprefixed entity pages at brain root - facts/backstop.ts: routes stubGuardBlocked facts to engine.insertFact so the fact still persists even when no markdown file is created - docs/issues/doctor-auto-heal-and-scoring.md: spec for follow-up doctor health-score improvements - .gitignore: guard reports/network-intelligence/ (private brain exports) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(privacy): scrub real names from entity-resolve test fixtures and JSDoc Replace YC partner names with placeholders per CLAUDE.md privacy rule: alice-example, bob-example, charlie-example, dave-example. Stripe and Stripe Atlas retained (allowed household brands; exercises the two-word company-prefix case). Test semantics preserved: - Alice / Dave: single-match cases - Bob / Charlie: multi-match tiebreaker cases (winner has more chunks) All 13 entity-resolve cases pass with the scrubbed fixtures. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * refactor(supervisor): extract classifyWorkerExit() helper (DRY) Three call sites were inline-classifying worker exits: supervisor's restart policy (child-worker-supervisor.ts:291), doctor's supervisor check (doctor.ts:1016), and jobs supervisor status (jobs.ts:806). Same rule, three copies — drift risk if one is updated without the others. Extract to src/core/minions/exit-classification.ts as a pure function. Signature consumes audit-JSON shape ({ code: number | null }) so doctor and jobs (which read serialized events from JSONL) and supervisor (which reads Node's exit callback) call the same function. Helper's classification rule: code === 0 → clean_exit, everything else (non-zero, null, undefined, missing) → crash. Default-to-crash prevents corrupted rows from silently demoting into the clean-restart bucket. 5 hermetic unit tests (test/exit-classification.test.ts) pin all edge cases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(facts): audit + sunset comment for stub-guard fires Wire telemetry into the v0.34.5 stub-guard at fence-write.ts:190. Every guard fire now appends a JSONL line to ~/.gbrain/audit/stub-guard-YYYY-Www.jsonl with {ts, slug, source_id, fact_count}. Operator visibility for the sunset criterion: when the new audit log reads <5 hits/week for 3 consecutive weeks on production brains, the prefix-expansion in resolveEntitySlug is sufficient and the guard can be removed in v0.36. Reader (readRecentStubGuardEvents) deliberately diverges from supervisor-audit.ts:readSupervisorEvents — it reads BOTH the current AND previous ISO-week file before filtering by ts. supervisor-audit's reader only reads the current week, which loses 24h-window correctness across Monday 00:00 UTC (a Sunday 23:55 event lives in last week's file). The 2-file read costs nothing and makes the window actually 24h. 9 hermetic unit tests pin filename math, the writer's swallows-errors contract, the cross-week-boundary read, sort order, missing-file behavior, and malformed-row tolerance. The cross-week test is the regression guard: if a future refactor copies the supervisor's single-file pattern, that test fails. Follow-up TODO (not in this PR): fix readSupervisorEvents to use the same 2-file pattern. The new stub-guard reader becomes the canonical template to copy back. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(doctor): stub_guard_24h check surfaces resolver gaps Adds a new doctor check that reads ~/.gbrain/audit/stub-guard-YYYY-Www.jsonl (via the dual-week-aware reader from T8) and surfaces the 24h fire count. WARN at >10 fires — at that rate the prefix-expansion in resolveEntitySlug is probably missing a case (typo prefix, alias, non-Latin script) and operators should grep the audit log for the offending slugs. Below the threshold but non-zero shows as OK with a count, so operators can watch the v0.36 sunset criterion (<5/week for 3 weeks → guard can be removed). Zero hits emits no check, keeping the doctor output clean on healthy brains. 5 source-grep regression tests pin the contract: check name, WARN threshold, fix hint mentions the audit log + the resolver function name, reader is the dual-week-aware variant (NOT the supervisor-audit single- week pattern), and zero-hits stays silent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(facts): pin stub-guard contract at writeFactsToFence + backstop layers - fence-write.test.ts: 3 new cases for the v0.34.5 stub guard. Bare slugs return {inserted: 0, stubGuardBlocked: true, ids: []} and create no file/.tmp at brain root. Prefixed slugs bypass the guard (regression guard against accidentally inverting the slug.includes('/') check). Empty facts array short-circuits before the guard fires. - facts-backstop.test.ts: 1 new case for the end-to-end routing. A bare-name LLM extraction resolves through to a bare slug, hits the guard, and lands in the facts table via engine.insertFact (DB-only). No phantom .md file; entity_slug stores the bare slug; source_markdown_slug is null. This is the routing contract Codex flagged as a "split-brain" data shape — the test pins the by-design behavior so a future refactor can't silently drop these facts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(supervisor): pin classifyWorkerExit consumer wire-up + regressions 12 new cases on top of the 5 helper unit tests: - doctor.ts / jobs.ts / child-worker-supervisor.ts each import the helper - All three call classifyWorkerExit at least once - doctor.ts and jobs.ts no longer carry the pre-T7 inline filter - supervisor uses the helper result to choose the clean_exit branch - audit-event shape round-trip: code=0 → clean_exit, code=1 → crash, code=null+SIGKILL → crash (catches future shape changes) The regression guards (3) and the wire-up checks (6) close the gap that motivated T7 in the first place: if a future change accidentally re-inlines the filter or shifts the audit event shape, the test fails before production sees the silent divergence. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * perf(entities): correlated subqueries scoped to slug-LIKE candidates Replace the derived-table JOIN shape in tryPrefixExpansion with correlated subqueries. The pre-fix SQL did LEFT JOIN (SELECT to_page_id, COUNT(*) FROM links GROUP BY to_page_id) li ON ... which forced the planner to aggregate the entire links + content_chunks tables on every prefix-expansion call — O(N) per call where N is total links/chunks in the brain. On a 100K-link / 50K-chunk brain that's slow enough to bottleneck fact-extraction. New shape uses correlated subqueries: (SELECT COUNT(*) FROM links WHERE to_page_id = p.id) + (SELECT COUNT(*) FROM links WHERE from_page_id = p.id) + (SELECT COUNT(*) FROM content_chunks WHERE page_id = p.id) The slug LIKE filter is already selective (typical brain has 0-5 pages per prefix), so the three subqueries run N≈3 times per matched row against the existing indexes on links.to_page_id, links.from_page_id, and content_chunks.page_id. Behavior preserved: 13/13 entity-resolve tests pass (single-match + multi-match tiebreaker + edge cases). Codex's outside-voice review caught the dead-end design that an earlier draft of this plan proposed (a CTE with `LIMIT 50` candidate cap — would have excluded correct high-connection candidates if their slug sorted late). Correlated subqueries without a candidate cap are the cleaner shape that lets the LIKE filter do the bounding work. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(entities): perf regression guard for prefix-expansion (58x speedup) Hermetic PGLite benchmark with 5K pages + 50K links + 25K chunks. Runs the pre-T12 derived-table shape and the new correlated-subquery shape side-by-side against the same fixture, asserts NEW >= 5x faster than OLD. Baseline-ratio, not absolute wall-clock — different machines / Bun versions / CI load can shift absolute timings by 10x without indicating a real regression, but the SHAPE difference between "aggregate the full tables" and "correlated subquery per candidate" is what we care about. Measured: old_median=18.16ms, new_median=0.31ms, speedup=58.22x. The 5x assertion has plenty of headroom. The OLD SQL is embedded verbatim as the regression baseline. If a future refactor re-introduces full-table aggregation (LEFT JOIN against SELECT...GROUP BY over the whole links or content_chunks table), the test fails. PGLite-only — Postgres planner can shape derived-table JOINs differently enough that the 5x ratio could be noise on a 5K-page fixture. The structural correctness of the rewrite is the same on both; this is purely a planner-shape regression guard. .slow.test.ts suffix keeps it out of the fast loop (run via `bun run test:slow`). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: bump version and changelog (v0.35.2.0) Wave content: - Privacy scrub: PII rebuilt out of branch history; real names → placeholders - Bug fix: doctor + jobs no longer count clean worker exits as crashes - Bug fix: entity resolver prefix-expansion catches bare first names - DRY refactor: classifyWorkerExit() helper (one rule, 3 call sites) - Observability: stub_guard_24h doctor check + ISO-week audit log - Perf: 58x speedup on tryPrefixExpansion query shape Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: rebump v0.35.2.0 → v0.35.4.0 + scrub TODOS.md privacy violation VERSION/package.json/CHANGELOG header rebumped to v0.35.4.0 per user request (queue allocation). TODOS.md rephrased to not literally name the banned private-agent string — that was the CI failure root cause on the v0.35.2.0 push. CHANGELOG.md is on check-privacy.sh's allow-list (meta-documentation exception); TODOS.md is not. CI re-runs against this commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
167 lines
6.4 KiB
TypeScript
167 lines
6.4 KiB
TypeScript
import { describe, it, expect, beforeAll, afterAll } from 'bun:test';
|
|
import { resolveEntitySlug, slugify } from '../src/core/entities/resolve.ts';
|
|
import { PGLiteEngine } from '../src/core/pglite-engine.ts';
|
|
import type { BrainEngine } from '../src/core/engine.ts';
|
|
|
|
/**
|
|
* Entity resolution prefix expansion tests.
|
|
*
|
|
* Validates that bare first names resolve to existing pages via prefix
|
|
* expansion, preventing phantom stub creation.
|
|
*
|
|
* Fixture names use the `alice-example` / `bob-example` / `charlie-example`
|
|
* / `dave-example` placeholder pattern per CLAUDE.md privacy rule.
|
|
* `stripe` and `stripe-atlas` are intentional — household-brand exception
|
|
* exercises the two-word company prefix case.
|
|
*/
|
|
|
|
let engine: PGLiteEngine;
|
|
|
|
beforeAll(async () => {
|
|
engine = new PGLiteEngine();
|
|
await engine.connect({ database_url: '' });
|
|
await engine.initSchema();
|
|
|
|
// Seed test pages. Naming pattern:
|
|
// - alice-example: single-match case (only people/alice-*)
|
|
// - bob-example vs bob-rosenstein: multi-match tiebreaker (bob-example wins on connections)
|
|
// - charlie-example vs charlie-bankcroft: multi-match tiebreaker (charlie-example wins on connections)
|
|
// - dave-example: single-match case
|
|
const pages = [
|
|
{ slug: 'people/alice-example', title: 'Alice Example', type: 'person' },
|
|
{ slug: 'people/bob-example', title: 'Bob Example', type: 'person' },
|
|
{ slug: 'people/bob-rosenstein', title: 'Bob Rosenstein', type: 'person' },
|
|
{ slug: 'people/charlie-example', title: 'Charlie Example', type: 'person' },
|
|
{ slug: 'people/charlie-bankcroft', title: 'Charlie Bankcroft', type: 'person' },
|
|
{ slug: 'people/dave-example', title: 'Dave Example', type: 'person' },
|
|
{ slug: 'companies/stripe', title: 'Stripe', type: 'company' },
|
|
{ slug: 'companies/stripe-atlas', title: 'Stripe Atlas', type: 'company' },
|
|
];
|
|
|
|
for (const p of pages) {
|
|
await engine.putPage(p.slug, {
|
|
type: p.type as any,
|
|
title: p.title,
|
|
compiled_truth: `# ${p.title}`,
|
|
frontmatter: { type: p.type, title: p.title, slug: p.slug },
|
|
}, { sourceId: 'default' });
|
|
}
|
|
|
|
// Give alice-example 10 chunks (single match, ensures it's the resolved target)
|
|
const alicePage = await engine.executeRaw<{ id: string }>(
|
|
`SELECT id FROM pages WHERE slug = 'people/alice-example' AND source_id = 'default'`,
|
|
[],
|
|
);
|
|
if (alicePage.length > 0) {
|
|
for (let i = 0; i < 10; i++) {
|
|
await engine.executeRaw(
|
|
`INSERT INTO content_chunks (page_id, chunk_index, chunk_text)
|
|
VALUES ($1, $2, $3)`,
|
|
[alicePage[0].id, i, `Chunk ${i} about Alice Example`],
|
|
);
|
|
}
|
|
}
|
|
|
|
// Give charlie-example more connections than charlie-bankcroft (20 vs 0)
|
|
const charliePage = await engine.executeRaw<{ id: string }>(
|
|
`SELECT id FROM pages WHERE slug = 'people/charlie-example' AND source_id = 'default'`,
|
|
[],
|
|
);
|
|
if (charliePage.length > 0) {
|
|
for (let i = 0; i < 20; i++) {
|
|
await engine.executeRaw(
|
|
`INSERT INTO content_chunks (page_id, chunk_index, chunk_text)
|
|
VALUES ($1, $2, $3)`,
|
|
[charliePage[0].id, i, `Chunk ${i} about Charlie Example`],
|
|
);
|
|
}
|
|
}
|
|
|
|
// Give bob-example more connections than bob-rosenstein (15 vs 0)
|
|
const bobPage = await engine.executeRaw<{ id: string }>(
|
|
`SELECT id FROM pages WHERE slug = 'people/bob-example' AND source_id = 'default'`,
|
|
[],
|
|
);
|
|
if (bobPage.length > 0) {
|
|
for (let i = 0; i < 15; i++) {
|
|
await engine.executeRaw(
|
|
`INSERT INTO content_chunks (page_id, chunk_index, chunk_text)
|
|
VALUES ($1, $2, $3)`,
|
|
[bobPage[0].id, i, `Chunk ${i} about Bob Example`],
|
|
);
|
|
}
|
|
}
|
|
});
|
|
|
|
afterAll(async () => {
|
|
await engine.disconnect();
|
|
});
|
|
|
|
describe('resolveEntitySlug — prefix expansion', () => {
|
|
it('resolves "Alice" to people/alice-example', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Alice');
|
|
expect(result).toBe('people/alice-example');
|
|
});
|
|
|
|
it('resolves "alice" (lowercase) to people/alice-example', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'alice');
|
|
expect(result).toBe('people/alice-example');
|
|
});
|
|
|
|
it('resolves "Bob" to people/bob-example (more connections)', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Bob');
|
|
expect(result).toBe('people/bob-example');
|
|
});
|
|
|
|
it('resolves "Charlie" to people/charlie-example (more connections)', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Charlie');
|
|
expect(result).toBe('people/charlie-example');
|
|
});
|
|
|
|
it('resolves "Dave" to people/dave-example (single match)', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Dave');
|
|
expect(result).toBe('people/dave-example');
|
|
});
|
|
|
|
it('falls through to slugify for unknown names', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Zyxwvut');
|
|
expect(result).toBe('zyxwvut');
|
|
});
|
|
|
|
it('exact match still works for fully-qualified slugs', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'people/alice-example');
|
|
expect(result).toBe('people/alice-example');
|
|
});
|
|
|
|
it('multi-word input does NOT trigger prefix expansion', async () => {
|
|
// "Alice Example" should go through fuzzy match, not prefix expansion
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'Alice Example');
|
|
// Should resolve via fuzzy match to the same page
|
|
expect(result).toContain('alice-example');
|
|
});
|
|
|
|
it('hyphenated input does NOT trigger prefix expansion', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', 'alice-example');
|
|
expect(result).toBe('people/alice-example');
|
|
});
|
|
|
|
it('returns null for empty input', async () => {
|
|
const result = await resolveEntitySlug(engine as unknown as BrainEngine, 'default', '');
|
|
expect(result).toBeNull();
|
|
});
|
|
});
|
|
|
|
describe('slugify', () => {
|
|
it('lowercases and hyphenates', () => {
|
|
expect(slugify('Alice Example')).toBe('alice-example');
|
|
});
|
|
|
|
it('handles single word', () => {
|
|
expect(slugify('Alice')).toBe('alice');
|
|
});
|
|
|
|
it('strips accents', () => {
|
|
expect(slugify('José García')).toBe('jose-garcia');
|
|
});
|
|
});
|