@popoverai/dotrequirements 0.23.0 → 0.24.1

package/dist/mcp/convexClient.d.ts

@@ -15,44 +15,5 @@ interface ConvexConfig {
  * Returns null if credentials are not configured.
  */
 export declare function loadConvexConfig(cwd?: string): ConvexConfig | null;
-/**
- * Query Convex for requirement coverage
- */
-export declare function getRequirementCoverage(requirementKey: string, projectId: string, projectSecret: string, convexUrl: string): Promise<{
-    requirementKey: string;
-    lastTestedAt: number | null;
-    branch: string | null;
-    testFile: string | null;
-    testLine: number | null;
-    allBranches: Array<{
-        branch: string;
-        lastTestedAt: number;
-        testFile?: string;
-        testLine?: number;
-    }>;
-}>;
-/**
- * Query Convex for project coverage summary
- */
-export declare function getProjectCoverage(projectId: string, projectSecret: string, convexUrl: string, options?: {
-    branch?: string;
-    sinceTimestamp?: number;
-}): Promise<{
-    tested: Array<{
-        requirementKey: string;
-        lastTestedAt: number;
-        branch: string;
-        testFile?: string;
-        testLine?: number;
-    }>;
-    untested: string[];
-}>;
-/**
- * PROJ-CONTEXT-7: Query Convex for project context (AI style guidelines)
- */
-export declare function getProjectContext(projectId: string, projectSecret: string, convexUrl: string): Promise<{
-    projectContext: string | null;
-    requirementsStyleContext: string | null;
-} | null>;
 export {};
 //# sourceMappingURL=convexClient.d.ts.map

package/dist/mcp/convexClient.js

@@ -1,8 +1,8 @@
-import { getProjectCredentials } from '../utils/project-settings.js';
+import { getProjectCredentials } from "../utils/project-settings.js";
 /**
  * Production Convex deployment URL
  */
-export const CONVEX_URL = 'https://data.dotrequirements.io';
+export const CONVEX_URL = "https://data.dotrequirements.io";
 /**
  * Load Convex configuration from project settings.
  * Returns null if credentials are not configured.
@@ -21,109 +21,4 @@ export function loadConvexConfig(cwd = process.cwd()) {
         return null;
     }
 }
-/**
- * Query Convex for requirement coverage
- */
-export async function getRequirementCoverage(requirementKey, projectId, projectSecret, convexUrl) {
-    const response = await fetch(`${convexUrl}/api/query`, {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-            path: 'testCoverage/queries:getRequirementCoverage',
-            args: {
-                projectAuth: {
-                    projectSlug: projectId,
-                    projectSecret,
-                },
-                target: {
-                    type: 'project',
-                    slug: projectId,
-                },
-                requirementKey,
-            },
-            format: 'json',
-        }),
-    });
-    if (!response.ok) {
-        throw new Error(`Failed to query coverage: ${response.statusText}`);
-    }
-    const json = await response.json();
-    if (json.status === 'error') {
-        throw new Error(`Convex query failed: ${json.errorMessage}`);
-    }
-    return json.value;
-}
-/**
- * Query Convex for project coverage summary
- */
-export async function getProjectCoverage(projectId, projectSecret, convexUrl, options) {
-    const response = await fetch(`${convexUrl}/api/query`, {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-            path: 'testCoverage/queries:getProjectCoverage',
-            args: {
-                projectAuth: {
-                    projectSlug: projectId,
-                    projectSecret,
-                },
-                target: {
-                    type: 'project',
-                    slug: projectId,
-                },
-                branch: options?.branch,
-                sinceTimestamp: options?.sinceTimestamp,
-            },
-            format: 'json',
-        }),
-    });
-    if (!response.ok) {
-        throw new Error(`Failed to query coverage: ${response.statusText}`);
-    }
-    const json = await response.json();
-    if (json.status === 'error') {
-        throw new Error(`Convex query failed: ${json.errorMessage}`);
-    }
-    return json.value;
-}
-/**
- * PROJ-CONTEXT-7: Query Convex for project context (AI style guidelines)
- */
-export async function getProjectContext(projectId, projectSecret, convexUrl) {
-    try {
-        const response = await fetch(`${convexUrl}/api/query`, {
-            method: 'POST',
-            headers: { 'Content-Type': 'application/json' },
-            body: JSON.stringify({
-                path: 'projects/queries:get',
-                args: {
-                    projectAuth: {
-                        projectSlug: projectId,
-                        projectSecret,
-                    },
-                    target: {
-                        type: 'project',
-                        slug: projectId,
-                    },
-                },
-                format: 'json',
-            }),
-        });
-        if (!response.ok) {
-            return null;
-        }
-        const json = await response.json();
-        if (json.status === 'error' || !json.value) {
-            return null;
-        }
-        return {
-            projectContext: json.value.projectContext ?? null,
-            requirementsStyleContext: json.value.requirementsStyleContext ?? null,
-        };
-    }
-    catch {
-        // Non-fatal: return null if query fails
-        return null;
-    }
-}
 //# sourceMappingURL=convexClient.js.map

