structx 1.0.0 → 2.1.0

package/dist/instructions/codex.md

@@ -0,0 +1,70 @@
+# StructX — Code Intelligence Graph (MANDATORY)
+
+This project uses **StructX**, a graph-powered code intelligence tool for TypeScript.
+StructX maintains a knowledge graph of the codebase including functions, types, routes,
+constants, and file summaries. **You MUST use StructX as your primary source of codebase
+understanding. Do NOT read raw source files to learn about the codebase.**
+
+## Mandatory Workflow
+
+### Step 1: Initialize (ALWAYS do this first)
+Run `npx structx status` to check the graph state.
+- If it says "not initialized", run `npx structx setup .`
+- If Functions/Types/Routes counts are 0, run `npx structx setup .`
+- **Do NOT proceed to any code task until StructX is initialized and populated.**
+
+### Step 2: Understand the codebase via StructX (NEVER skip this)
+Before writing ANY code, you MUST query StructX to understand the codebase:
+```
+npx structx overview --repo .
+npx structx ask "what types and interfaces exist?" --repo .
+npx structx ask "what routes/endpoints exist?" --repo .
+npx structx ask "how does <relevant feature> work?" --repo .
+```
+**You are FORBIDDEN from reading .ts source files to understand the codebase architecture,
+discover what functions exist, learn about types, or understand how features work.
+StructX provides all of this. Use it.**
+
+### Step 3: Read source files ONLY for editing
+You may ONLY use raw file reads when you have ALREADY queried StructX and now need to
+see the exact code at a specific location to make an edit. The workflow is:
+1. Ask StructX what exists and where it is
+2. StructX tells you the file path and line numbers
+3. THEN read that specific file to make your edit
+
+**Reading source files to "explore" or "understand" the codebase is PROHIBITED.
+That is what StructX is for.**
+
+### Step 4: After making changes
+After editing any TypeScript files:
+```
+npx structx ingest .
+npx structx analyze . --yes
+```
+
+### Step 5: Impact analysis before modifying existing code
+Before changing any existing function, type, or route:
+```
+npx structx ask "what breaks if I change <name>?" --repo .
+```
+
+## Available Commands
+
+| Command | Description |
+|---------|-------------|
+| `npx structx status` | Check graph state — ALWAYS run first |
+| `npx structx setup .` | Full bootstrap (init + ingest + analyze) |
+| `npx structx overview --repo .` | Full codebase summary in one shot |
+| `npx structx ask "<question>" --repo .` | Query the knowledge graph |
+| `npx structx ingest .` | Re-parse codebase after changes |
+| `npx structx analyze . --yes` | Run semantic analysis on new/changed entities |
+
+## Rules Summary
+
+1. **ALWAYS** run `structx status` at session start
+2. **ALWAYS** run `structx setup .` if not initialized
+3. **ALWAYS** use `structx ask` or `structx overview` to understand the codebase
+4. **NEVER** read .ts files to explore/understand architecture — use StructX
+5. **ONLY** read .ts files when you know exactly what file+line to edit (from StructX output)
+6. **ALWAYS** run `structx ingest .` after making code changes
+7. **ALWAYS** run impact analysis before modifying existing functions

package/dist/instructions/copilot.md

@@ -1,39 +1,70 @@
-# StructX — Code Intelligence Graph
+# StructX — Code Intelligence Graph (MANDATORY)
 
 This project uses **StructX**, a graph-powered code intelligence tool for TypeScript.
-StructX maintains a function-level knowledge graph of the codebase that you should use
-instead of reading raw source files when answering code questions.
+StructX maintains a knowledge graph of the codebase including functions, types, routes,
+constants, and file summaries. **You MUST use StructX as your primary source of codebase
+understanding. Do NOT read raw source files to learn about the codebase.**
 
-## Rules
+## Mandatory Workflow
 
-1. **On session start:** Run `npx structx status` to check if the graph is initialized.
-   If not initialized, run `npx structx setup .` to bootstrap (init + ingest + analyze).
+### Step 1: Initialize (ALWAYS do this first)
+Run `npx structx status` to check the graph state.
+- If it says "not initialized", run `npx structx setup .`
+- If Functions/Types/Routes counts are 0, run `npx structx setup .`
+- **Do NOT proceed to any code task until StructX is initialized and populated.**
 
