@popoverai/dotrequirements 0.22.0 → 0.24.0

package/dist/schema/schemas.js

@@ -2,8 +2,8 @@
  * Zod schemas for Markdown requirements format.
  * TypeScript types are inferred from these schemas using z.infer<>.
  */
-import { z } from 'zod';
-import { fromZodError } from 'zod-validation-error';
+import { z } from "zod";
+import { fromZodError } from "zod-validation-error";
 // =============================================================================
 // Prefix and Key Validation
 // =============================================================================
@@ -24,21 +24,21 @@ export const REQUIREMENT_KEY_PATTERN = /^[A-Z][A-Z-]*-[0-9]+$/;
  */
 export const RequirementPrefixSchema = z
     .string()
-    .min(1, 'Prefix must be at least 1 character')
-    .max(30, 'Prefix must be at most 30 characters')
+    .min(1, "Prefix must be at least 1 character")
+    .max(30, "Prefix must be at most 30 characters")
     .transform((val) => val.toUpperCase())
-    .refine((val) => REQUIREMENT_PREFIX_PATTERN.test(val), 'Prefix must start with a letter and contain only uppercase letters and hyphens');
+    .refine((val) => REQUIREMENT_PREFIX_PATTERN.test(val), "Prefix must start with a letter and contain only uppercase letters and hyphens");
 /**
  * Zod schema for requirement key (PREFIX-number).
  * Normalizes to uppercase and strips leading zeros from numbers.
  */
 export const RequirementKeySchema = z
     .string()
