@popoverai/dotrequirements 0.26.2 → 0.27.1

package/dist/mcp/handlers/report.js

@@ -1,134 +0,0 @@
-/**
- * Unified coverage handler for the MCP `report_coverage` tool. Replaces
- * `get_requirement_coverage` and `get_project_coverage_summary` with a
- * single tool that takes a `source: "local" | "cloud"` argument and
- * mirrors the CLI `dotreq report` semantics.
- */
-import { getProjectCoverage as queryProjectCoverage, getRequirementCoverage as queryRequirementCoverage, } from "../../requirements/cloud-coverage.js";
-import { buildLocalReport, LocalReportCacheMissingError, } from "../../requirements/coverage.js";
-import { CONVEX_URL } from "../convexClient.js";
-import { errorResponse, textResponse } from "./types.js";
-export async function handleReport(args, context) {
-    const source = args.source ?? "local";
-    if (source === "local") {
-        if (args.branch || args.sinceTimestamp !== undefined) {
-            return errorResponse("branch and sinceTimestamp require source=cloud. Local reports cover only the most recent test run on this machine.");
-        }
-        try {
-            const report = buildLocalReport({
-                projectRoot: context.workspaceRoot,
-                requirementFilter: args.requirementKey,
-            });
-            return textResponse(formatLocalReport(report));
-        }
-        catch (error) {
-            if (error instanceof LocalReportCacheMissingError) {
-                return errorResponse(error.message);
-            }
-            throw error;
-        }
-    }
-    // source === "cloud"
-    let project;
-    try {
-        project = await context.getProjectFromDiscovery(args.projectId);
-    }
-    catch (error) {
-        return errorResponse(`Cloud report requires cloud credentials. Run \`dotrequirements link\` to connect to cloud.\n\nError: ${error instanceof Error ? error.message : String(error)}`);
-    }
-    if (args.requirementKey) {
-        const record = await queryRequirementCoverage(args.requirementKey, project.projectId, project.projectSecret, CONVEX_URL);
-        return textResponse(formatCloudRequirement(record));
-    }
-    const record = await queryProjectCoverage(project.projectId, project.projectSecret, CONVEX_URL, {
-        branch: args.branch,
-        sinceTimestamp: args.sinceTimestamp,
-    });
-    return textResponse(formatCloudProject(record, {
-        branch: args.branch,
-        sinceTimestamp: args.sinceTimestamp,
-    }));
-}
-function formatLocalReport(report) {
-    const { total, tested, untested, coveragePercent } = report.summary;
-    let out = `# Coverage Report (local)\n\n`;
-    if (report.warnings.length > 0) {
-        for (const w of report.warnings) {
-            out += `> ⚠️ ${w}\n`;
-        }
-        out += "\n";
-    }
-    out += `**Total:** ${total} | **Tested:** ${tested} | **Untested:** ${untested} | **Coverage:** ${coveragePercent}%\n\n`;
-    const testedEntries = report.entries.filter((c) => c.tested);
-    if (testedEntries.length > 0) {
-        out += `## Tested (${testedEntries.length})\n\n`;
-        for (const c of testedEntries) {
-            out += `- **${c.key}**: ${c.content}\n`;
-            for (const loc of c.locations) {
-                out += `  - \`${loc}\`\n`;
-            }
-        }
-        out += "\n";
-    }
-    const untestedEntries = report.entries.filter((c) => !c.tested);
-    if (untestedEntries.length > 0) {
-        out += `## Untested (${untestedEntries.length})\n\n`;
-        for (const c of untestedEntries) {
-            out += `- **${c.key}**: ${c.content}\n`;
-        }
-    }
-    return out;
-}
-function formatCloudRequirement(record) {
-    if (!record.lastTestedAt) {
-        return `**${record.requirementKey}** has no cloud coverage records.`;
-    }
-    const lastTested = new Date(record.lastTestedAt).toISOString();
-    let out = `# Coverage for ${record.requirementKey} (cloud)\n\n`;
-    out += `**Last tested:** ${lastTested}\n`;
-    if (record.branch)
-        out += `**Branch:** ${record.branch}\n`;
-    if (record.testFile) {
-        out += `**Test location:** \`${record.testFile}${record.testLine ? `:${record.testLine}` : ""}\`\n`;
-    }
-    const otherBranches = record.allBranches.filter((b) => b.branch !== record.branch);
-    if (otherBranches.length > 0) {
-        out += `\n**Also tested on:**\n`;
-        for (const b of otherBranches) {
-            out += `- ${b.branch}: ${new Date(b.lastTestedAt).toISOString()}\n`;
-        }
-    }
-    return out;
-}
-function formatCloudProject(record, filters) {
-    const tested = record.tested.length;
-    const untested = record.untested.length;
-    const total = tested + untested;
-    const coveragePercent = total > 0 ? ((tested / total) * 100).toFixed(1) : "0.0";
-    let filterNote = "";
-    if (filters.branch)
-        filterNote += `\n**Branch:** ${filters.branch}`;
-    if (filters.sinceTimestamp) {
-        filterNote += `\n**Since:** ${new Date(filters.sinceTimestamp).toISOString()}`;
-    }
-    let out = `# Project Coverage Report (cloud)\n\n`;
-    out += `**Total Requirements:** ${total}\n**Coverage:** ${coveragePercent}%${filterNote}\n`;
-    if (record.tested.length > 0) {
-        out += `\n## Tested Requirements (${record.tested.length})\n\n`;
-        for (const t of record.tested) {
-            const date = new Date(t.lastTestedAt).toISOString();
-            const location = t.testFile
-                ? ` (\`${t.testFile}${t.testLine ? `:${t.testLine}` : ""}\`)`
-                : "";
-            out += `- **${t.requirementKey}** [${t.branch}]: ${date}${location}\n`;
-        }
-    }
-    if (record.untested.length > 0) {
-        out += `\n## Untested Requirements (${record.untested.length})\n\n`;
-        for (const key of record.untested) {
-            out += `- ${key}\n`;
-        }
-    }
-    return out;
-}
-//# sourceMappingURL=report.js.map

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