-2. **Before answering code questions:** Run `npx structx ask "your question" --repo .`
-   instead of reading raw files. The graph provides function signatures, purposes,
-   relationships, and semantic metadata that raw file reads miss.
+### Step 2: Understand the codebase via StructX (NEVER skip this)
+Before writing ANY code, you MUST query StructX to understand the codebase:
+```
+npx structx overview --repo .
+npx structx ask "what types and interfaces exist?" --repo .
+npx structx ask "what routes/endpoints exist?" --repo .
+npx structx ask "how does <relevant feature> work?" --repo .
+```
+**You are FORBIDDEN from reading .ts source files to understand the codebase architecture,
+discover what functions exist, learn about types, or understand how features work.
+StructX provides all of this. Use it.**
 
-3. **After making code changes:** Run `npx structx ingest .` to update the function graph
-   with your changes.
+### Step 3: Read source files ONLY for editing
+You may ONLY use raw file reads when you have ALREADY queried StructX and now need to
+see the exact code at a specific location to make an edit. The workflow is:
+1. Ask StructX what exists and where it is
+2. StructX tells you the file path and line numbers
+3. THEN read that specific file to make your edit
 
-4. **After ingestion queues new functions:** Run `npx structx analyze . --yes` to enrich
-   newly discovered or changed functions with semantic metadata.
+**Reading source files to "explore" or "understand" the codebase is PROHIBITED.
+That is what StructX is for.**
 
-5. **For impact analysis:** Before modifying a function, run
-   `npx structx ask "what breaks if I change <functionName>" --repo .`
-   to understand downstream effects.
+### Step 4: After making changes
+After editing any TypeScript files:
+```
+npx structx ingest .
+npx structx analyze . --yes
+```
+
+### Step 5: Impact analysis before modifying existing code
+Before changing any existing function, type, or route:
+```
+npx structx ask "what breaks if I change <name>?" --repo .
+```
 
 ## Available Commands
 
-- `npx structx status` — Check if graph is initialized and view stats
-- `npx structx setup .` — One-step bootstrap (init + ingest + analyze)
-- `npx structx ingest .` — Re-parse codebase after changes
-- `npx structx analyze . --yes` — Run semantic analysis on new/changed functions
-- `npx structx ask "question" --repo .` — Query the function graph
+| Command | Description |
+|---------|-------------|
+| `npx structx status` | Check graph state — ALWAYS run first |
+| `npx structx setup .` | Full bootstrap (init + ingest + analyze) |
+| `npx structx overview --repo .` | Full codebase summary in one shot |
+| `npx structx ask "<question>" --repo .` | Query the knowledge graph |
+| `npx structx ingest .` | Re-parse codebase after changes |
+| `npx structx analyze . --yes` | Run semantic analysis on new/changed entities |
 
-## When to Use StructX vs Raw File Reads
+## Rules Summary
 
-- **Use StructX** for: understanding function purposes, finding callers/callees,
-  impact analysis, discovering related functions, understanding code architecture.
-- **Use raw file reads** for: viewing exact implementation details, making edits,
-  reading config files, non-TypeScript files.
+1. **ALWAYS** run `structx status` at session start
+2. **ALWAYS** run `structx setup .` if not initialized
+3. **ALWAYS** use `structx ask` or `structx overview` to understand the codebase
+4. **NEVER** read .ts files to explore/understand architecture — use StructX
+5. **ONLY** read .ts files when you know exactly what file+line to edit (from StructX output)
+6. **ALWAYS** run `structx ingest .` after making code changes
+7. **ALWAYS** run impact analysis before modifying existing functions

package/dist/instructions/cursor.md

@@ -1,39 +1,68 @@
-# StructX — Code Intelligence Graph
+# StructX — Code Intelligence Graph (MANDATORY)
 
 This project uses **StructX**, a graph-powered code intelligence tool for TypeScript.
-StructX maintains a function-level knowledge graph of the codebase that you should use
-instead of reading raw source files when answering code questions.
+StructX maintains a knowledge graph of the codebase including functions, types, routes,
+constants, and file summaries. **You MUST use StructX as your primary source of codebase
+understanding. Do NOT read raw source files to learn about the codebase.**
 
-## Rules
+## Mandatory Workflow
 
