[sorensencc-dotcom]

No description provided.

[trailhq-graft]

🌱 graft blast radius

Nothing outside this diff depends on it. 2 areas changed; no indexed dependents at depth 2.
Tests: no test reaches CLI Query Root; 1 area updated its tests.
Tag: @anirudhkumar-nanonets — Root Resolution, CLI Query Root

Who knows this code — 1 person across 2 areas

Area	Who knows it
Root Resolution · changed	@anirudhkumar-nanonets — 1 commit, last 3mo ago
CLI Query Root · changed	@anirudhkumar-nanonets — 68 commits, last yesterday

Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no @ has no GitHub handle in its commit email — tag them by hand, or add a .mailmap entry. A suggestion from history, not a CODEOWNERS rule.

Test signal per changed area — 1 ✓ · 1 ✗

Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.

• ✓ Root Resolution — 1 of 2 reached · 1 test file changed here: test/graph-root.test.ts
  • not reached: nearestGitRoot
• ✗ CLI Query Root — 0 of 1 reached · no test file reaches it
  • not reached: queryRoot

_{graft blast · origin/main...HEAD · depth 2 · 3 changed files}

Open the interactive graph → — click an area to see its dependent symbols at file:line.

[shhdwi]

The root fix here is real. With a child checkout inside a built parent repo, ask childFn from the child returned parentFn on main and check said OK, both from the parent's map. With this PR you get no results and check: NO GRAPH, which is right.

The PR also bundles unrelated release work, though:

• a version bump from 0.28.0 to 0.28.1
• server.json and mcpName for the MCP Registry
• a root .mcp.json that runs npx -y @trailhq/trail-code mcp for anyone who opens the repo

The registry work is being handled in #742/#761. Could you split out just the src/graph/root.ts fix and its tests into its own PR? Also, the notice it prints says it's answering from a child/graft that doesn't exist, so that line could use a fix.

[shhdwi]

Pushed two commits to your branch so this can go in on its own:

• Dropped the release and MCP Registry changes (version bump, server.json, mcpName, root .mcp.json). Those are handled in List Trail Code in MCP directories; release 0.28.1 #742/Release 0.29.0: Anirudh's work since 0.28.0 #761. The PR now holds only the src/graph/root.ts fix and its test.
• src/cli.ts: the "no code map here: answering from …" notice now prints only when the root it stopped at has a graph. Before, a child checkout with no graph named a child/graft that doesn't exist.

Checked with a built parent repo and an unbuilt child checkout inside it: from the child, ask childFn returns no results and check says NO GRAPH, with no misleading notice. From a plain subdirectory of the parent, the notice still appears. test/graph-*.test.ts passes.