@@ -1,52 +0,0 @@
-/**
- * Review handlers for MCP tools
- *
- * Provides AI-powered review functionality:
- * - style_check: Check requirements or test files for style issues
- * - review_test: Comprehensively review tests for semantic correctness
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for style_check tool
- */
-export interface StyleCheckArgs {
-    filePath: string;
-    requirementKeys?: string[];
-    model?: string;
-    projectId?: string;
-}
-/**
- * Arguments for review_test tool
- */
-export interface ReviewTestArgs {
-    testFilePath: string;
-    projectId?: string;
-}
-/**
- * Handler for style_check tool
- *
- * Requirements covered:
- * - MCP-REVIEW-1.0: For requirements files, feedback identifies clarity issues such as vague language and missing preconditions
- * - MCP-REVIEW-1.1: For test files, feedback identifies incorrect requirement() usage and missing test coverage
- * - MCP-REVIEW-1.2: Feedback is categorized by severity: must fix, should fix, could improve
- * - MCP-REVIEW-1.3: When cloud credentials are unavailable, an error explains how to authenticate
- */
-export declare function handleStyleCheck(args: StyleCheckArgs, context: HandlerContext, options?: {
-    useEnvAuth?: boolean;
-    apiBaseUrl?: string;
-}): Promise<ToolResponse>;
-/**
- * Handler for review_test tool
- *
- * Requirements covered:
- * - MCP-REVIEW-2.0: Feedback identifies test setup that does not match requirement preconditions
- * - MCP-REVIEW-2.1: Feedback identifies test actions that do not match requirement triggers
- * - MCP-REVIEW-2.2: Feedback identifies test assertions that do not match requirement outcomes
- * - MCP-REVIEW-2.3: Feedback identifies requirements without test coverage
- * - MCP-REVIEW-2.4: Feedback identifies tests that reference non-existent requirements
- * - MCP-REVIEW-2.5: When cloud credentials are unavailable, an error explains how to authenticate
- */
-export declare function handleReviewTest(args: ReviewTestArgs, context: HandlerContext, options?: {
-    apiBaseUrl?: string;
-}): Promise<ToolResponse>;
-//# sourceMappingURL=review.d.ts.map

package/dist/mcp/handlers/review.js