-1. **On session start:** Run `npx structx status` to check if the graph is initialized.
-   If not initialized, run `npx structx setup .` to bootstrap (init + ingest + analyze).
+### Step 1: Initialize (ALWAYS do this first)
+Run `npx structx status` to check the graph state.
+- If it says "not initialized", run `npx structx setup .`
+- If Functions/Types/Routes counts are 0, run `npx structx setup .`
+- **Do NOT proceed to any code task until StructX is initialized and populated.**
 
-2. **Before answering code questions:** Run `npx structx ask "your question" --repo .`
-   instead of reading raw files. The graph provides function signatures, purposes,
-   relationships, and semantic metadata that raw file reads miss.
+### Step 2: Understand the codebase via StructX (NEVER skip this)
+Before writing ANY code, you MUST query StructX to understand the codebase:
+```
+npx structx overview --repo .
+npx structx ask "what types and interfaces exist?" --repo .
+npx structx ask "what routes/endpoints exist?" --repo .
+npx structx ask "how does <relevant feature> work?" --repo .
+```
+**You are FORBIDDEN from reading .ts source files to understand the codebase architecture,
+discover what functions exist, learn about types, or understand how features work.
+StructX provides all of this. Use it.**
 
-3. **After making code changes:** Run `npx structx ingest .` to update the function graph
-   with your changes.
+### Step 3: Read source files ONLY for editing
+You may ONLY use raw file reads when you have ALREADY queried StructX and now need to
+see the exact code at a specific location to make an edit. The workflow is:
+1. Ask StructX what exists and where it is
+2. StructX tells you the file path and line numbers
+3. THEN read that specific file to make your edit
 
-4. **After ingestion queues new functions:** Run `npx structx analyze . --yes` to enrich
-   newly discovered or changed functions with semantic metadata.
+**Reading source files to "explore" or "understand" the codebase is PROHIBITED.
+That is what StructX is for.**
 
-5. **For impact analysis:** Before modifying a function, run
-   `npx structx ask "what breaks if I change <functionName>" --repo .`
-   to understand downstream effects.
+### Step 4: After making changes
+After editing any TypeScript files:
+```
+npx structx ingest .
+npx structx analyze . --yes
+```
+
+### Step 5: Impact analysis before modifying existing code
+Before changing any existing function, type, or route:
+```
+npx structx ask "what breaks if I change <name>?" --repo .
+```
 
 ## Available Commands
 
-- `npx structx status` — Check if graph is initialized and view stats
-- `npx structx setup .` — One-step bootstrap (init + ingest + analyze)
+- `npx structx status` — Check graph state — ALWAYS run first
+- `npx structx setup .` — Full bootstrap (init + ingest + analyze)
+- `npx structx overview --repo .` — Full codebase summary in one shot
+- `npx structx ask "<question>" --repo .` — Query the knowledge graph
 - `npx structx ingest .` — Re-parse codebase after changes
-- `npx structx analyze . --yes` — Run semantic analysis on new/changed functions
-- `npx structx ask "question" --repo .` — Query the function graph
+- `npx structx analyze . --yes` — Run semantic analysis on new/changed entities
 
-## When to Use StructX vs Raw File Reads
+## Rules Summary
 
-- **Use StructX** for: understanding function purposes, finding callers/callees,
-  impact analysis, discovering related functions, understanding code architecture.
-- **Use raw file reads** for: viewing exact implementation details, making edits,
-  reading config files, non-TypeScript files.
+1. **ALWAYS** run `structx status` at session start
+2. **ALWAYS** run `structx setup .` if not initialized
+3. **ALWAYS** use `structx ask` or `structx overview` to understand the codebase
+4. **NEVER** read .ts files to explore/understand architecture — use StructX
+5. **ONLY** read .ts files when you know exactly what file+line to edit (from StructX output)
+6. **ALWAYS** run `structx ingest .` after making code changes
+7. **ALWAYS** run impact analysis before modifying existing functions

package/dist/instructions/generic.md

@@ -1,41 +1,70 @@
-# StructX — AI Agent Instructions
+# StructX — Code Intelligence Graph (MANDATORY)
 
 This project uses **StructX**, a graph-powered code intelligence tool for TypeScript.
-StructX maintains a function-level knowledge graph of the codebase that you should use
-instead of reading raw source files when answering code questions.
+StructX maintains a knowledge graph of the codebase including functions, types, routes,
+constants, and file summaries. **You MUST use StructX as your primary source of codebase
+understanding. Do NOT read raw source files to learn about the codebase.**
 