-    .refine((val) => REQUIREMENT_KEY_PATTERN.test(val.toUpperCase()), 'Key must be in format PREFIX-number (e.g., LOGIN-1, AUTH-42)')
+    .refine((val) => REQUIREMENT_KEY_PATTERN.test(val.toUpperCase()), "Key must be in format PREFIX-number (e.g., LOGIN-1, AUTH-42)")
     .transform((val) => {
     const upper = val.toUpperCase();
     // Normalize leading zeros: LOGIN-01 -> LOGIN-1, LOGIN-007 -> LOGIN-7
-    return upper.replace(/-0+(\d+)$/, '-$1');
+    return upper.replace(/-0+(\d+)$/, "-$1");
 });
 /**
  * Normalize a prefix to uppercase.
@@ -54,8 +54,9 @@ export function normalizePrefix(prefix) {
 export function validatePrefix(prefix) {
     const result = RequirementPrefixSchema.safeParse(prefix);
     if (!result.success) {
+        // biome-ignore lint/suspicious/noExplicitAny: zod-validation-error and our zod v3 ZodError have a typing mismatch across versions; the runtime shape is identical.
         const validationError = fromZodError(result.error);
-        throw new ValidationError(`Invalid prefix "${prefix}": ${validationError.message}`, 'prefix', result.error);
+        throw new ValidationError(`Invalid prefix "${prefix}": ${validationError.message}`, "prefix", result.error);
     }
     return result.data;
 }
@@ -66,8 +67,9 @@ export function validatePrefix(prefix) {
 export function validateKey(key) {
     const result = RequirementKeySchema.safeParse(key);
     if (!result.success) {
+        // biome-ignore lint/suspicious/noExplicitAny: zod-validation-error and our zod v3 ZodError have a typing mismatch across versions; the runtime shape is identical.
         const validationError = fromZodError(result.error);
-        throw new ValidationError(`Invalid key "${key}": ${validationError.message}`, 'key', result.error);
+        throw new ValidationError(`Invalid key "${key}": ${validationError.message}`, "key", result.error);
     }
     return result.data;
 }
@@ -93,10 +95,10 @@ export function parseRequirementKey(key) {
 export function buildRequirementKey(prefix, number) {
     const normalizedPrefix = prefix.toUpperCase();
     if (!REQUIREMENT_PREFIX_PATTERN.test(normalizedPrefix)) {
-        throw new ValidationError(`Invalid prefix "${prefix}": must match pattern ${REQUIREMENT_PREFIX_PATTERN}`, 'prefix');
+        throw new ValidationError(`Invalid prefix "${prefix}": must match pattern ${REQUIREMENT_PREFIX_PATTERN}`, "prefix");
     }
     if (number < 0 || !Number.isInteger(number)) {
-        throw new ValidationError(`Invalid number "${number}": must be a non-negative integer`, 'number');
+        throw new ValidationError(`Invalid number "${number}": must be a non-negative integer`, "number");
     }
     return `${normalizedPrefix}-${number}`;
 }
@@ -110,11 +112,13 @@ export function buildRequirementKey(prefix, number) {
 export const MetadataSchema = z.object({
     version: z.number().optional(), // Informational - incremented on push
     pulledAt: z.string().optional(), // ISO 8601 timestamp - used for conflict detection
-    document: z.object({
+    document: z
+        .object({
         id: z.string().optional(), // Cloud document link - filled by push when creating
         title: z.string(), // Required for push
         defaultPrefix: z.string().optional(), // Editor hint for new requirement keys
-    }).optional(),
+    })
+        .optional(),
 });
 // =============================================================================
 // Push Readiness Validation
@@ -135,31 +139,31 @@ export function validateForPush(metadata) {
     if (!metadata.document) {
         return {
             valid: false,
-            reason: 'Missing document section. Add a document section with a title to push this file.'
+            reason: "Missing document section. Add a document section with a title to push this file.",
         };
     }
     // Must have title
-    if (!metadata.document.title || metadata.document.title.trim() === '') {
+    if (!metadata.document.title || metadata.document.title.trim() === "") {
         return {
             valid: false,
-            reason: 'Document section missing required title.'
+            reason: "Document section missing required title.",
         };
     }
     // Check document.id
     if (!metadata.document.id) {
         // No ID = create new document
-        return { valid: true, action: 'create' };
+        return { valid: true, action: "create" };
     }
     // Has ID - check if it's a valid Convex ID
     if (CONVEX_ID_PATTERN.test(metadata.document.id)) {
         // Valid Convex ID = update existing document
-        return { valid: true, action: 'update' };
+        return { valid: true, action: "update" };
     }
     // Invalid ID format - will create new document and overwrite
     return {
         valid: true,
-        action: 'create',
-        warning: `Invalid document ID '${metadata.document.id}' will be replaced with a new ID.`
+        action: "create",
+        warning: `Invalid document ID '${metadata.document.id}' will be replaced with a new ID.`,
     };
 }
 /**
@@ -172,31 +176,37 @@ export const RequirementNodeSchema = z.lazy(() => z.object({
     content: z.string(), // The actual requirement text
     children: z.array(RequirementNodeSchema).default([]),
     // Optional metadata preserved from Convex
-    metadata: z.object({
+    metadata: z
+        .object({
         convexId: z.string().optional(), // Convex _id
         rootId: z.string().optional(), // Convex rootId
         position: z.string().optional(), // Convex position path
         updatedAt: z.number().optional(),
-        externalLinks: z.object({
+        externalLinks: z
+            .object({
             jira: z.string().optional(),
             notion: z.string().optional(),
-        }).optional(),
+        })
+            .optional(),
         // New schema fields for bidirectional sync
         prefix: z.string().optional(), // e.g., "REQ"
         index: z.number().optional(), // e.g., 123
         documentId: z.string().optional(), // Convex document ID
-    }).optional(),
+    })
+        .optional(),
 }));
 /**
  * Complete requirements file structure.
  * Top-level keys are either "_meta" or requirement IDs.
  */