@@ -1,243 +0,0 @@
-/**
- * Review handlers for MCP tools
- *
- * Provides AI-powered review functionality:
- * - style_check: Check requirements or test files for style issues
- * - review_test: Comprehensively review tests for semantic correctness
- */
-import { existsSync, readFileSync } from "node:fs";
-import { dirname } from "node:path";
-import { fetchReviewTestFeedback, fetchStyleCheckFeedback, } from "../../requirements/cloud-ai.js";
-import { findRequirementsInFile } from "../../requirements/grep.js";
-import { filterRequirementsByKeys, formatRequirementTree, getRequirementTree, } from "../../requirements/index.js";
-import { discoverProjects, } from "../../utils/project-discovery.js";
-import { errorResponse, resolveProjectFilePath, textResponse, } from "./types.js";
-const STYLE_CHECK_GUIDANCE = `
-
----
-
-## How to use this feedback
-
-1. **This check is stateless.** It is a "new set of eyes" from any previous feedback rounds — it has no memory of prior suggestions or changes you've already made.
-
-2. **Act on feedback from the posture of "what will make the requirements better."** The severity categories (MUST FIX / SHOULD FIX / COULD IMPROVE) are prioritized for convenience, but unless the user has explicitly told you to ignore lower-priority feedback, go ahead and make any improvements — minor or otherwise. If you believe acting on a specific piece of feedback would make the requirements *worse*, surface that feedback to the user rather than silently ignoring it. Otherwise, just act.
-
-3. **Next steps:** Always run \`validate_requirements\` again after making updates. If you make significant changes based on this feedback, you can run \`style_check\` again — but be aware that will be a fresh set of eyes, not a continued conversation.`;
-/**
- * Handler for style_check tool
- *
- * Requirements covered:
- * - MCP-REVIEW-1.0: For requirements files, feedback identifies clarity issues such as vague language and missing preconditions
- * - MCP-REVIEW-1.1: For test files, feedback identifies incorrect requirement() usage and missing test coverage
- * - MCP-REVIEW-1.2: Feedback is categorized by severity: must fix, should fix, could improve
- * - MCP-REVIEW-1.3: When cloud credentials are unavailable, an error explains how to authenticate
- */
-export async function handleStyleCheck(args, context, options) {
-    const { filePath, requirementKeys, model, projectId } = args;
-    const { useEnvAuth = false, apiBaseUrl = "https://app.dotrequirements.io" } = options ?? {};
-    // #49: Resolve against the discovered project.path (matching push) with a
-    // workspaceRoot fallback, so a relative path that push accepts also works
-    // here in PROJ_*-based setups. Discovery may throw without credentials — that
-    // is fine, we then fall back to workspaceRoot.
-    let styleProjectPath;
-    try {
-        styleProjectPath = (await context.getProjectFromDiscovery(projectId)).path;
-    }
-    catch {
-        styleProjectPath = undefined;
-    }
-    const fullPath = resolveProjectFilePath(filePath, styleProjectPath, context.workspaceRoot);
-    if (!existsSync(fullPath)) {
-        return errorResponse(`File not found: ${filePath}`);
-    }
-    // Read file contents
-    const fileContents = readFileSync(fullPath, "utf-8");
-    // Detect file type
-    // MCP-REVIEW-1.0 & MCP-REVIEW-1.1: Different feedback for different file types
-    const isRequirementsFile = filePath.endsWith(".requirements.md");
-    const isTestFile = /\.(test|spec)\.(js|jsx|ts|tsx)$/.test(filePath);
-    if (!isRequirementsFile && !isTestFile) {
-        return errorResponse(`Unsupported file type. File must be:\n- Requirements file: *.requirements.md\n- Test file: *.test.{js,jsx,ts,tsx} or *.spec.{js,jsx,ts,tsx}`);
-    }
-    const fileType = isRequirementsFile ? "requirements" : "test";
-    // If requirementKeys provided, filter the file to only those requirements
-    let fileContentsToCheck = fileContents;
-    let scopeNote = "";
-    if (requirementKeys && requirementKeys.length > 0) {
-        if (!isRequirementsFile) {
-            return errorResponse(`requirementKeys can only be used with requirements files (*.requirements.md), not test files.`);
-        }
-        try {
-            const { filteredContent, foundKeys, missingKeys } = filterRequirementsByKeys(fileContents, requirementKeys);
-            if (foundKeys.length === 0) {
-                return errorResponse(`None of the specified requirement keys were found in ${filePath}: ${requirementKeys.join(", ")}`);
-            }
-            fileContentsToCheck = filteredContent;
-            if (missingKeys.length > 0) {
-                scopeNote = `\n\n> **Note:** Some specified keys were not found in the file: ${missingKeys.join(", ")}`;
-            }
-        }
-        catch (error) {
-            return errorResponse(`Failed to filter requirements: ${error instanceof Error ? error.message : String(error)}`);
-        }
-    }
-    // MCP-REVIEW-1.3: Get credentials - walk up from file's directory to find project
-    const fileDir = dirname(fullPath);
-    let project;
-    try {
-        if (projectId) {
-            // #48: PROJ-CONTEXT-6 — an explicit projectId disambiguates a
-            // multi-project workspace. Thread it straight through to discovery
-            // (matching review_test/push/report) instead of the file-directory
-            // auto-detect path, which cannot choose among multiple projects.
-            project = await context.getProjectFromDiscovery(projectId);
-        }
-        else if (useEnvAuth) {
-            // Using env auth - go straight to context
-            project = await context.getProjectFromDiscovery();
-        }
-        else {
-            // Try to find a project starting from the file's directory
-            const result = await discoverProjects(fileDir);
-            if (result.type === "none") {
-                // If no project found from file dir, try from context
-                project = await context.getProjectFromDiscovery();
-            }
-            else if (result.type === "single") {
-                project = result.project;
-            }
-            else {
-                // #48: Multiple projects — can't auto-detect. The remedy is to pass
-                // projectId (not `dotrequirements link`, which is already satisfied);
-                // list the available projects so the caller can choose.
-                const available = result.projects
-                    .map((p) => p.projectId)
-                    .filter(Boolean)
-                    .join(", ");
-                return errorResponse(`Multiple projects found. Specify the \`projectId\` parameter to choose one${available ? ` (available: ${available})` : ""}.`);
-            }
-        }
-    }
-    catch (error) {
-        return errorResponse(`Style check requires project credentials. Run \`dotrequirements link\` to connect to cloud.\n\nError: ${error instanceof Error ? error.message : String(error)}`);
-    }
-    // Call hosted endpoint via the shared library helper
-    try {
-        const feedback = await fetchStyleCheckFeedback({
-            apiBaseUrl,
-            projectId: project.projectId,
-            projectSecret: project.projectSecret,
-            fileContents: fileContentsToCheck,
-            fileType,
-            model,
-        });
-        const scopeLabel = requirementKeys && requirementKeys.length > 0
-            ? ` (${requirementKeys.join(", ")})`
-            : "";
-        // MCP-REVIEW-1.2: Feedback includes severity categories (in the API response)
-        return textResponse(`# Style Check Results for \`${filePath}\`${scopeLabel}\n\n${feedback}${scopeNote}${STYLE_CHECK_GUIDANCE}`);
-    }
-    catch (error) {
-        return errorResponse(`Style check failed: ${error instanceof Error ? error.message : String(error)}`);
-    }
-}
-/**
- * Handler for review_test tool
- *
- * Requirements covered:
- * - MCP-REVIEW-2.0: Feedback identifies test setup that does not match requirement preconditions
- * - MCP-REVIEW-2.1: Feedback identifies test actions that do not match requirement triggers
- * - MCP-REVIEW-2.2: Feedback identifies test assertions that do not match requirement outcomes
- * - MCP-REVIEW-2.3: Feedback identifies requirements without test coverage
- * - MCP-REVIEW-2.4: Feedback identifies tests that reference non-existent requirements
- * - MCP-REVIEW-2.5: When cloud credentials are unavailable, an error explains how to authenticate
- */
-export async function handleReviewTest(args, context, options) {
-    const { testFilePath, projectId } = args;
-    const { apiBaseUrl = "https://app.dotrequirements.io" } = options ?? {};
-    // #49: Resolve against the discovered project.path (matching push) with a
-    // workspaceRoot fallback. Discovery may throw without credentials — fall back
-    // to workspaceRoot; the credential error is reported later.
-    let reviewProjectPath;
-    try {
-        reviewProjectPath = (await context.getProjectFromDiscovery(projectId)).path;
-    }
-    catch {
-        reviewProjectPath = undefined;
-    }
-    const fullPath = resolveProjectFilePath(testFilePath, reviewProjectPath, context.workspaceRoot);
-    if (!existsSync(fullPath)) {
-        return errorResponse(`File not found: ${testFilePath}`);
-    }
-    // Verify it's a test file
-    const isTestFile = /\.(test|spec)\.(js|jsx|ts|tsx)$/.test(testFilePath);
-    if (!isTestFile) {
-        return errorResponse(`File must be a test file: *.test.{js,jsx,ts,tsx} or *.spec.{js,jsx,ts,tsx}`);
-    }
-    // Read test file contents
-    const testFileContents = readFileSync(fullPath, "utf-8");
-    // #43: Extract requirement IDs via the shared AST-based extractor so that
-    // multi-arg calls (`requirement("A", "B")`) and options-bearing calls
-    // (`requirement("A", { ... })`) are captured — the old single-string regex
-    // matched neither.
-    const references = await findRequirementsInFile(fullPath);
-    const requirementIds = new Set(references.map((ref) => ref.requirementId));
-    // MCP-REVIEW-2.5: Get project credentials
-    let project;
-    try {
-        project = await context.getProjectFromDiscovery(projectId);
-    }
-    catch (error) {
-        return errorResponse(`Test review requires a configured dotrequirements project.\n\nError: ${error instanceof Error ? error.message : String(error)}`);
-    }
-    // Load all requirements for this project
-    const allRequirements = await context.getRequirements(projectId);
-    // Group requirement IDs by their root to avoid sending duplicate trees
-    // e.g., NAV-3.0, NAV-3.1, NAV-3.2 all belong to root NAV-3
-    //
-    // #42: A reference may be a bare root (`AUTH-1`), an index child (`AUTH-1.0`),
-    // or a label path (`AUTH-1.given`). Normalize each reference to its root id
-    // (the substring before the first dot) before matching — the same approach
-    // getReferencedRequirementIds uses — so label-path refs resolve instead of
-    // being reported as non-existent.
-    const rootToTestedIds = new Map();
-    for (const reqId of requirementIds) {
-        const dotIndex = reqId.indexOf(".");
-        const refRootId = dotIndex > 0 ? reqId.substring(0, dotIndex) : reqId;
-        const req = allRequirements.find((r) => r.rootId === refRootId);
-        if (req) {
-            if (!rootToTestedIds.has(req.rootId)) {
-                rootToTestedIds.set(req.rootId, new Set());
-            }
-            rootToTestedIds.get(req.rootId).add(reqId);
-        }
-    }
-    // Build requirements array with one entry per unique root tree
-    // MCP-REVIEW-2.0, 2.1, 2.2: These validations happen in the API based on the tree structure
-    const requirements = [];
-    for (const [rootId, testedIds] of rootToTestedIds) {
-        const tree = getRequirementTree(allRequirements, rootId);
-        const formattedTree = formatRequirementTree(tree);
-        requirements.push({
-            id: rootId,
-            content: formattedTree,
-            testedIds: Array.from(testedIds).sort(),
-        });
-    }
-    // Call hosted endpoint via the shared library helper
-    // MCP-REVIEW-2.3 & 2.4: API identifies coverage gaps and non-existent references
-    try {
-        const feedback = await fetchReviewTestFeedback({
-            apiBaseUrl,
-            projectId: project.projectId,
-            projectSecret: project.projectSecret,
-            testFileContents,
-            requirements,
-        });
-        return textResponse(`# Test Review Results for \`${testFilePath}\`\n\n${feedback}`);
-    }
-    catch (error) {
-        return errorResponse(`Test review failed: ${error instanceof Error ? error.message : String(error)}`);
-    }
-}
-//# sourceMappingURL=review.js.map

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

