Repository navigation
Codex/trail repo context 0281 - #744
sorensencc-dotcom wants to merge 2 commits into
Conversation
The official MCP Registry accepts a server only when the npm package it names carries mcpName. pack-trail.mjs now puts mcpName io.github.trailhq/trail-code on @trailhq/trail-code alone, and both packages get MCP keywords for npm search. server.json is the registry entry (from mcp-publisher init, then fixed: description under the 100-character limit, the trailhq/Trail-Code URL, the `mcp` argument so npx starts the server rather than the CLI, and no placeholder API key). .mcp.json at the root is how Cursor Directory and others find the server. The repo's package.json keeps the @nanonets/graft name: the registry reads npm, not the repo, and tests assume this checkout runs as graft.
🌱 graft blast radius2 areas changed → 1 area can be affected. 4 dependent symbols, depth 2. flowchart TB
A0(("CLI Commands<br/>4 symbols"))
classDef reached fill:#D9EDF3,stroke:#3AA7C9,stroke-width:1.5px,color:#0E313C;
class A0 reached;
Who knows this code — 1 person across 3 areas
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 All 4 dependent symbols, grouped by areaCLI Commands — 4 symbols in 1 file
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.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
|
The root fix here is real. With a child checkout inside a built parent repo, The PR also bundles unrelated release work, though:
The registry work is being handled in #742/#761. Could you split out just the |
No description provided.