@popoverai/dotrequirements 0.26.2 → 0.27.0

package/dist/utils/context-file.js

@@ -11,7 +11,8 @@ const PLATFORM_CONTEXT_FILES = {
     cursor: "AGENTS.md",
     codex: "AGENTS.md",
     "github-copilot": "AGENTS.md",
-    antigravity: "GEMINI.md",
+    // Antigravity 2.0 retired the GEMINI.md/.gemini conventions for AGENTS.md
+    antigravity: "AGENTS.md",
 };
 /**
  * Get the appropriate context file name for a platform
@@ -20,10 +21,14 @@ export function getContextFileName(platform) {
     return PLATFORM_CONTEXT_FILES[platform] ?? null;
 }
 /**
- * Find the git root directory
+ * Find the git root directory.
+ *
+ * CONTEXT-FILE-6: in a worktree, .git is a FILE pointing at the main
+ * checkout — matching directories only would walk past it and resolve to
+ * the main checkout's root, landing the context file in the wrong tree.
  */
 export async function findGitRoot() {
-    const gitDir = await findUp(".git", { type: "directory" });
+    const gitDir = await findUp(".git", { type: "both" });
     return gitDir ? dirname(gitDir) : null;
 }
 /**
@@ -95,8 +100,8 @@ export async function getContextFilePath(platform) {
  * Build a user-facing message explaining that context file installation
  * was skipped because the current directory is not inside a git repository.
  *
- * The MCP server itself is configured separately, so this message is only
- * about the second step (writing the platform's context file).
+ * Writing the platform's context file is the whole of setup now, so a missing
+ * git root means nothing was installed.
  */
 export function buildNoGitRepoMessage(fileName) {
     return [
@@ -106,8 +111,6 @@ export function buildNoGitRepoMessage(fileName) {
         "   To finish setup, either:",
         "     • run `git init` here, then re-run `dotreq ai-setup`, or",
         "     • `cd` into an existing project directory and run `dotreq ai-setup` there.",
-        "",
-        "   Note: the MCP server itself was configured successfully — only the context file step was skipped.",
     ].join("\n");
 }
 //# sourceMappingURL=context-file.js.map

package/dist/utils/project-settings.d.ts

@@ -41,6 +41,7 @@ export interface ProjectInfo {
  * Returns undefined if either is missing.
  */
 export declare function getCredentialsFromEnv(): ProjectSettings | undefined;
+export declare function setAuthFromEnv(enabled: boolean): void;
 /**
  * Find the project root by walking up from startDir looking for .requirements/ folder
  * Returns the directory containing .requirements/, or undefined if not found

package/dist/utils/project-settings.js

@@ -18,6 +18,19 @@ export function getCredentialsFromEnv() {
     }
     return undefined;
 }
+/**
+ * AUTHZ-6: explicit CI/CD credential injection. Set by the global
+ * --auth-from-env flag (cli.ts preAction hook); when enabled,
+ * getProjectCredentials reads DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET
+ * instead of file-based discovery. Without the flag those variables are
+ * ignored entirely — the explicit opt-in prevents credential conflicts
+ * between local and CI environments. (Previously the retired MCP server's
+ * --auth-from-env; ported to the CLI with identical semantics.)
+ */
+let authFromEnv = false;
+export function setAuthFromEnv(enabled) {
+    authFromEnv = enabled;
+}
 /**
  * Find the project root by walking up from startDir looking for .requirements/ folder
  * Returns the directory containing .requirements/, or undefined if not found
@@ -157,6 +170,15 @@ export function getProjectInfo(startDir = process.cwd()) {
  * Get project credentials, throwing helpful error if not available
  */
 export function getProjectCredentials(startDir = process.cwd()) {
+    // AUTHZ-6.0 / 6.1: with the explicit flag, env credentials replace
+    // file-based discovery entirely
+    if (authFromEnv) {
+        const envCredentials = getCredentialsFromEnv();
+        if (!envCredentials) {
+            throw new Error("--auth-from-env requires both DOTREQ_PROJECT_ID and DOTREQ_PROJECT_SECRET environment variables to be set.");
+        }
+        return envCredentials;
+    }
     const info = getProjectInfo(startDir);
     if (!info) {
         throw new Error('No dotrequirements project found. Run "dotrequirements init" to create one.');

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@popoverai/dotrequirements",
-  "version": "0.26.2",
-  "description": "Requirements tracking CLI, test harness, and MCP server",
+  "version": "0.27.0",
+  "description": "Requirements tracking CLI and test harness",
   "type": "module",
   "bin": {
     "dotrequirements": "./dist/cli.js",
@@ -11,8 +11,7 @@
     ".": "./dist/cli.js",
     "./test": "./dist/harness/index.js",
     "./schema": "./dist/schema/index.js",
-    "./schema/browser": "./dist/schema/browser.js",
-    "./mcp": "./dist/mcp/index.js"
+    "./schema/browser": "./dist/schema/browser.js"
   },
   "publishConfig": {
     "access": "public"
@@ -34,7 +33,6 @@
     "test-coverage",
     "bdd",
     "tdd",
-    "mcp",
     "ai-assistant"
   ],
   "author": "Will Raymer @Popover",

package/dist/mcp/convexClient.d.ts

@@ -1,19 +0,0 @@
-/**
- * Production Convex deployment URL
- */
-export declare const CONVEX_URL = "https://data.dotrequirements.io";
-/**
- * Convex configuration for cloud operations
- */
-interface ConvexConfig {
-    convexUrl: string;
-    projectId: string;
-    projectSecret: string;
-}
-/**
- * Load Convex configuration from project settings.
- * Returns null if credentials are not configured.
- */
-export declare function loadConvexConfig(cwd?: string): ConvexConfig | null;
-export {};
-//# sourceMappingURL=convexClient.d.ts.map

package/dist/mcp/convexClient.js

@@ -1,24 +0,0 @@
-import { getProjectCredentials } from "../utils/project-settings.js";
-/**
- * Production Convex deployment URL
- */
-export const CONVEX_URL = "https://data.dotrequirements.io";
-/**
- * Load Convex configuration from project settings.
- * Returns null if credentials are not configured.
- */
-export function loadConvexConfig(cwd = process.cwd()) {
-    try {
-        const credentials = getProjectCredentials(cwd);
-        return {
-            convexUrl: CONVEX_URL,
-            projectId: credentials.projectId,
-            projectSecret: credentials.projectSecret,
-        };
-    }
-    catch {
-        // Credentials not found or project not connected to cloud
-        return null;
-    }
-}
-//# sourceMappingURL=convexClient.js.map

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

@@ -1,41 +0,0 @@
-/**
- * Authoring handlers for MCP tools
- *
- * Provides document creation and validation:
- * - create_requirement_document: Generate requirements template with format guidance
- * - validate_requirements: Validate requirements file syntax offline
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for create_requirement_document tool
- */
-export interface CreateRequirementDocumentArgs {
-    filePath?: string;
-}
-/**
- * Arguments for validate_requirements tool
- */
-export interface ValidateRequirementsArgs {
-    filePath: string;
-}
-/**
- * Handler for create_requirement_document tool
- *
- * Requirements covered:
- * - MCP-AUTHOR-1.0: The template includes format guidance with code block examples
- * - MCP-AUTHOR-1.1: The template includes style guidance (concrete examples, concise prose, testable conditions)
- * - MCP-AUTHOR-1.2: When the project has requirementsStyleContext configured, it is included in the template
- * - MCP-AUTHOR-1.3: When cloud credentials are unavailable, the template works without the custom context
- */
-export declare function handleCreateRequirementDocument(args: CreateRequirementDocumentArgs, context: HandlerContext): Promise<ToolResponse>;
-/**
- * Handler for validate_requirements tool
- *
- * Requirements covered:
- * - MCP-AUTHOR-2.1: When the file has valid syntax, the response confirms validation passed
- * - MCP-AUTHOR-2.2: When the file has syntax errors, the response lists each error with location
- * - MCP-AUTHOR-2.3: Validation does not require network access or cloud credentials
- * - MCP-AUTHOR-2.4: When the file does not exist, an error is returned
- */
-export declare function handleValidateRequirements(args: ValidateRequirementsArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=authoring.d.ts.map

package/dist/mcp/handlers/authoring.js

@@ -1,113 +0,0 @@
-/**
- * Authoring handlers for MCP tools
- *
- * Provides document creation and validation:
- * - create_requirement_document: Generate requirements template with format guidance
- * - validate_requirements: Validate requirements file syntax offline
- */
-import { existsSync } from "node:fs";
-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, resolveProjectFilePath, textResponse, } from "./types.js";
-/**
- * Handler for create_requirement_document tool
- *
- * Requirements covered:
- * - MCP-AUTHOR-1.0: The template includes format guidance with code block examples
- * - MCP-AUTHOR-1.1: The template includes style guidance (concrete examples, concise prose, testable conditions)
- * - MCP-AUTHOR-1.2: When the project has requirementsStyleContext configured, it is included in the template
- * - 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;
-    // 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 {
-        // No project configured — discovered patterns will be empty
-    }
-    // MCP-AUTHOR-1.2: Try to fetch user-provided style context from cloud
-    let customStyleGuidance = null;
-    try {
-        const project = await context.getProjectFromDiscovery();
-        const contextData = await getProjectContext(project.projectId, project.projectSecret, CONVEX_URL);
-        customStyleGuidance = contextData?.requirementsStyleContext ?? null;
-    }
-    catch {
-        // MCP-AUTHOR-1.3: No credentials or cloud unavailable - continue without user context
-    }
-    const localStyleGuide = readLocalStyleGuide(context.workspaceRoot);
-    return textResponse(generateStyleGuide({
-        requirements,
-        customStyleGuidance,
-        filePath,
-        localStyleGuide,
-    }));
-}
-/**
- * Handler for validate_requirements tool
- *
- * Requirements covered:
- * - MCP-AUTHOR-2.1: When the file has valid syntax, the response confirms validation passed
- * - MCP-AUTHOR-2.2: When the file has syntax errors, the response lists each error with location
- * - MCP-AUTHOR-2.3: Validation does not require network access or cloud credentials
- * - MCP-AUTHOR-2.4: When the file does not exist, an error is returned
- */
-export async function handleValidateRequirements(args, context) {
-    const { filePath } = args;
-    // #49: Resolve against the discovered project.path (matching push) with a
-    // workspaceRoot fallback. MCP-AUTHOR-2.3: validation stays offline — if
-    // discovery has no credentials it simply throws and we fall back to
-    // workspaceRoot resolution.
-    let projectPath;
-    try {
-        projectPath = (await context.getProjectFromDiscovery()).path;
-    }
-    catch {
-        projectPath = undefined;
-    }
-    const fullPath = resolveProjectFilePath(filePath, projectPath, context.workspaceRoot);
-    // MCP-AUTHOR-2.4: Check if file exists
-    if (!existsSync(fullPath)) {
-        return errorResponse(`File not found: ${filePath}`);
-    }
-    try {
-        // MCP-AUTHOR-2.1 & MCP-AUTHOR-2.2: Parse and validate
-        const parsed = parseRequirementsFromFile(fullPath);
-        const reqCount = Object.keys(parsed.requirements).length;
-        // Check push readiness
-        const pushValidation = validateForPush(parsed.metadata);
-        let headline;
-        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";
-            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`);
-    }
-    catch (error) {
-        // MCP-AUTHOR-2.2: Syntax errors are returned with details
-        return {
-            content: [
-                {
-                    type: "text",
-                    text: `✗ Validation failed for \`${filePath}\`:\n\n${error instanceof Error ? error.message : String(error)}`,
-                },
-            ],
-            isError: true,
-        };
-    }
-}
-//# sourceMappingURL=authoring.js.map

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

@@ -1,16 +0,0 @@
-/**
- * debug_mcp_environment handler
- *
- * Returns diagnostic information about the MCP server environment.
- * Useful for debugging configuration issues.
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for debug_mcp_environment tool
- */
-export type DebugMcpEnvironmentArgs = Record<string, never>;
-/**
- * Handler for debug_mcp_environment tool
- */
-export declare function handleDebugMcpEnvironment(_args: DebugMcpEnvironmentArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=debug.d.ts.map

package/dist/mcp/handlers/debug.js

@@ -1,37 +0,0 @@
-/**
- * debug_mcp_environment handler
- *
- * Returns diagnostic information about the MCP server environment.
- * Useful for debugging configuration issues.
- */
-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_"))
-        .map(([key, value]) => `  ${key}: ${value}`)
-        .join("\n");
-    // Show discovered projects from env vars
-    const projectList = Array.from(context.projectPaths.entries())
-        .map(([id, path]) => `  ${id}: ${path}`)
-        .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)"}
-
-**Antigravity/Gemini env vars:**
-${antigravityVars || "(none found)"}
-
-**Projects from PROJ_* env vars:**
-${projectList || "(none found)"}`;
-    return textResponse(text);
-}
-//# sourceMappingURL=debug.js.map

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

@@ -1,24 +0,0 @@
-/**
- * get_requirement handler
- *
- * Retrieves a specific requirement by ID with its full tree and test coverage.
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for get_requirement tool
- */
-export interface GetRequirementArgs {
-    id: string;
-    projectId?: string;
-}
-/**
- * Handler for get_requirement tool
- *
- * Requirements covered:
- * - MCP-GET-1.0: When the ID matches a root requirement, the full tree is returned
- * - MCP-GET-1.1: When the ID matches a child requirement, that subtree is returned
- * - MCP-GET-1.2: When the ID does not exist, an error message is returned
- * - MCP-GET-1.3: When a requirement is retrieved, test references are shown with file path and line number
- */
-export declare function handleGetRequirement(args: GetRequirementArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=get.d.ts.map

package/dist/mcp/handlers/get.js

@@ -1,69 +0,0 @@
-/**
- * get_requirement handler
- *
- * Retrieves a specific requirement by ID with its full tree and test coverage.
- */
-import { glob } from "glob";
-import { formatRequirementTree } from "../../requirements/index.js";
-import { findFilesWithRequirement, findTestCodeForRequirement, } from "../../requirements/testCodeExtractor.js";
-import { textResponse } from "./types.js";
-/**
- * Handler for get_requirement tool
- *
- * Requirements covered:
- * - MCP-GET-1.0: When the ID matches a root requirement, the full tree is returned
- * - MCP-GET-1.1: When the ID matches a child requirement, that subtree is returned
- * - MCP-GET-1.2: When the ID does not exist, an error message is returned
- * - MCP-GET-1.3: When a requirement is retrieved, test references are shown with file path and line number
- */
-export async function handleGetRequirement(args, context) {
-    const { id, projectId } = args;
-    const project = await context.getProjectFromDiscovery(projectId);
-    const requirements = await context.getRequirements(projectId);
-    // Get the tree starting from this ID.
-    // MCP-GET-1.0: Full tree for root requirement
-    // MCP-GET-1.1: Subtree for child requirement
-    //
-    // #46: Match the node itself plus all of its descendants by id prefix. The
-    // shared getRequirementTree only matches on rootId/id equality, which drops
-    // grandchildren (e.g. REQ-123.0.0) when a child id (REQ-123.0) is requested.
-    const tree = requirements.filter((r) => r.id === id || r.id.startsWith(`${id}.`));
-    // MCP-GET-1.2: Return error if not found
-    if (tree.length === 0) {
-        return textResponse(`Requirement "${id}" not found`);
-    }
-    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}", {
-        cwd: project.path,
-        absolute: true,
-        ignore: ["**/node_modules/**", "**/dist/**", "**/build/**"],
-    });
-    const matchingFiles = findFilesWithRequirement(testFiles, id);
-    const testCodeSections = [];
-    for (const file of matchingFiles) {
-        const testRefs = findTestCodeForRequirement(file, id);
-        // Deduplicate by removing nested blocks - keep only outermost blocks
-        const deduplicated = testRefs.filter((ref, i) => {
-            // Check if this ref is contained within any other ref
-            const isNested = testRefs.some((other, j) => {
-                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 !isNested;
-        });
-        for (const ref of deduplicated) {
-            testCodeSections.push(`**${ref.requirementId}** tested in \`${ref.file}:${ref.startLine}-${ref.endLine}\`:\n\n\`\`\`typescript\n${ref.code}\n\`\`\``);
-        }
-    }
-    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.";
-    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

