Perf: Optimize doc lookup

[gaojude]

• Fix the contradictory instruction ('search is recommended' vs 'skip search') in the init tool
• Forces consistent behaviour -- get index from init, and then read the docs from the path of that index; no search, force understanding of the model

Before

❯ init next devtools 

● I'll initialize the Next.js DevTools MCP for this project.

● next-devtools - init (MCP)(project_path:
                            "/home/judegao/projects/furry-together")
  ⎿  {                                                                     
       "success": true,
       "description": "Next.js DevTools MCP Initialization",
     … +114 lines (ctrl+o to expand)

● Initialization complete.

❯ what is refresh() api in next.js? 

● I'll look up the refresh() API in the Next.js documentation for you.

● next-devtools - nextjs_docs (MCP)(action: "search", query: "refresh() API")
  ⎿ {                                                                      
      "error": "SEARCH_NOT_NEEDED",
      "message": "You already have the complete Next.js docs index from the
    i
    … +4 lines (ctrl+o to expand)

● readMcpResource(Read resource "nextjs-docs://llms-index" from server
                 "next-devtools")
  ⎿  {                              
       "contents": [
         {
     … +863 lines (ctrl+o to expand)

● Let me get the full documentation for the refresh() API.

● next-devtools - nextjs_docs (MCP)(action: "get", path:
                                   "/docs/app/api-reference/functions/refresh")
  ⎿  {                                                                     
       "path": "/docs/app/api-reference/functions/refresh",
       "anchor": null,
     … +22 lines (ctrl+o to expand)

● refresh() API in Next.js

  The refresh() function allows you to refresh the client router from within a Server Action.

  Key Points:

After

❯ init next devtools

● I'll initialize the Next.js DevTools MCP for you.

● next-devtools - init (MCP)(project_path: "/home/judegao/next-devtools-mcp")
  ⎿  {
       "success": true,
       "description": "Next.js DevTools MCP Initialization",
     … +41 lines (ctrl+o to expand)

● Initialization complete.

❯ whats refresh api?

● I'll look up the refresh API in the Next.js documentation for you.

● readMcpResource(Read resource "nextjs-docs://llms-index" from server "next-devtools")
  ⎿  {
       "contents": [
         {
     … +523 lines (ctrl+o to expand)

● next-devtools - nextjs_docs (MCP)(path: "/docs/app/api-reference/functions/refresh")
  ⎿  {
       "path": "/docs/app/api-reference/functions/refresh",
       "anchor": null,
     … +14 lines (ctrl+o to expand)

● The refresh API in Next.js allows you to refresh the client router from within a Server Action.

  Key Points:

[huozhi]

unexpected change?