feat(agent-sdk): context-bundle contract + token budgeter (F1)

[officialCodeWork]

Step 5.2 — Context-bundle contract

Failure mode F1 (wrong-sized output blows the agent's context window). The ContextBundle is the budgeted payload resolveContext produces.

• Sections: match (instances + evidence), lineage (per-instance data sources), journeys (slice around the match, depth 2), blastRadius / tests / history (empty until 5.3 / 5.4 / 5.6), and warnings (staleness, incomplete flags, trims).
• Budgeter: a deterministic ~4-chars-per-token estimate; when over budgetTokens, sections are emptied in reverse priority (history → tests → journeys → blastRadius → lineage; match is never dropped, only reduced to top-1), and each trim is logged to warnings.
• JSON Schema (schemas/context-bundle.schema.json) committed + drift-gated, mirroring the core schema setup.

CLI

$ ui-lineage bundle "the 'All users' page is broken" -b 4000
{ "status": "matched", "match": [{ "component": "UsersPage", … }], "journeys": [ … ],
  "budget": { "tokens": 4000, "used": 560 }, "warnings": [] }

Tests

• agent-sdk: budget compliance at 2k/4k/8k, trim order, out-of-domain decline, schema drift gate.
• parser-react: bundle over a real scanned graph (b3 fixture) — match/lineage/journeys populated, every bundle ≤ budget.

Verification

41 core + 14 agent-sdk + 3 vision + 107 parser tests pass; pnpm eval green; bundle has no leaked @coderadar imports.

🤖 Generated with Claude Code