package/dist/mcp/handlers/authoring.d.ts

@@ -5,7 +5,7 @@
  * - create_requirement_document: Generate requirements template with format guidance
  * - validate_requirements: Validate requirements file syntax offline
  */
-import type { HandlerContext, ToolResponse } from './types.js';
+import type { HandlerContext, ToolResponse } from "./types.js";
 /**
  * Arguments for create_requirement_document tool
  */

package/dist/mcp/handlers/authoring.js

@@ -5,11 +5,13 @@
  * - create_requirement_document: Generate requirements template with format guidance
  * - validate_requirements: Validate requirements file syntax offline
  */
-import { textResponse, errorResponse } from './types.js';
-import { existsSync } from 'fs';
-import { resolve } from 'path';
-import { parseRequirementsFromFile, validateForPush } from '../../schema/index.js';
-import { CONVEX_URL, getProjectContext, } from '../convexClient.js';
+import { existsSync } from "node:fs";
+import { resolve } from "node:path";
+import { getProjectContext } from "../../requirements/cloud-ai.js";
+import { generateStyleGuide, readLocalStyleGuide, } from "../../requirements/style-guide.js";
+import { parseRequirementsFromFile, validateForPush, } from "../../schema/index.js";
+import { CONVEX_URL } from "../convexClient.js";
+import { errorResponse, textResponse } from "./types.js";
 /**
  * Handler for create_requirement_document tool
  *
@@ -20,245 +22,32 @@ import { CONVEX_URL, getProjectContext, } from '../convexClient.js';
  * - MCP-AUTHOR-1.3: When cloud credentials are unavailable, the template works without the custom context
  */
 export async function handleCreateRequirementDocument(args, context) {
-    const { filePath = '.requirements/example.requirements.md' } = args;
-    // Discover existing label and key patterns in the codebase
-    // Try to get requirements, but don't fail if no project is configured
+    const { filePath = ".requirements/example.requirements.md" } = args;
+    // MCP-AUTHOR-1.3: Try to get requirements, but don't fail if no project is configured
     let requirements = [];
     try {
         requirements = await context.getRequirements();
     }
     catch {
-        // MCP-AUTHOR-1.3: No project configured - that's okay, we'll just not have discovered patterns
-    }
-    const labels = new Set();
-    const keyPrefixes = new Set();
-    for (const req of requirements) {
-        // Collect labels (empty string means unlabeled, so skip those)
-        if (req.label && req.label.trim()) {
-            labels.add(req.label);
-        }
-        // Collect requirement key prefixes (root IDs only)
-        // Extract prefix from keys like "AUTH-1" -> "AUTH", "LOGIN-FLOW-2" -> "LOGIN-FLOW"
-        if (req.path.length === 0 && req.id) {
-            const lastDashIndex = req.id.lastIndexOf('-');
-            if (lastDashIndex > 0) {
-                const prefix = req.id.substring(0, lastDashIndex);
-                keyPrefixes.add(prefix);
-            }
-        }
-    }
-    const discoveredLabels = Array.from(labels).sort();
-    const discoveredPrefixes = Array.from(keyPrefixes).sort();
-    let labelGuidance = '';
-    let keyGuidance = '';
-    // Generate label guidance
-    if (discoveredLabels.length > 0) {
-        const labelList = discoveredLabels.slice(0, 10).map(l => `"${l}"`).join(', ');
-        const more = discoveredLabels.length > 10 ? ` (and ${discoveredLabels.length - 10} more)` : '';
-        labelGuidance = `**Existing labels in this codebase:** ${labelList}${more}
-
-**Use these existing labels** to maintain consistency. If you're unsure which labels to use for a new requirement, ask the user.`;
-    }
-    else {
-        labelGuidance = `**No existing requirements found in this codebase.**
-
-**Default to unlabeled requirements** (\`0. → content\`). If the user wants labels, ask them which format they prefer. Do not choose an opinionated framework like Given/When/Then without explicit user consent.`;
-    }
-    // Generate key guidance
-    if (discoveredPrefixes.length > 0) {
-        const prefixList = discoveredPrefixes.map(p => `"${p}"`).join(', ');
-        keyGuidance = `**Existing requirement key prefixes in this codebase:** ${prefixList}
-
-**Match the existing pattern** when creating new requirement keys. Use the same domain prefixes and sequential numbering style.`;
-    }
-    else {
-        keyGuidance = `**No existing requirements found in this codebase.**
-
-**Use concise domain prefixes** like \`AUTH-1\`, \`LOGIN-1\`, etc. Start numbering at 1 and increment sequentially.`;
+        // No project configured — discovered patterns will be empty
     }
     // MCP-AUTHOR-1.2: Try to fetch user-provided style context from cloud
-    let userStyleGuidance = '';
+    let customStyleGuidance = null;
     try {
         const project = await context.getProjectFromDiscovery();
         const contextData = await getProjectContext(project.projectId, project.projectSecret, CONVEX_URL);
-        if (contextData?.requirementsStyleContext?.trim()) {
-            userStyleGuidance = `
-
-## User-Provided Style Guidelines
-
-The following style guidelines were provided by the project owner. When these conflict with the defaults above, prioritize the user's guidelines.
-
-${contextData.requirementsStyleContext.trim()}`;
-        }
+        customStyleGuidance = contextData?.requirementsStyleContext ?? null;
     }
     catch {
         // MCP-AUTHOR-1.3: No credentials or cloud unavailable - continue without user context
     }
-    // MCP-AUTHOR-1.0: Template with format guidance and code block examples
-    // MCP-AUTHOR-1.1: Template includes style principles (concrete examples, concise prose, testable conditions)
-    const template = `---
-document:
-  title: "Example Requirements"
----
-
-# Example Requirements
-
-This template demonstrates the dotrequirements Markdown format and style guidelines.
-
-## Syntax Overview
-
-**File naming:** Use \`*.requirements.md\` pattern (colocated: \`auth.requirements.md\` or centralized: \`.requirements/auth.requirements.md\`)
-
-**Block format:**
-\`\`\`dotrequirements
-KEY: Root requirement content
-  0. → First criterion (unlabeled)
-  1. Label → Second criterion (with label)
-    1.0. → Nested criterion (unlabeled)
-\`\`\`
-
-- First line: \`KEY: content\` (requirement key and description)
-- Criteria: \`position. Label → content\` or \`position. → content\` (unlabeled)
-- Position: \`0\`, \`1\`, \`2\` (top-level) or \`0.0\`, \`1.0\` (nested) - defines hierarchy
-- Delimiter: \`→\` or \`->\` separates optional label from content
-
-## Requirement Keys: Concise and Sequential
-
-${keyGuidance}
-
-**Key format:** \`DOMAIN-FEATURE-N\` where N is sequential (1, 2, 3...)
-
-**Best practices:**
-1. **Concise domains** - Use short, clear prefixes
-   - ✅ \`AUTHZ-1\` (authorization)
-   - ✅ \`AUTH-1\` (authentication)
-   - ❌ \`AUTHORIZATION-1\` (too verbose)
-   - ❌ \`REQ-IDENTITY-ACCESS-AUTHZ-1\` (too nested)
-
-2. **Sequential, 1-indexed numbering** - Start at 1, no padding
-   - ✅ \`LOGIN-1\`, \`LOGIN-2\`, \`LOGIN-3\`
-   - ❌ \`LOGIN-0\` (don't use 0-indexing for requirement IDs)
-   - ❌ \`LOGIN-001\` (no zero-padding)
-
-3. **Unique across project** - Each key must be unique in the entire project
-
-4. **Match existing patterns** - Check existing requirements first and follow their convention
-
-## Labels: Match Your Codebase or Ask the User
-
-${labelGuidance}
-
-## Style Principles for Requirements
-
-**1. Use Concrete Examples**: Replace vague language with specific, testable conditions.
-- ❌ "users can log in" or "works properly"
-- ✅ "When a registered user provides valid credentials, they are authenticated"
-
-**2. Write Natural, Concise Prose**: Avoid terseness and verbosity. Use declarative style (not "should").
-- ❌ "registered user with valid credentials is authenticated" (too terse)
-- ❌ "A registered user, whose account was created on Tuesday and whose life story is as follows..." (too verbose)
-- ✅ "When a registered user provides valid credentials, they are authenticated"
-
-**3. Keep Arrange/Act/Assert in Mind**: Well-written requirements describe preconditions, trigger, and result.
-- ✅ "When [preconditions:] a registered user [trigger:] provides valid credentials, [result:] they are authenticated"
-
-**4. Be Framework Neutral**: Don't prescribe Given/When/Then vs AC vs other formats - focus on content quality.
-
-**5. Use Named Personas**: Establish personas in parent requirements, reuse in children.
-- ✅ Parent: "A registered user, Jamie, can log in normally" → Child: "When Jamie provides valid credentials, they are authenticated"
-
-**6. Use User-Centric Language**: Describe user experience, not technical internals.
-- ❌ "they are redirected to app.dotrequirements.io/redirect/dashboard"
-- ✅ "they are automatically brought to the dashboard"
-
-**7. Single Action Per Requirement**: Don't chain multiple actions with "and then".
-- ❌ "When Robin provides credentials, requests an OTP, then provides the OTP..."
-- ✅ Break into separate requirements for each action
-
-**8. Each Requirement Should Be Independent**: Requirements within a block should be independently testable. If they share preconditions or form a sequence, either nest them or restate context.
-- ❌ "0. → When Jordan submits signup, an account is created" / "1. → Welcome email is sent" / "2. → Dashboard appears"
-- ✅ Option A: Restate context - "1. → When Jordan submits signup, a welcome email is sent"
-- ✅ Option B: Use nesting - "0. When → Jordan submits signup" / "  0.0. Then → an account is created"
-- Test: Can you understand what's being tested by reading just one requirement, or do you need to read its siblings?
-
-**9. Focus on Behavior, Not Design**: Describe what happens, not UI specifics.
-- ❌ "enters valid credentials into two single-line input fields and presses a green button"
-- ✅ "provides valid credentials"
-
-**10. Focus on Outcomes, Not Implementation**: User perspective, even for technical requirements.
-- ❌ "When the app requests that Twilio send Casey an OTP from /email/POST endpoint..."
-- ✅ "When Casey requests an email OTP..."
-- Note: Even technical requirements can be user-centric: "95 percent of users experience under 1 second of delay"
-
-**11. Decompose Large Requirements**: If it can't be validated with a single test, break it down.
-${userStyleGuidance}
-
-## Example Requirements
-
-**Unlabeled (recommended default):**
-\`\`\`dotrequirements
-AUTH-LOGIN-1: A registered user, Jamie, can log in to their account
-  0. → When Jamie provides their registered email and correct password, they are authenticated and brought to their dashboard
-  1. → When Jamie provides an incorrect password, they see an error message and remain on the login page
-  2. → When Jamie's account has been deactivated, they see a message explaining their account status
-\`\`\`
-
-**With labels (example only - DO NOT use opinionated formats like Given/When/Then without asking the user first):**
-\`\`\`dotrequirements
-PAYMENT-REFUND-1: A customer, Alex, receives a refund after returning an item
-  0. Given → Alex purchased a laptop from the store 10 days ago
-  1. Given → Alex initiates a return through their order history
-  2. When → Alex's returned laptop is received and inspected at the warehouse
-  3. Then → Alex receives a refund to their original payment method within 5 business days
-  4. Then → Alex receives an email confirmation with the refund amount and expected timeline
-\`\`\`
-
-## Referencing Requirements in Tests
-
-**Use \`requirement()\` as the test description** - it returns a string:
-
-\`\`\`typescript
-import { describe, it, expect } from 'vitest';
-import { requirement } from '@popoverai/dotrequirements/test';
-
-describe(requirement('AUTH-LOGIN-1'), () => {
-  describe(requirement('AUTH-LOGIN-1.given'), () => {
-    // Arrange: Create Jamie's account
-  });
-
-  describe(requirement('AUTH-LOGIN-1.when'), () => {
-    // Act: Submit login with valid credentials
-
-    it(requirement('AUTH-LOGIN-1.then'), () => {
-      // Assert: Jamie is authenticated
-    });
-  });
-});
-\`\`\`
-
-**Test Style Principles:**
-
-**1. Use requirement() AS the description**: Don't put requirement() inside test body or in comments.
-- ✅ \`test(requirement('AUTH-LOGIN-1'), () => { /* test code */ })\`
-- ✅ \`it(requirement('LOGIN-1.then'), () => { /* assert */ })\`
-- ❌ \`test("user can log in", () => { requirement('AUTH-LOGIN-1'); /* test code */ })\`
-- ❌ \`// LOGIN-1: User can log in\` (comment instead of using requirement() as description)
-
-**2. Comments describe the TEST, not the requirement**: Don't copy requirement text verbatim.
-- ✅ \`describe(requirement('REQ-1.0'), () => { // registered user, valid credentials\`
-- ❌ \`describe(requirement('REQ-1.0'), () => { // 0. When a registered user provides valid credentials, they are authenticated\` (verbatim copy is a red flag)
-- Note: Comments should reflect what the test actually does, not just repeat what the requirement says
-
-**3. Structure tests to match requirements**: Nest describe/it blocks for structured requirements.
-- ✅ For structured requirements: \`describe(requirement('LOGIN-1.given'))\` nested with \`describe(requirement('LOGIN-1.when'))\` and \`it(requirement('LOGIN-1.then'))\`
-- ✅ For simple requirements: \`test(requirement('AUTH-LOGIN-1'), () => { /* arrange, act, assert all in one */ })\`
-
-**Path formats:**
-- \`requirement('AUTH-LOGIN-1')\` - root requirement
-- \`requirement('AUTH-LOGIN-1.0')\` - by numeric position
-- \`requirement('AUTH-LOGIN-1.given')\` - by label (case-insensitive)
-- \`requirement('AUTH-LOGIN-1.given#1')\` - disambiguate duplicate labels`;
-    return textResponse(`# Requirements File Template\n\nHere's a comprehensive template for \`${filePath}\` with format and style guidance:\n\n\`\`\`markdown\n${template}\`\`\`\n\n## Next Steps\n\n1. **Create file**: Use Write tool to create \`${filePath}\` based on this template\n2. **Refine style** (optional): Call \`style_check\` for AI feedback on style and best practices\n3. **Validate syntax**: Call \`validate_requirements\` to verify format is correct\n4. **Push to Convex**: Call \`push_requirements\` to sync requirements to data layer\n\n**Note**: Requirements files can be colocated with code (\`src/auth.requirements.md\`) or centralized in \`.requirements/\` directory.`);
+    const localStyleGuide = readLocalStyleGuide(context.workspaceRoot);
+    return textResponse(generateStyleGuide({
+        requirements,
+        customStyleGuidance,
+        filePath,
+        localStyleGuide,
+    }));
 }
 /**
  * Handler for validate_requirements tool
@@ -284,23 +73,30 @@ export async function handleValidateRequirements(args, context) {
         // Check push readiness
         const pushValidation = validateForPush(parsed.metadata);
         let headline;
-        let pushDetails = '';
+        let pushDetails = "";
         if (!pushValidation.valid) {
             headline = `❌ \`${filePath}\` - Not push-ready\n- ${pushValidation.reason}`;
         }
         else {
-            const actionLabel = pushValidation.action === 'create' ? 'Will create new document' : 'Will update existing document';
+            const actionLabel = pushValidation.action === "create"
+                ? "Will create new document"
+                : "Will update existing document";
             headline = `✓ \`${filePath}\` - ${actionLabel}`;
             if (pushValidation.warning) {
                 pushDetails = `\n- ⚠️ ${pushValidation.warning}`;
             }
         }
-        return textResponse(`${headline}${pushDetails}\n\n**Metadata:**\n- Version: ${parsed.metadata.version ?? '(none)'}\n- Document: ${parsed.metadata.document?.title || '(none)'}\n- Document ID: ${parsed.metadata.document?.id || '(none)'}\n\n**Requirements:** ${reqCount} root requirement(s) found`);
+        return textResponse(`${headline}${pushDetails}\n\n**Metadata:**\n- Version: ${parsed.metadata.version ?? "(none)"}\n- Document: ${parsed.metadata.document?.title || "(none)"}\n- Document ID: ${parsed.metadata.document?.id || "(none)"}\n\n**Requirements:** ${reqCount} root requirement(s) found`);
     }
     catch (error) {
         // MCP-AUTHOR-2.1: Syntax errors are returned with details
         return {
-            content: [{ type: 'text', text: `✗ Validation failed for \`${filePath}\`:\n\n${error instanceof Error ? error.message : String(error)}` }],
+            content: [
+                {
+                    type: "text",
+                    text: `✗ Validation failed for \`${filePath}\`:\n\n${error instanceof Error ? error.message : String(error)}`,
+                },
+            ],
             isError: true,
         };
     }

package/dist/mcp/handlers/debug.d.ts

@@ -4,12 +4,11 @@
  * Returns diagnostic information about the MCP server environment.
  * Useful for debugging configuration issues.
  */