-## Rules
+## Mandatory Workflow
 
-1. **On session start:** Run `npx structx status` to check if the graph is initialized.
-   If not initialized, run `npx structx setup .` to bootstrap (init + ingest + analyze).
+### Step 1: Initialize (ALWAYS do this first)
+Run `npx structx status` to check the graph state.
+- If it says "not initialized", run `npx structx setup .`
+- If Functions/Types/Routes counts are 0, run `npx structx setup .`
+- **Do NOT proceed to any code task until StructX is initialized and populated.**
 
-2. **Before answering code questions:** Run `npx structx ask "your question" --repo .`
-   instead of reading raw files. The graph provides function signatures, purposes,
-   relationships, and semantic metadata that raw file reads miss.
+### Step 2: Understand the codebase via StructX (NEVER skip this)
+Before writing ANY code, you MUST query StructX to understand the codebase:
+```
+npx structx overview --repo .
+npx structx ask "what types and interfaces exist?" --repo .
+npx structx ask "what routes/endpoints exist?" --repo .
+npx structx ask "how does <relevant feature> work?" --repo .
+```
+**You are FORBIDDEN from reading .ts source files to understand the codebase architecture,
+discover what functions exist, learn about types, or understand how features work.
+StructX provides all of this. Use it.**
 
-3. **After making code changes:** Run `npx structx ingest .` to update the function graph
-   with your changes.
+### Step 3: Read source files ONLY for editing
+You may ONLY use raw file reads when you have ALREADY queried StructX and now need to
+see the exact code at a specific location to make an edit. The workflow is:
+1. Ask StructX what exists and where it is
+2. StructX tells you the file path and line numbers
+3. THEN read that specific file to make your edit
 
-4. **After ingestion queues new functions:** Run `npx structx analyze . --yes` to enrich
-   newly discovered or changed functions with semantic metadata.
+**Reading source files to "explore" or "understand" the codebase is PROHIBITED.
+That is what StructX is for.**
 
-5. **For impact analysis:** Before modifying a function, run
-   `npx structx ask "what breaks if I change <functionName>" --repo .`
-   to understand downstream effects.
+### Step 4: After making changes
+After editing any TypeScript files:
+```
+npx structx ingest .
+npx structx analyze . --yes
+```
+
+### Step 5: Impact analysis before modifying existing code
+Before changing any existing function, type, or route:
+```
+npx structx ask "what breaks if I change <name>?" --repo .
+```
 
 ## Available Commands
 
 | Command | Description |
 |---------|-------------|
-| `npx structx status` | Check if graph is initialized and view stats |
-| `npx structx setup .` | One-step bootstrap (init + ingest + analyze) |
+| `npx structx status` | Check graph state — ALWAYS run first |
+| `npx structx setup .` | Full bootstrap (init + ingest + analyze) |
+| `npx structx overview --repo .` | Full codebase summary in one shot |
+| `npx structx ask "<question>" --repo .` | Query the knowledge graph |
 | `npx structx ingest .` | Re-parse codebase after changes |
-| `npx structx analyze . --yes` | Run semantic analysis on new/changed functions |
-| `npx structx ask "question" --repo .` | Query the function graph |
+| `npx structx analyze . --yes` | Run semantic analysis on new/changed entities |
 
-## When to Use StructX vs Raw File Reads
+## Rules Summary
 
-- **Use StructX** for: understanding function purposes, finding callers/callees,
-  impact analysis, discovering related functions, understanding code architecture.
-- **Use raw file reads** for: viewing exact implementation details, making edits,
-  reading config files, non-TypeScript files.
+1. **ALWAYS** run `structx status` at session start
+2. **ALWAYS** run `structx setup .` if not initialized
+3. **ALWAYS** use `structx ask` or `structx overview` to understand the codebase
+4. **NEVER** read .ts files to explore/understand architecture — use StructX
+5. **ONLY** read .ts files when you know exactly what file+line to edit (from StructX output)
+6. **ALWAYS** run `structx ingest .` after making code changes
+7. **ALWAYS** run impact analysis before modifying existing functions