@@ -1,30 +0,0 @@
-/**
- * search_requirements handler
- *
- * Searches requirements by text or regex query across IDs, content, and labels.
- * Returns matching requirements with their full tree context.
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for search_requirements tool
- */
-export interface SearchRequirementsArgs {
-    query: string;
-    useRegex?: boolean;
-    projectId?: string;
-}
-/**
- * Handler for search_requirements tool
- *
- * Requirements covered:
- * - MCP-SEARCH-1.0: Query matches requirement ID
- * - MCP-SEARCH-1.1: Query matches requirement content
- * - MCP-SEARCH-1.2: Query matches requirement label
- * - MCP-SEARCH-1.3: useRegex interprets query as case-insensitive regex
- * - MCP-SEARCH-1.4: Invalid regex returns error
- * - MCP-SEARCH-1.5: No matches returns informative message
- * - MCP-SEARCH-1.6: Nested match returns the full root requirement tree
- * - MCP-SEARCH-1.7: Results include full tree as code block
- */
-export declare function handleSearchRequirements(args: SearchRequirementsArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=search.d.ts.map

package/dist/mcp/handlers/search.js

@@ -1,58 +0,0 @@
-/**
- * search_requirements handler
- *
- * Searches requirements by text or regex query across IDs, content, and labels.
- * Returns matching requirements with their full tree context.
- */
-import { formatRequirementTree, getRequirementTree, searchRequirements, } from "../../requirements/index.js";
-import { errorResponse, textResponse } from "./types.js";
-/**
- * Handler for search_requirements tool
- *
- * Requirements covered:
- * - MCP-SEARCH-1.0: Query matches requirement ID
- * - MCP-SEARCH-1.1: Query matches requirement content
- * - MCP-SEARCH-1.2: Query matches requirement label
- * - MCP-SEARCH-1.3: useRegex interprets query as case-insensitive regex
- * - MCP-SEARCH-1.4: Invalid regex returns error
- * - MCP-SEARCH-1.5: No matches returns informative message
- * - MCP-SEARCH-1.6: Nested match returns the full root requirement tree
- * - MCP-SEARCH-1.7: Results include full tree as code block
- */
-export async function handleSearchRequirements(args, context) {
-    const { query, useRegex = false, projectId } = args;
-    const requirements = await context.getRequirements(projectId);
-    let results;
-    if (useRegex) {
-        // MCP-SEARCH-1.3: Interpret query as case-insensitive regex
-        // MCP-SEARCH-1.4: Return error for invalid regex
-        try {
-            const regex = new RegExp(query, "i");
-            results = requirements.filter((r) => regex.test(r.id) || regex.test(r.content) || regex.test(r.label));
-        }
-        catch (error) {
-            return errorResponse(`Invalid regular expression: ${error instanceof Error ? error.message : String(error)}`);
-        }
-    }
-    else {
-        // MCP-SEARCH-1.0, MCP-SEARCH-1.1, MCP-SEARCH-1.2: Text search across ID, content, label
-        results = searchRequirements(requirements, query);
-    }
-    // MCP-SEARCH-1.6: Collect unique root IDs from all matches (nested matches bubble up to their root)
-    const matchedRootIds = new Set(results.map((r) => r.rootId));
-    const rootResults = requirements.filter((r) => r.path.length === 0 && matchedRootIds.has(r.rootId));
-    // MCP-SEARCH-1.5: No matches returns informative message
-    if (rootResults.length === 0) {
-        return textResponse(`No requirements found matching "${query}"${useRegex ? " (regex)" : ""}`);
-    }
-    // MCP-SEARCH-1.7: Each result includes full tree as code block
-    const formatted = rootResults
-        .map((r) => {
-        const tree = getRequirementTree(requirements, r.id);
-        const treeFormatted = formatRequirementTree(tree);
-        return `**${r.id}** (${r.label})\n${r.content}\n_Source: ${r.documentTitle}_\n\n\`\`\`\n${treeFormatted}\n\`\`\``;
-    })
-        .join("\n\n---\n\n");
-    return textResponse(`Found ${rootResults.length} requirement(s) matching "${query}"${useRegex ? " (regex)" : ""}:\n\n${formatted}`);
-}
-//# sourceMappingURL=search.js.map

package/dist/mcp/handlers/test-mapping.d.ts

@@ -1,39 +0,0 @@
-/**
- * get_requirements_by_test and get_tests_by_requirement handlers
- *
- * Maps between test files and requirements in both directions.
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for get_requirements_by_test tool
- */
-export interface GetRequirementsByTestArgs {
-    testFile: string;
-    projectId?: string;
-}
-/**
- * Handler for get_requirements_by_test tool
- *
- * Requirements covered:
- * - MCP-MAP-1.0: The response lists each requirement() call found in the test file
- * - MCP-MAP-1.1: For each reference, the requirement content and line number are shown
- * - MCP-MAP-1.2: When the test file does not exist, an error is returned
- */
-export declare function handleGetRequirementsByTest(args: GetRequirementsByTestArgs, context: HandlerContext): Promise<ToolResponse>;
-/**
- * Arguments for get_tests_by_requirement tool
- */
-export interface GetTestsByRequirementArgs {
-    requirementsFile: string;
-    projectId?: string;
-}
-/**
- * Handler for get_tests_by_requirement tool
- *
- * Requirements covered:
- * - MCP-MAP-2.0: The response lists which requirements have test references
- * - MCP-MAP-2.1: For each covered requirement, the test file and line number are shown
- * - MCP-MAP-2.2: Requirements without test references are listed separately
- */
-export declare function handleGetTestsByRequirement(args: GetTestsByRequirementArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=test-mapping.d.ts.map