-import type { HandlerContext, ToolResponse } from './types.js';
+import type { HandlerContext, ToolResponse } from "./types.js";
 /**
  * Arguments for debug_mcp_environment tool
  */
-export interface DebugMcpEnvironmentArgs {
-}
+export type DebugMcpEnvironmentArgs = Record<string, never>;
 /**
  * Handler for debug_mcp_environment tool
  */

package/dist/mcp/handlers/debug.js

@@ -4,34 +4,34 @@
  * Returns diagnostic information about the MCP server environment.
  * Useful for debugging configuration issues.
  */
-import { textResponse } from './types.js';
+import { textResponse } from "./types.js";
 /**
  * Handler for debug_mcp_environment tool
  */
 export async function handleDebugMcpEnvironment(_args, context) {
     // Check for Antigravity-specific env vars
     const antigravityVars = Object.entries(context.env)
-        .filter(([key]) => key.startsWith('GEMINI_') || key.startsWith('ANTIGRAVITY_'))
+        .filter(([key]) => key.startsWith("GEMINI_") || key.startsWith("ANTIGRAVITY_"))
         .map(([key, value]) => `  ${key}: ${value}`)
-        .join('\n');
+        .join("\n");
     // Show discovered projects from env vars
     const projectList = Array.from(context.projectPaths.entries())
         .map(([id, path]) => `  ${id}: ${path}`)
-        .join('\n');
+        .join("\n");
     const text = `# MCP Server Environment Debug Info
 
 **process.cwd():** ${process.cwd()}
 **WORKSPACE_ROOT:** ${context.workspaceRoot}
-**REQUIREMENTS_DIR env:** ${context.env.REQUIREMENTS_DIR || '(not set)'}
-**HOME:** ${context.env.HOME || '(not set)'}
-**PWD:** ${context.env.PWD || '(not set)'}
-**OLDPWD:** ${context.env.OLDPWD || '(not set)'}
+**REQUIREMENTS_DIR env:** ${context.env.REQUIREMENTS_DIR || "(not set)"}
+**HOME:** ${context.env.HOME || "(not set)"}
+**PWD:** ${context.env.PWD || "(not set)"}
+**OLDPWD:** ${context.env.OLDPWD || "(not set)"}
 
 **Antigravity/Gemini env vars:**
-${antigravityVars || '(none found)'}
+${antigravityVars || "(none found)"}
 
 **Projects from PROJ_* env vars:**
-${projectList || '(none found)'}`;
+${projectList || "(none found)"}`;
     return textResponse(text);
 }
 //# sourceMappingURL=debug.js.map

package/dist/mcp/handlers/get.d.ts

@@ -3,7 +3,7 @@
  *
  * Retrieves a specific requirement by ID with its full tree and test coverage.
  */
-import type { HandlerContext, ToolResponse } from './types.js';
+import type { HandlerContext, ToolResponse } from "./types.js";
 /**
  * Arguments for get_requirement tool
  */

package/dist/mcp/handlers/get.js

@@ -3,10 +3,10 @@
  *
  * Retrieves a specific requirement by ID with its full tree and test coverage.
  */
-import { textResponse } from './types.js';
-import { glob } from 'glob';
-import { getRequirementTree, formatRequirementTree, } from '../requirements.js';
-import { findFilesWithRequirement, findTestCodeForRequirement, } from '../testCodeExtractor.js';
+import { glob } from "glob";
+import { formatRequirementTree, getRequirementTree, } from "../../requirements/index.js";
+import { findFilesWithRequirement, findTestCodeForRequirement, } from "../../requirements/testCodeExtractor.js";
+import { textResponse } from "./types.js";
 /**
  * Handler for get_requirement tool
  *
@@ -31,10 +31,10 @@ export async function handleGetRequirement(args, context) {
     const root = tree[0];
     const formatted = formatRequirementTree(tree);
     // MCP-GET-1.3: Find test files that reference this requirement
-    const testFiles = await glob('**/*.{test,spec}.{js,jsx,ts,tsx}', {
+    const testFiles = await glob("**/*.{test,spec}.{js,jsx,ts,tsx}", {
         cwd: project.path,
         absolute: true,
-        ignore: ['**/node_modules/**', '**/dist/**', '**/build/**'],
+        ignore: ["**/node_modules/**", "**/dist/**", "**/build/**"],
     });
     const matchingFiles = findFilesWithRequirement(testFiles, id);
     const testCodeSections = [];
@@ -47,8 +47,9 @@ export async function handleGetRequirement(args, context) {
                 if (i === j)
                     return false;
                 // other contains ref if it starts before or at the same line and ends after or at the same line
-                return other.startLine <= ref.startLine && other.endLine >= ref.endLine &&
-                    (other.startLine < ref.startLine || other.endLine > ref.endLine);
+                return (other.startLine <= ref.startLine &&
+                    other.endLine >= ref.endLine &&
+                    (other.startLine < ref.startLine || other.endLine > ref.endLine));
             });
             return !isNested;
         });
@@ -57,8 +58,8 @@ export async function handleGetRequirement(args, context) {
         }
     }
     const testSection = testCodeSections.length > 0
-        ? `\n\n## Test Coverage (${testCodeSections.length} reference(s)):\n\n${testCodeSections.join('\n\n---\n\n')}`
-        : '\n\n## Test Coverage\n\nNo tests found referencing this requirement.';
+        ? `\n\n## Test Coverage (${testCodeSections.length} reference(s)):\n\n${testCodeSections.join("\n\n---\n\n")}`
+        : "\n\n## Test Coverage\n\nNo tests found referencing this requirement.";
     return textResponse(`# ${id}\n\n**Document:** ${root.documentTitle}\n**Source:** ${root.sourceFile}\n\n## Requirement Tree (${tree.length} node(s)):\n\n\`\`\`\n${formatted}\n\`\`\`${testSection}`);
 }
 //# sourceMappingURL=get.js.map