@@ -1,28 +0,0 @@
-/**
- * MCP Tool Handlers
- *
- * Each handler is a pure function that processes tool arguments
- * and returns an MCP response. Handlers receive a context object
- * that provides access to shared dependencies.
- */
-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

package/dist/mcp/handlers/index.js

@@ -1,19 +0,0 @@
-/**
- * MCP Tool Handlers
- *
- * Each handler is a pure function that processes tool arguments
- * and returns an MCP response. Handlers receive a context object
- * that provides access to shared dependencies.
- */
-export { handleCreateRequirementDocument, handleValidateRequirements, } from "./authoring.js";
-// Handlers
-export { handleDebugMcpEnvironment } from "./debug.js";
-export { handleGetRequirement } from "./get.js";
-export { handleList } from "./list.js";
-export { handlePushRequirements } from "./push.js";
-export { handleReport } from "./report.js";
-export { handleReviewTest, handleStyleCheck } from "./review.js";
-export { handleSearchRequirements } from "./search.js";
-export { handleGetRequirementsByTest, handleGetTestsByRequirement, } from "./test-mapping.js";
-export { errorResponse, textResponse } from "./types.js";
-//# sourceMappingURL=index.js.map

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

@@ -1,7 +0,0 @@
-import type { HandlerContext, ToolResponse } from "./types.js";
-export interface ListArgs {
-    untested?: boolean;
-    projectId?: string;
-}
-export declare function handleList(args: ListArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=list.d.ts.map

package/dist/mcp/handlers/list.js

@@ -1,43 +0,0 @@
-import { getReferencedRequirementIds } from "../../requirements/grep.js";
-import { textResponse } from "./types.js";
-export async function handleList(args, context) {
-    const { untested = false, projectId } = args;
-    const project = await context.getProjectFromDiscovery(projectId);
-    const requirements = await context.getRequirements(projectId);
-    if (requirements.length === 0) {
-        return textResponse(`No requirements found in project: ${project.path}\n\nMake sure .requirements/ directory exists with Markdown files (*.requirements.md).`);
-    }
-    if (untested) {
-        return formatUntested(requirements, project.path);
-    }
-    return formatAll(requirements);
-}
-function formatAll(requirements) {
-    const grouped = new Map();
-    for (const req of requirements) {
-        const existing = grouped.get(req.rootId) || [];
-        existing.push(req);
-        grouped.set(req.rootId, existing);
-    }
-    const formatted = Array.from(grouped.entries())
-        .map(([rootId, reqs]) => {
-        const root = reqs.find((r) => r.path.length === 0);
-        const childCount = reqs.length - 1;
-        return `- **${rootId}**: ${root?.content || "(no content)"} (${childCount} children)`;
-    })
-        .join("\n");
-    return textResponse(`Found ${grouped.size} requirement(s) with ${requirements.length} total nodes:\n\n${formatted}`);
-}
-async function formatUntested(requirements, projectPath) {
-    const referencedIds = await getReferencedRequirementIds(projectPath);
-    const rootRequirements = requirements.filter((r) => r.path.length === 0);
-    const untested = rootRequirements.filter((r) => !referencedIds.has(r.id));
-    if (untested.length === 0) {
-        return textResponse(`All ${rootRequirements.length} requirement(s) have test references — coverage is complete.`);
-    }
-    const formatted = untested
-        .map((r) => `- **${r.id}**: ${r.content}`)
-        .join("\n");
-    return textResponse(`Found ${untested.length} untested requirement(s) out of ${rootRequirements.length} total:\n\n${formatted}`);
-}
-//# sourceMappingURL=list.js.map

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

@@ -1,26 +0,0 @@
-/**
- * Push handler for MCP tools
- *
- * Provides requirements push functionality:
- * - push_requirements: Push local requirements to cloud
- */
-import type { HandlerContext, ToolResponse } from "./types.js";
-/**
- * Arguments for push_requirements tool
- */
-export interface PushRequirementsArgs {
-    filePath?: string;
-    confirmed?: boolean;
-    projectId?: string;
-}
-/**
- * Handler for push_requirements tool
- *
- * Requirements covered:
- * - MCP-PUSH-1.0: When not confirmed, no changes are made and a preview of creates/updates is returned
- * - MCP-PUSH-1.1: When confirmed is true, the push executes and returns success message
- * - MCP-PUSH-1.2: When credentials are missing or invalid, an error explains how to authenticate
- * - MCP-PUSH-1.3: When filePath is provided, only that file is pushed (MCP-PUSH-1.3.0: missing file is an error)
- */
-export declare function handlePushRequirements(args: PushRequirementsArgs, context: HandlerContext): Promise<ToolResponse>;
-//# sourceMappingURL=push.d.ts.map