package/dist/query/answerer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"answerer.d.ts","sourceRoot":"","sources":["../../src/query/answerer.ts"],"names":[],"mappings":"AAGA,MAAM,WAAW,YAAY;IAC3B,MAAM,EAAE,MAAM,CAAC;IACf,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,IAAI,EAAE,MAAM,CAAC;IACb,cAAc,EAAE,MAAM,CAAC;CACxB;AAWD,wBAAsB,cAAc,CAClC,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,MAAM,EACb,MAAM,EAAE,MAAM,GACb,OAAO,CAAC,YAAY,CAAC,CAiCvB"}
+{"version":3,"file":"answerer.d.ts","sourceRoot":"","sources":["../../src/query/answerer.ts"],"names":[],"mappings":"AAGA,MAAM,WAAW,YAAY;IAC3B,MAAM,EAAE,MAAM,CAAC;IACf,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,IAAI,EAAE,MAAM,CAAC;IACb,cAAc,EAAE,MAAM,CAAC;CACxB;AAeD,wBAAsB,cAAc,CAClC,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,MAAM,EACb,MAAM,EAAE,MAAM,GACb,OAAO,CAAC,YAAY,CAAC,CAiCvB"}

package/dist/query/answerer.js

@@ -8,12 +8,16 @@ const sdk_1 = __importDefault(require("@anthropic-ai/sdk"));
 const tokens_1 = require("../utils/tokens");
 const SYSTEM_PROMPT = `You are a code intelligence assistant. You answer developer questions about a TypeScript codebase using structured context retrieved from a code graph database.
 
+The context may include functions, types (interfaces/type aliases/enums), HTTP routes/endpoints, file summaries, and constants extracted from the codebase.
+
 Rules:
 - Answer based ONLY on the provided context
 - Be concise and specific
-- Reference function names and file locations when relevant
+- Reference function names, type names, route paths, and file locations when relevant
 - If the context doesn't contain enough information, say so clearly
-- Do not make up information not present in the context`;
+- Do not make up information not present in the context
+- When describing routes, include the HTTP method, path, and handler details
+- When describing types, include the full definition when available`;
 async function generateAnswer(question, context, model, apiKey) {
     const client = new sdk_1.default({ apiKey });
     const startTime = Date.now();

package/dist/query/answerer.js.map

@@ -1 +1 @@
-{"version":3,"file":"answerer.js","sourceRoot":"","sources":["../../src/query/answerer.ts"],"names":[],"mappings":";;;;;AAoBA,wCAsCC;AA1DD,4DAA0C;AAC1C,4CAA+C;AAU/C,MAAM,aAAa,GAAG;;;;;;;wDAOkC,CAAC;AAElD,KAAK,UAAU,cAAc,CAClC,QAAgB,EAChB,OAAe,EACf,KAAa,EACb,MAAc;IAEd,MAAM,MAAM,GAAG,IAAI,aAAS,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC;IACzC,MAAM,SAAS,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;IAE7B,MAAM,QAAQ,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC;QAC5C,KAAK;QACL,UAAU,EAAE,IAAI;QAChB,MAAM,EAAE,aAAa;QACrB,QAAQ,EAAE;YACR;gBACE,IAAI,EAAE,MAAM;gBACZ,OAAO,EAAE,GAAG,OAAO,iBAAiB,QAAQ,EAAE;aAC/C;SACF;KACF,CAAC,CAAC;IAEH,MAAM,cAAc,GAAG,IAAI,CAAC,GAAG,EAAE,GAAG,SAAS,CAAC;IAE9C,MAAM,MAAM,GAAG,QAAQ,CAAC,OAAO;SAC5B,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC;SACtC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAE,KAAa,CAAC,IAAI,CAAC;SACjC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEZ,MAAM,WAAW,GAAG,QAAQ,CAAC,KAAK,EAAE,YAAY,IAAI,CAAC,CAAC;IACtD,MAAM,YAAY,GAAG,QAAQ,CAAC,KAAK,EAAE,aAAa,IAAI,CAAC,CAAC;IAExD,OAAO;QACL,MAAM;QACN,WAAW;QACX,YAAY;QACZ,IAAI,EAAE,IAAA,qBAAY,EAAC,KAAK,EAAE,WAAW,EAAE,YAAY,CAAC;QACpD,cAAc;KACf,CAAC;AACJ,CAAC"}
+{"version":3,"file":"answerer.js","sourceRoot":"","sources":["../../src/query/answerer.ts"],"names":[],"mappings":";;;;;AAwBA,wCAsCC;AA9DD,4DAA0C;AAC1C,4CAA+C;AAU/C,MAAM,aAAa,GAAG;;;;;;;;;;;oEAW8C,CAAC;AAE9D,KAAK,UAAU,cAAc,CAClC,QAAgB,EAChB,OAAe,EACf,KAAa,EACb,MAAc;IAEd,MAAM,MAAM,GAAG,IAAI,aAAS,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC;IACzC,MAAM,SAAS,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;IAE7B,MAAM,QAAQ,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC;QAC5C,KAAK;QACL,UAAU,EAAE,IAAI;QAChB,MAAM,EAAE,aAAa;QACrB,QAAQ,EAAE;YACR;gBACE,IAAI,EAAE,MAAM;gBACZ,OAAO,EAAE,GAAG,OAAO,iBAAiB,QAAQ,EAAE;aAC/C;SACF;KACF,CAAC,CAAC;IAEH,MAAM,cAAc,GAAG,IAAI,CAAC,GAAG,EAAE,GAAG,SAAS,CAAC;IAE9C,MAAM,MAAM,GAAG,QAAQ,CAAC,OAAO;SAC5B,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC;SACtC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAE,KAAa,CAAC,IAAI,CAAC;SACjC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEZ,MAAM,WAAW,GAAG,QAAQ,CAAC,KAAK,EAAE,YAAY,IAAI,CAAC,CAAC;IACtD,MAAM,YAAY,GAAG,QAAQ,CAAC,KAAK,EAAE,aAAa,IAAI,CAAC,CAAC;IAExD,OAAO;QACL,MAAM;QACN,WAAW;QACX,YAAY;QACZ,IAAI,EAAE,IAAA,qBAAY,EAAC,KAAK,EAAE,WAAW,EAAE,YAAY,CAAC;QACpD,cAAc;KACf,CAAC;AACJ,CAAC"}

package/dist/query/classifier.d.ts

@@ -1,10 +1,15 @@
-export type QueryStrategy = 'direct' | 'relationship' | 'semantic' | 'domain' | 'impact';
+export type QueryStrategy = 'direct' | 'relationship' | 'semantic' | 'domain' | 'impact' | 'route' | 'type' | 'file' | 'list' | 'pattern';
 export interface ClassificationResult {
     strategy: QueryStrategy;
     functionName: string | null;
     keywords: string[];
     domain: string | null;
     direction: 'callers' | 'callees' | null;
+    typeName: string | null;
+    filePath: string | null;
+    routePath: string | null;
+    routeMethod: string | null;
+    listEntity: string | null;
 }
 export declare function classifyQuestion(question: string, model: string, apiKey: string): Promise<ClassificationResult>;
 //# sourceMappingURL=classifier.d.ts.map

package/dist/query/classifier.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"classifier.d.ts","sourceRoot":"","sources":["../../src/query/classifier.ts"],"names":[],"mappings":"AAEA,MAAM,MAAM,aAAa,GAAG,QAAQ,GAAG,cAAc,GAAG,UAAU,GAAG,QAAQ,GAAG,QAAQ,CAAC;AAEzF,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,aAAa,CAAC;IACxB,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,SAAS,EAAE,SAAS,GAAG,SAAS,GAAG,IAAI,CAAC;CACzC;AAoBD,wBAAsB,gBAAgB,CACpC,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,MAAM,EAAE,MAAM,GACb,OAAO,CAAC,oBAAoB,CAAC,CAoC/B"}
+{"version":3,"file":"classifier.d.ts","sourceRoot":"","sources":["../../src/query/classifier.ts"],"names":[],"mappings":"AAEA,MAAM,MAAM,aAAa,GAAG,QAAQ,GAAG,cAAc,GAAG,UAAU,GAAG,QAAQ,GAAG,QAAQ,GAAG,OAAO,GAAG,MAAM,GAAG,MAAM,GAAG,MAAM,GAAG,SAAS,CAAC;AAE1I,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,aAAa,CAAC;IACxB,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,SAAS,EAAE,SAAS,GAAG,SAAS,GAAG,IAAI,CAAC;IACxC,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACxB,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACxB,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IACzB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,UAAU,EAAE,MAAM,GAAG,IAAI,CAAC;CAC3B;AA8BD,wBAAsB,gBAAgB,CACpC,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,MAAM,EAAE,MAAM,GACb,OAAO,CAAC,oBAAoB,CAAC,CA8C/B"}

package/dist/query/classifier.js

@@ -13,14 +13,24 @@ Categories:
 3. "semantic" - Question asks about a concept, topic, or behavior (e.g., "How is authentication handled?")
 4. "domain" - Question asks about a category of functions (e.g., "Show all database operations")
 5. "impact" - Question asks about what would be affected by changes (e.g., "What breaks if I change validateEmail?")
+6. "route" - Question asks about HTTP routes/endpoints (e.g., "What does the /api/users endpoint do?", "What routes exist?")
+7. "type" - Question asks about a type, interface, or enum (e.g., "What is the User type?", "Show me the Request interface")
+8. "file" - Question asks about a specific file or its contents (e.g., "What does auth.ts do?", "What's in the config file?")
+9. "list" - Question asks to enumerate/list entities (e.g., "List all routes", "What functions exist?", "Show all types")
+10. "pattern" - Question asks about patterns or cross-cutting concerns spanning multiple entities (e.g., "How does the login flow work?", "How are errors handled?")
 
 Respond ONLY with JSON, no markdown:
 {
-  "strategy": "direct|relationship|semantic|domain|impact",
+  "strategy": "direct|relationship|semantic|domain|impact|route|type|file|list|pattern",
   "function_name": "extracted function name or null",
   "keywords": ["relevant", "search", "terms"],
   "domain": "authentication|database|validation|routing|middleware|utility|logging|session|crypto|ui|api|config|testing|other or null",
-  "direction": "callers|callees|null"
+  "direction": "callers|callees|null",
+  "type_name": "extracted type/interface/enum name or null",
+  "file_path": "extracted file path or null",
+  "route_path": "extracted route path like /api/users or null",
+  "route_method": "GET|POST|PUT|DELETE|PATCH or null",
+  "list_entity": "functions|routes|types|files|constants or null"
 }`;
 async function classifyQuestion(question, model, apiKey) {
     const client = new sdk_1.default({ apiKey });
@@ -44,6 +54,11 @@ async function classifyQuestion(question, model, apiKey) {
             keywords: parsed.keywords || [],
             domain: parsed.domain || null,
             direction: parsed.direction || null,
+            typeName: parsed.type_name || null,
+            filePath: parsed.file_path || null,
+            routePath: parsed.route_path || null,
+            routeMethod: parsed.route_method || null,
+            listEntity: parsed.list_entity || null,
         };
     }
     catch {
@@ -54,6 +69,11 @@ async function classifyQuestion(question, model, apiKey) {
             keywords: question.split(/\s+/).filter(w => w.length > 3),
             domain: null,
             direction: null,
+            typeName: null,
+            filePath: null,
+            routePath: null,
+            routeMethod: null,
+            listEntity: null,
         };
     }
 }