package/dist/mcp/handlers/index.d.ts

@@ -5,24 +5,24 @@
  * and returns an MCP response. Handlers receive a context object
  * that provides access to shared dependencies.
  */
-export type { ToolContentItem, ToolResponse, HandlerContext, ToolHandler, } from './types.js';
-export { textResponse, errorResponse } from './types.js';
-export { handleDebugMcpEnvironment } from './debug.js';
-export type { DebugMcpEnvironmentArgs } from './debug.js';
-export { handleSearchRequirements } from './search.js';
-export type { SearchRequirementsArgs } from './search.js';
-export { handleListAllRequirements, handleListUntestedRequirements } from './list.js';
-export type { ListAllRequirementsArgs, ListUntestedRequirementsArgs } from './list.js';
-export { handleGetRequirement } from './get.js';
-export type { GetRequirementArgs } from './get.js';
-export { handleGetRequirementsByTest, handleGetTestsByRequirement } from './test-mapping.js';
-export type { GetRequirementsByTestArgs, GetTestsByRequirementArgs } from './test-mapping.js';
-export { handleGetRequirementCoverage, handleGetProjectCoverageSummary } from './coverage.js';
-export type { GetRequirementCoverageArgs, GetProjectCoverageSummaryArgs } from './coverage.js';
-export { handleCreateRequirementDocument, handleValidateRequirements } from './authoring.js';
-export type { CreateRequirementDocumentArgs, ValidateRequirementsArgs } from './authoring.js';
-export { handlePushRequirements } from './push.js';
-export type { PushRequirementsArgs } from './push.js';
-export { handleStyleCheck, handleReviewTest } from './review.js';
-export type { StyleCheckArgs, ReviewTestArgs } from './review.js';
+export type { CreateRequirementDocumentArgs, ValidateRequirementsArgs, } from "./authoring.js";
+export { handleCreateRequirementDocument, handleValidateRequirements, } from "./authoring.js";
+export type { DebugMcpEnvironmentArgs } from "./debug.js";
+export { handleDebugMcpEnvironment } from "./debug.js";
+export type { GetRequirementArgs } from "./get.js";
+export { handleGetRequirement } from "./get.js";
+export type { ListArgs } from "./list.js";
+export { handleList } from "./list.js";
+export type { PushRequirementsArgs } from "./push.js";
+export { handlePushRequirements } from "./push.js";
+export type { ReportArgs } from "./report.js";
+export { handleReport } from "./report.js";
+export type { ReviewTestArgs, StyleCheckArgs } from "./review.js";
+export { handleReviewTest, handleStyleCheck } from "./review.js";
+export type { SearchRequirementsArgs } from "./search.js";
+export { handleSearchRequirements } from "./search.js";
+export type { GetRequirementsByTestArgs, GetTestsByRequirementArgs, } from "./test-mapping.js";
+export { handleGetRequirementsByTest, handleGetTestsByRequirement, } from "./test-mapping.js";
+export type { HandlerContext, ToolContentItem, ToolHandler, ToolResponse, } from "./types.js";
+export { errorResponse, textResponse } from "./types.js";
 //# sourceMappingURL=index.d.ts.map