-export const RequirementsFileSchema = z.object({
+export const RequirementsFileSchema = z
+    .object({
     _meta: MetadataSchema,
     // All other keys are requirement roots
     // We'll validate the structure separately since Zod doesn't handle
     // arbitrary keys with specific structure well
-}).passthrough(); // Allow additional keys
+})
+    .passthrough(); // Allow additional keys
 /**
  * Parsed criterion from Markdown (position. Label: content format)
  * Example: "0. Given: user has valid credentials"
@@ -216,7 +226,7 @@ export class ValidationError extends Error {
         super(message);
         this.path = path;
         this.cause = cause;
-        this.name = 'ValidationError';
+        this.name = "ValidationError";
     }
 }
 /**
@@ -225,8 +235,9 @@ export class ValidationError extends Error {
 export function validateMetadata(data) {
     const result = MetadataSchema.safeParse(data);
     if (!result.success) {
+        // biome-ignore lint/suspicious/noExplicitAny: zod-validation-error and our zod v3 ZodError have a typing mismatch across versions; the runtime shape is identical.
         const validationError = fromZodError(result.error);
-        throw new ValidationError(`Invalid metadata block:\n${validationError.message}`, '_meta', result.error);
+        throw new ValidationError(`Invalid metadata block:\n${validationError.message}`, "_meta", result.error);
     }
     return result.data;
 }
@@ -236,6 +247,7 @@ export function validateMetadata(data) {
 export function validateRequirementNode(data, path) {
     const result = RequirementNodeSchema.safeParse(data);
     if (!result.success) {
+        // biome-ignore lint/suspicious/noExplicitAny: zod-validation-error and our zod v3 ZodError have a typing mismatch across versions; the runtime shape is identical.
         const validationError = fromZodError(result.error);
         throw new ValidationError(`Invalid requirement node structure at ${path}:\n${validationError.message}`, path, result.error);
     }
@@ -247,6 +259,7 @@ export function validateRequirementNode(data, path) {
 export function validateRequirementsFile(data) {
     const result = RequirementsFileSchema.safeParse(data);
     if (!result.success) {
+        // biome-ignore lint/suspicious/noExplicitAny: zod-validation-error and our zod v3 ZodError have a typing mismatch across versions; the runtime shape is identical.
         const validationError = fromZodError(result.error);
         throw new ValidationError(`Invalid requirements file structure:\n${validationError.message}`, undefined, result.error);
     }

package/dist/schema/test-schema.js

@@ -1,59 +1,59 @@
 /**
  * Quick test to verify the new YAML schema is valid and round-trips correctly.
  */
-import { buildRequirementsMarkdown, parseRequirementsFile, buildMetadata } from './index.js';
+import { buildMetadata, buildRequirementsMarkdown, parseRequirementsFile, } from "./index.js";
 // Create test data
 const metadata = buildMetadata(1);
 const testRequirements = [
     {
-        id: 'REQ123',
-        label: 'requirement',
-        content: 'User can authenticate',
+        id: "REQ123",
+        label: "requirement",
+        content: "User can authenticate",
         children: [
             {
-                id: 'REQ123.0',
-                label: 'given',
-                content: 'user has valid credentials',
+                id: "REQ123.0",
+                label: "given",
+                content: "user has valid credentials",
                 children: [],
             },
             {
-                id: 'REQ123.1',
-                label: 'when',
-                content: 'user submits login form',
+                id: "REQ123.1",
+                label: "when",
+                content: "user submits login form",
                 children: [
                     {
-                        id: 'REQ123.1.0',
-                        label: 'then',
-                        content: 'system validates credentials',
+                        id: "REQ123.1.0",
+                        label: "then",
+                        content: "system validates credentials",
                         children: [],
                     },
                     {
-                        id: 'REQ123.1.1',
-                        label: 'then',
-                        content: 'system creates session',
+                        id: "REQ123.1.1",
+                        label: "then",
+                        content: "system creates session",
                         children: [],
                     },
                 ],
             },
             {
-                id: 'REQ123.2',
-                label: 'then',
-                content: 'user is redirected to dashboard',
+                id: "REQ123.2",
+                label: "then",
+                content: "user is redirected to dashboard",
                 children: [],
             },
         ],
     },
 ];
-console.log('=== Building Markdown ===\n');
+console.log("=== Building Markdown ===\n");
 const markdown = buildRequirementsMarkdown(metadata, testRequirements);
 console.log(markdown);