package/dist/query/classifier.js.map

@@ -1 +1 @@
-{"version":3,"file":"classifier.js","sourceRoot":"","sources":["../../src/query/classifier.ts"],"names":[],"mappings":";;;;;AA8BA,4CAwCC;AAtED,4DAA0C;AAY1C,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;EAgB5B,CAAC;AAEI,KAAK,UAAU,gBAAgB,CACpC,QAAgB,EAChB,KAAa,EACb,MAAc;IAEd,MAAM,MAAM,GAAG,IAAI,aAAS,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC;IAEzC,MAAM,QAAQ,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC;QAC5C,KAAK;QACL,UAAU,EAAE,GAAG;QACf,QAAQ,EAAE;YACR,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,GAAG,qBAAqB,kBAAkB,QAAQ,GAAG,EAAE;SACjF;KACF,CAAC,CAAC;IAEH,MAAM,IAAI,GAAG,QAAQ,CAAC,OAAO;SAC1B,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC;SACtC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAE,KAAa,CAAC,IAAI,CAAC;SACjC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEZ,IAAI,CAAC;QACH,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,eAAe,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC;QACjF,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;QACnC,OAAO;YACL,QAAQ,EAAE,MAAM,CAAC,QAAQ,IAAI,UAAU;YACvC,YAAY,EAAE,MAAM,CAAC,aAAa,IAAI,IAAI;YAC1C,QAAQ,EAAE,MAAM,CAAC,QAAQ,IAAI,EAAE;YAC/B,MAAM,EAAE,MAAM,CAAC,MAAM,IAAI,IAAI;YAC7B,SAAS,EAAE,MAAM,CAAC,SAAS,IAAI,IAAI;SACpC,CAAC;IACJ,CAAC;IAAC,MAAM,CAAC;QACP,8BAA8B;QAC9B,OAAO;YACL,QAAQ,EAAE,UAAU;YACpB,YAAY,EAAE,IAAI;YAClB,QAAQ,EAAE,QAAQ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC;YACzD,MAAM,EAAE,IAAI;YACZ,SAAS,EAAE,IAAI;SAChB,CAAC;IACJ,CAAC;AACH,CAAC"}
+{"version":3,"file":"classifier.js","sourceRoot":"","sources":["../../src/query/classifier.ts"],"names":[],"mappings":";;;;;AA6CA,4CAkDC;AA/FD,4DAA0C;AAiB1C,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;EA0B5B,CAAC;AAEI,KAAK,UAAU,gBAAgB,CACpC,QAAgB,EAChB,KAAa,EACb,MAAc;IAEd,MAAM,MAAM,GAAG,IAAI,aAAS,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC;IAEzC,MAAM,QAAQ,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC;QAC5C,KAAK;QACL,UAAU,EAAE,GAAG;QACf,QAAQ,EAAE;YACR,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,GAAG,qBAAqB,kBAAkB,QAAQ,GAAG,EAAE;SACjF;KACF,CAAC,CAAC;IAEH,MAAM,IAAI,GAAG,QAAQ,CAAC,OAAO;SAC1B,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC;SACtC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAE,KAAa,CAAC,IAAI,CAAC;SACjC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEZ,IAAI,CAAC;QACH,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,eAAe,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC;QACjF,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;QACnC,OAAO;YACL,QAAQ,EAAE,MAAM,CAAC,QAAQ,IAAI,UAAU;YACvC,YAAY,EAAE,MAAM,CAAC,aAAa,IAAI,IAAI;YAC1C,QAAQ,EAAE,MAAM,CAAC,QAAQ,IAAI,EAAE;YAC/B,MAAM,EAAE,MAAM,CAAC,MAAM,IAAI,IAAI;YAC7B,SAAS,EAAE,MAAM,CAAC,SAAS,IAAI,IAAI;YACnC,QAAQ,EAAE,MAAM,CAAC,SAAS,IAAI,IAAI;YAClC,QAAQ,EAAE,MAAM,CAAC,SAAS,IAAI,IAAI;YAClC,SAAS,EAAE,MAAM,CAAC,UAAU,IAAI,IAAI;YACpC,WAAW,EAAE,MAAM,CAAC,YAAY,IAAI,IAAI;YACxC,UAAU,EAAE,MAAM,CAAC,WAAW,IAAI,IAAI;SACvC,CAAC;IACJ,CAAC;IAAC,MAAM,CAAC;QACP,8BAA8B;QAC9B,OAAO;YACL,QAAQ,EAAE,UAAU;YACpB,YAAY,EAAE,IAAI;YAClB,QAAQ,EAAE,QAAQ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC;YACzD,MAAM,EAAE,IAAI;YACZ,SAAS,EAAE,IAAI;YACf,QAAQ,EAAE,IAAI;YACd,QAAQ,EAAE,IAAI;YACd,SAAS,EAAE,IAAI;YACf,WAAW,EAAE,IAAI;YACjB,UAAU,EAAE,IAAI;SACjB,CAAC;IACJ,CAAC;AACH,CAAC"}

package/dist/query/context-builder.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"context-builder.d.ts","sourceRoot":"","sources":["../../src/query/context-builder.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAqB,MAAM,aAAa,CAAC;AAGvE,wBAAgB,YAAY,CAAC,SAAS,EAAE,gBAAgB,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CA+BlF"}
+{"version":3,"file":"context-builder.d.ts","sourceRoot":"","sources":["../../src/query/context-builder.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAsF,MAAM,aAAa,CAAC;AAGxI,wBAAgB,YAAY,CAAC,SAAS,EAAE,gBAAgB,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CA8DlF"}