Treating a codebase's context graph like a build artifact instead of an AI feature

Wanted to share this since it's more of an infra decision than an AI one. Building a context layer for coding agents (Graft), and the part that actually mattered in production use wasn't the LLM piece, it was making the graph behave like any other build artifact: cached by content hash, diffable in git, and there's a graft check command that fails a build (exit 1) if the graph's drifted from the code, same idea as a lint check in CI. The structural graph itself needs no LLM call at all, pure tree-sitter parsing. The optional LLM-written summaries are a separate opt-in layer on top, provider-ag