-console.log('\n=== Parsing Markdown back ===\n');
+console.log("\n=== Parsing Markdown back ===\n");
 try {
     const { metadata: parsedMeta, requirements: parsedReqs } = parseRequirementsFile(markdown);
-    console.log('Metadata:', JSON.stringify(parsedMeta, null, 2));
-    console.log('\nRequirements tree:');
+    console.log("Metadata:", JSON.stringify(parsedMeta, null, 2));
+    console.log("\nRequirements tree:");
     function printTree(node, indent = 0) {
-        const spaces = '  '.repeat(indent);
+        const spaces = "  ".repeat(indent);
         console.log(`${spaces}${node.id}: ${node.label} → ${node.content}`);
         for (const child of node.children) {
             printTree(child, indent + 1);
@@ -62,9 +62,9 @@ try {
     for (const req of parsedReqs) {
         printTree(req);
     }
-    console.log('\n✅ Round-trip successful!');
+    console.log("\n✅ Round-trip successful!");
     // Verify structure
-    console.log('\n=== Verifying structure ===');
+    console.log("\n=== Verifying structure ===");
     const req = parsedReqs[0];
     console.log(`Root ID: ${req.id}`);
     console.log(`Root label: ${req.label}`);
@@ -75,7 +75,7 @@ try {
     console.log(`First grandchild ID: ${req.children[1].children[0].id}`);
 }
 catch (error) {
-    console.error('❌ Failed to parse Markdown:', error);
+    console.error("❌ Failed to parse Markdown:", error);
     process.exit(1);
 }
 //# sourceMappingURL=test-schema.js.map

package/dist/templates/context-file-section.md

@@ -47,7 +47,7 @@ test(requirement('REQ-ID.0'), () => { /* test specific criterion */ });
 ### MCP Tools
 
 **Exploration:**
-- `list_all_requirements` - Overview of all requirements
+- `list_requirements` - Overview of all requirements (set `untested: true` to filter to coverage gaps)
 - `get_requirement` - Requirement tree with test coverage
 - `search_requirements` - Search by text/regex
 
@@ -59,5 +59,6 @@ test(requirement('REQ-ID.0'), () => { /* test specific criterion */ });
 
 **Testing:**
 - `get_requirements_by_test` - See requirements a test file covers
-- `list_untested_requirements` - Find gaps in coverage
+- `list_requirements` (with `untested: true`) - Find requirements without tests
+- `report_coverage` - Get test coverage from local cache or cloud
 - `review_test` - Validate tests match requirement intent

package/dist/templates/example-requirements.js

@@ -4,7 +4,7 @@
  * This template is used for both local-only and authenticated init flows.
  * It demonstrates the dotrequirements markdown format with nested requirements.
  */
-export function generateExampleRequirements(projectId = 'local') {
+export function generateExampleRequirements(projectId = "local") {
     const now = new Date().toISOString();
     return `---
 projectId: ${projectId}

package/dist/templates/example-requirements.ts

@@ -4,7 +4,9 @@
  * This template is used for both local-only and authenticated init flows.
  * It demonstrates the dotrequirements markdown format with nested requirements.
  */
-export function generateExampleRequirements(projectId: string = 'local'): string {
+export function generateExampleRequirements(
+  projectId: string = "local",
+): string {
   const now = new Date().toISOString();
 
   return `---

package/dist/templates/requirements-readme.js

@@ -23,7 +23,7 @@ Requirements use the \`*.requirements.md\` naming pattern. See the [Requirements
 
 - \`dotrequirements pull\` - Sync requirements from cloud
 - \`dotrequirements push\` - Push local requirements to cloud
-- \`dotrequirements test\` - Validate requirement files
+- \`dotrequirements validate\` - Validate requirement files
 
 Learn more: https://dotrequirements.io
 `;

package/dist/templates/requirements-readme.ts

@@ -23,7 +23,7 @@ Requirements use the \`*.requirements.md\` naming pattern. See the [Requirements
 
 - \`dotrequirements pull\` - Sync requirements from cloud
 - \`dotrequirements push\` - Push local requirements to cloud
-- \`dotrequirements test\` - Validate requirement files
+- \`dotrequirements validate\` - Validate requirement files
 
 Learn more: https://dotrequirements.io
 `;

package/dist/templates/skills/codebase-to-spec/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: codebase-to-spec
+description: Generate dotrequirements behavioral specifications from a codebase. Use this when the user wants to capture what an existing codebase does as a set of testable behavioral requirements — e.g. for legacy systems, third-party libraries, or before refactoring.
+---
+
+# Codebase to Spec
+
+You are a thin conversational wrapper around the `dotrequirements cts run` CLI. **You do not implement any pipeline logic yourself.** The CLI handles packing, planning, fan-out parallelism, retry, resumability, review loops, and presentation. Your job is to:
+
+1. Confirm the user's scope.
+2. Run the CLI via the Bash tool.
+3. Narrate progress as the CLI emits it.
+4. Surface the final summary and residual notes.
+5. Offer sensible follow-ups (push to cloud, re-run, narrow scope, etc.).
+
+## When this skill is right
+
+Use it when the user wants behavioral requirements *from* code that already exists. Typical phrasings:
+- "Generate requirements from this codebase"
+- "Capture the behavior of this library"
+- "I want a behavioral spec for the auth module"
+- "Document what this service does"
+
+Do **not** use it for:
+- New feature design (use `dotreq-requirements` / the capture flow instead)
+- Bug investigation
+- Code review
+
+## Workflow
+
+### Step 1 — Confirm scope
+
+If the user passed a scope argument (e.g. a path like `src/auth`), use it. Otherwise, ask one concise question:
+
+> "Which part of the codebase should I spec? You can give me a path (e.g. `src/auth`) or say 'the whole thing'."
+
+Whole-codebase runs are fine for small repos. For larger ones, encourage scoping to a single area — the CLI will tell you if the working-context budget is exceeded.
+
+### Step 2 — Run the CLI
+
+Invoke the pipeline via Bash. The command is:
+
+```bash
+dotrequirements cts run --scope <PATH> --non-interactive
+```
+
+Flags:
+- `--scope <path>` — limit packing to a subdirectory. Omit for the whole repo.
+- `--non-interactive` — important: you're running in an agentic context, so prompts won't work.
+- `--overwrite` — replace existing `.requirements/*.requirements.md` files.
+- `--skip-existing` — leave existing files untouched.
+- `--fresh` — clear the cache before running (use only if a previous run is corrupt).
+
+Default to `--non-interactive`. Decide between `--overwrite` and `--skip-existing` based on what the user wants if there are existing `.requirements/` files; otherwise neither flag is needed (the default `fail-fast` policy will surface conflicts).
+
+### Step 3 — Narrate progress
+
+The CLI emits lines like:
+
+```
+[CTS] pack/done Packed 16 files → ... (compressed), ... (uncompressed)
+[CTS] plan/done Plan loop converged at turn 1 with verdict: approved-with-revisions
+[CTS] specify/summary Completed: 7 / Skipped (resume): 0 / Failed: 0
+[CTS] spec-review/done Edit loop converged at turn 1 with verdict: approved-with-revisions
+[CTS] present/created created: .../sample.requirements.md
+```
+
+Surface these to the user in conversational form as they appear. **Do not invent progress claims** — narrate only what the CLI has actually emitted. If the CLI is silent for a long stretch (specifier fan-out can take minutes), a single reassuring note ("still working — the specifier fan-out runs in parallel and takes a few minutes for larger areas") is fine. Don't repeat it.
+
+### Step 4 — Surface the final summary
+
+When the CLI finishes successfully, it prints a "Pipeline summary:" block with:
+- total areas
+- total top-level requirements
+- outline review turns and verdict
+- specifier completion count
+- spec review turns and verdict
+- the list of output files written
+- residual notes (issues the reviewer flagged in `approved-with-revisions` outcomes)
+
+Present that summary back to the user. **Highlight the residual notes** prominently — these are concerns the reviewer wanted the human to verify. Common categories:
+- `outline.coverage_gap` — files the planner didn't assign to any area
+- `spec.coverage_gap` — behaviors the spec missed
+- `spec.framing_error` — requirements written as guidance/explanation rather than observable behavior
+- `spec.cross_area` — duplication across areas
+- `spec.internal_mechanics` — internal vocabulary that leaked into a user-facing spec
+
+### Step 5 — Offer follow-ups
+
+After surfacing the summary, ask the user what they want next. Useful options:
+
+- **Push to cloud** — `dotrequirements push` syncs the generated `.requirements/*.requirements.md` files to dotrequirements cloud. Only suggest this if the user has a cloud account (you can check by reading `.dotrequirements/config.json` or asking).
+- **Refine a specific area** — re-run `dotrequirements cts specify-area "<name>"` for one area, optionally with `--model <name>` for a stronger model.
+- **Refine the whole spec** — re-run `dotrequirements cts edit-loop` to iterate on the composed spec.
+- **Narrow the scope** — re-run with a smaller `--scope`.
+- **Hand-edit** — the output files are plain Markdown; the user can edit them directly.
+
+## Failure handling
+
+The CLI uses stable exit codes (see `dotrequirements cts run --help`). Common cases:
+
+- **Exit code 10 (BudgetExceeded)** — the codebase is too large for a single agent's context window after compression. Explain this in plain language and offer to retry with a narrower `--scope`.
+- **Exit code 11 (MaxTurnsHit)** — a review loop hit its cap without converging. The CLI still writes the latest artifact; surface the residual review and ask the user whether to ship it, re-run the stage (`dotrequirements cts edit-loop`), or hand-edit.
+- **Exit code 12 (OverwriteRefused)** — existing `.requirements/` files would be overwritten in non-interactive mode. Offer `--overwrite` or `--skip-existing`.
+- **Exit code 3 (StageFailed)** — a stage errored. Read stderr for details. Offer: resume (re-run the same command — the cache means earlier stages are skipped), restart fresh (`--fresh`), or investigate (read files in `.dotrequirements-cache/`).
+- **Any other non-zero exit** — surface stderr verbatim, then offer the same three options.
+
+## What you must NOT do
+
+- Don't try to generate requirements yourself; always use the CLI.
+- Don't paraphrase or summarize the CLI's progress lines in ways that change their meaning.
+- Don't claim the pipeline did something it didn't (e.g. don't say "the reviewer approved this" if the verdict was `approved-with-revisions`).
+- Don't push to cloud without asking — `dotrequirements push` is a destructive sync.
+- Don't suggest editing files inside `.dotrequirements-cache/`; that's internal CLI state.
+
+## Host portability
+
+This skill makes no assumptions about subagent mechanisms, Task tools, or framework-specific features. Its only host requirements are: Agent Skills format support, a Bash tool (or equivalent shell-out), and `dotrequirements` installed on the user's machine.

package/dist/utils/brand.js

@@ -1,8 +1,8 @@
-import chalk from 'chalk';
+import chalk from "chalk";
 // Cyan color: rgb(8, 145, 178)
 const bulletColor = chalk.rgb(8, 145, 178);
 /** Branded name for terminal output (colored bullet) */
-export const brand = `dot${bulletColor('•')}requirements`;
+export const brand = `dot${bulletColor("•")}requirements`;
 /** Branded name for plain text (MCP descriptions, etc) */
-export const brandPlain = 'dot•requirements';
+export const brandPlain = "dot•requirements";
 //# sourceMappingURL=brand.js.map

package/dist/utils/browser-launch.js

@@ -6,7 +6,7 @@
  * Uses the `open` npm package for secure, cross-platform browser launching
  * without shell command injection vulnerabilities.
  */
-import open from 'open';
+import open from "open";
 /**
  * Open a URL in the user's default browser
  *
@@ -26,10 +26,10 @@ export async function openBrowser(url) {
 export async function openBrowserWithFallback(url) {
     try {
         await openBrowser(url);
-        console.log('Opening browser for authentication...');
+        console.log("Opening browser for authentication...");
     }
-    catch (error) {
-        console.error('Could not automatically open browser.');
+    catch {
+        console.error("Could not automatically open browser.");
         console.log(`\nPlease open this URL in your browser manually:\n${url}\n`);
     }
 }

package/dist/utils/context-file.d.ts

@@ -28,7 +28,7 @@ export declare function wrapInSectionMarkers(content: string): string;
  * Returns: { action: 'created' | 'appended' | 'updated', existingContent?: string }
  */
 export declare function appendOrUpdateSection(filePath: string, sectionContent: string): {
-    action: 'created' | 'appended' | 'updated';
+    action: "created" | "appended" | "updated";
     existingContent?: string;
 };
 /**

package/dist/utils/context-file.js

@@ -1,17 +1,17 @@
-import { readFileSync, writeFileSync, existsSync } from 'fs';
-import { join, dirname } from 'path';
-import { findUp } from 'find-up';
-const SECTION_START = '<!-- dotrequirements:start -->';
-const SECTION_END = '<!-- dotrequirements:end -->';
+import { existsSync, readFileSync, writeFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { findUp } from "find-up";
+const SECTION_START = "<!-- dotrequirements:start -->";
+const SECTION_END = "<!-- dotrequirements:end -->";
 /**
  * Platform to context file mapping
  */
 const PLATFORM_CONTEXT_FILES = {
-    'claude-code': 'CLAUDE.md',
-    'cursor': 'AGENTS.md',
-    'codex': 'AGENTS.md',
-    'github-copilot': 'AGENTS.md',
-    'antigravity': 'GEMINI.md',
+    "claude-code": "CLAUDE.md",
+    cursor: "AGENTS.md",
+    codex: "AGENTS.md",
+    "github-copilot": "AGENTS.md",
+    antigravity: "GEMINI.md",
 };
 /**
  * Get the appropriate context file name for a platform
@@ -23,7 +23,7 @@ export function getContextFileName(platform) {
  * Find the git root directory
  */
 export async function findGitRoot() {
-    const gitDir = await findUp('.git', { type: 'directory' });
+    const gitDir = await findUp(".git", { type: "directory" });
     return gitDir ? dirname(gitDir) : null;
 }
 /**
@@ -61,23 +61,23 @@ export function appendOrUpdateSection(filePath, sectionContent) {
     const wrappedContent = wrapInSectionMarkers(sectionContent);
     if (!existsSync(filePath)) {
         // Create new file with just the section
-        writeFileSync(filePath, wrappedContent + '\n', 'utf-8');
-        return { action: 'created' };
+        writeFileSync(filePath, `${wrappedContent}\n`, "utf-8");
+        return { action: "created" };
     }
-    const existingFile = readFileSync(filePath, 'utf-8');
+    const existingFile = readFileSync(filePath, "utf-8");
     const existingSection = findDotrequirementsSection(existingFile);
     if (!existingSection) {
         // Append section to end of file
-        const separator = existingFile.endsWith('\n') ? '\n' : '\n\n';
-        writeFileSync(filePath, existingFile + separator + wrappedContent + '\n', 'utf-8');
-        return { action: 'appended' };
+        const separator = existingFile.endsWith("\n") ? "\n" : "\n\n";
+        writeFileSync(filePath, `${existingFile + separator + wrappedContent}\n`, "utf-8");
+        return { action: "appended" };
     }
     // Replace existing section
     const newContent = existingFile.slice(0, existingSection.start) +
         wrappedContent +
         existingFile.slice(existingSection.end);
-    writeFileSync(filePath, newContent, 'utf-8');
-    return { action: 'updated', existingContent: existingSection.content };
+    writeFileSync(filePath, newContent, "utf-8");
+    return { action: "updated", existingContent: existingSection.content };
 }
 /**
  * Get the full path to the context file for a platform
@@ -102,12 +102,12 @@ export function buildNoGitRepoMessage(fileName) {
     return [
         `⚠️  Skipped writing ${fileName}: not inside a git repository.`,
         `   ${fileName} would have been created at the git repo root, but no .git directory was found.`,
-        '',
-        '   To finish setup, either:',
-        '     • run `git init` here, then re-run `dotreq mcp-setup`, or',
-        '     • `cd` into an existing project directory and run `dotreq mcp-setup` there.',
-        '',
-        '   Note: the MCP server itself was configured successfully — only the context file step was skipped.',
-    ].join('\n');
+        "",
+        "   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