@popoverai/dotrequirements 0.12.1 → 0.14.0

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

@@ -4,22 +4,36 @@ export interface SelectedProject {
     projectName: string;
     projectSlug: string | null;
 }
+export interface SelectedTeam {
+    teamId: string;
+    tier: string;
+}
 /**
  * Prompt user to select a team from their available teams.
- * Returns the team ID, or null if user cancels.
+ * Returns the team ID and tier, or null if user cancels.
  */
-export declare function selectTeam(client: ConvexHttpClient): Promise<string | null>;
+export declare function selectTeam(client: ConvexHttpClient): Promise<SelectedTeam | null>;
 /**
  * Prompt user to select a project from a team.
  * Returns the selected project info, or null if user cancels or no projects exist.
  */
 export declare function selectProject(client: ConvexHttpClient, teamId: string): Promise<SelectedProject | null>;
+export type ExpiryDays = 30 | 90 | 365;
 /**
  * Get or create a user-scoped secret for a project.
  * Returns the secret and whether it was newly created.
+ *
+ * @param expiryDays - Optional expiry duration for paid tier users (30/90/365 days)
+ *                     Free tier always gets 30 days regardless of this parameter.
  */
-export declare function getOrCreateProjectSecret(client: ConvexHttpClient, projectId: string): Promise<{
+export declare function getOrCreateProjectSecret(client: ConvexHttpClient, projectId: string, expiryDays?: ExpiryDays): Promise<{
     secret: string;
     created: boolean;
+    expiresAt?: number;
 }>;
+/**
+ * Prompt paid-tier users for secret expiry duration.
+ * Returns undefined (use default) if user cancels.
+ */
+export declare function promptExpiryDays(tierSlug: string): Promise<ExpiryDays | undefined>;
 //# sourceMappingURL=project-selector.d.ts.map

package/dist/utils/project-selector.js

@@ -2,10 +2,12 @@ import { promptChoice } from './prompts.js';
 import { api } from '../convex.js';
 /**
  * Prompt user to select a team from their available teams.
- * Returns the team ID, or null if user cancels.
+ * Returns the team ID and tier, or null if user cancels.
  */
 export async function selectTeam(client) {
     console.log('Fetching your teams...\n');
+    // AUTH-24.0: Ensure user has a default team if they don't have any
+    await client.mutation(api.teams.mutations.ensureDefaultTeam, {});
     const teams = await client.query(api.teams.queries.listForUserWithUsage);
     if (teams.length === 0) {
         console.log('You are not a member of any teams.');
@@ -22,7 +24,14 @@ export async function selectTeam(client) {
         };
     });
     const selectedTeamId = await promptChoice('Select a team:', teamChoices);
-    return selectedTeamId ?? null;
+    if (!selectedTeamId) {
+        return null;
+    }
+    const selectedTeam = teams.find((t) => t.teamId === selectedTeamId);
+    return {
+        teamId: selectedTeamId,
+        tier: selectedTeam?.tier ?? 'free',
+    };
 }
 /**
  * Prompt user to select a project from a team.
@@ -59,11 +68,36 @@ export async function selectProject(client, teamId) {
 /**
  * Get or create a user-scoped secret for a project.
  * Returns the secret and whether it was newly created.
+ *
+ * @param expiryDays - Optional expiry duration for paid tier users (30/90/365 days)
+ *                     Free tier always gets 30 days regardless of this parameter.
  */
-export async function getOrCreateProjectSecret(client, projectId) {
+export async function getOrCreateProjectSecret(client, projectId, expiryDays) {
     const result = await client.mutation(api.projectSecrets.mutations.ensureOwnSecret, {
         target: { type: 'project', id: projectId },
+        expiryDays,
     });
     return result;
 }
+/**
+ * Prompt paid-tier users for secret expiry duration.
+ * Returns undefined (use default) if user cancels.
+ */
+export async function promptExpiryDays(tierSlug) {
+    // Free tier users don't get a choice - always 30 days
+    if (tierSlug === 'free') {
+        return undefined;
+    }
+    // AUTHZ-3.1, AUTHZ-3.2: Paid tier users can choose expiry
+    const choice = await promptChoice('How long should this secret be valid?', [
+        { title: '365 days (Recommended)', value: '365' },
+        { title: '90 days', value: '90' },
+        { title: '30 days', value: '30' },
+    ]);
+    // If user cancels, use default (365 for paid tier)
+    if (!choice) {
+        return 365;
+    }
+    return parseInt(choice, 10);
+}
 //# sourceMappingURL=project-selector.js.map

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

@@ -0,0 +1,47 @@
+/**
+ * Project credentials stored in project-settings.json
+ */
+export interface ProjectSettings {
+    projectId: string;
+    projectSecret: string;
+}
+/**
+ * Project status indicating whether it's connected to cloud
+ */
+export type ProjectStatus = 'cloud-connected' | 'local-only';
+/**
+ * Result of finding a project
+ */
+export interface ProjectInfo {
+    /** Absolute path to the project root (directory containing .requirements/) */
+    rootPath: string;
+    /** Whether the project has cloud credentials */
+    status: ProjectStatus;
+    /** Credentials if cloud-connected */
+    credentials?: ProjectSettings;
+}
+/**
+ * Find the project root by walking up from startDir looking for .requirements/ folder
+ * Returns the directory containing .requirements/, or undefined if not found
+ */
+export declare function findProjectRoot(startDir?: string): string | undefined;
+/**
+ * Read project settings from .requirements/project-settings.json
+ * Returns undefined if file doesn't exist, throws if file is invalid JSON
+ */
+export declare function readProjectSettings(projectRoot: string): ProjectSettings | undefined;
+/**
+ * Write project settings to .requirements/project-settings.json
+ * Creates .requirements/ directory if it doesn't exist
+ */
+export declare function writeProjectSettings(projectRoot: string, settings: ProjectSettings): void;
+/**
+ * Get project info including status and credentials
+ * Returns undefined if no project found
+ */
+export declare function getProjectInfo(startDir?: string): ProjectInfo | undefined;
+/**
+ * Get project credentials, throwing helpful error if not available
+ */
+export declare function getProjectCredentials(startDir?: string): ProjectSettings;
+//# sourceMappingURL=project-settings.d.ts.map

package/dist/utils/project-settings.js

@@ -0,0 +1,110 @@
+import * as fs from 'fs';
+import * as path from 'path';
+const REQUIREMENTS_DIR = '.requirements';
+const SETTINGS_FILE = 'project-settings.json';
+/**
+ * Find the project root by walking up from startDir looking for .requirements/ folder
+ * Returns the directory containing .requirements/, or undefined if not found
+ */
+export function findProjectRoot(startDir = process.cwd()) {
+    let currentDir = path.resolve(startDir);
+    const root = path.parse(currentDir).root;
+    while (currentDir !== root) {
+        const requirementsDir = path.join(currentDir, REQUIREMENTS_DIR);
+        if (fs.existsSync(requirementsDir) && fs.statSync(requirementsDir).isDirectory()) {
+            return currentDir;
+        }
+        currentDir = path.dirname(currentDir);
+    }
+    // Check root directory as well
+    const rootRequirementsDir = path.join(root, REQUIREMENTS_DIR);
+    if (fs.existsSync(rootRequirementsDir) && fs.statSync(rootRequirementsDir).isDirectory()) {
+        return root;
+    }
+    return undefined;
+}
+/**
+ * Read project settings from .requirements/project-settings.json
+ * Returns undefined if file doesn't exist, throws if file is invalid JSON
+ */
+export function readProjectSettings(projectRoot) {
+    const settingsPath = path.join(projectRoot, REQUIREMENTS_DIR, SETTINGS_FILE);
+    if (!fs.existsSync(settingsPath)) {
+        return undefined;
+    }
+    let content;
+    try {
+        content = fs.readFileSync(settingsPath, 'utf-8');
+    }
+    catch (err) {
+        throw new Error(`Could not read project-settings.json: ${err.message}`);
+    }
+    let parsed;
+    try {
+        parsed = JSON.parse(content);
+    }
+    catch (err) {
+        throw new Error(`project-settings.json is invalid: ${err.message}`);
+    }
+    if (typeof parsed !== 'object' ||
+        parsed === null ||
+        typeof parsed.projectId !== 'string' ||
+        typeof parsed.projectSecret !== 'string') {
+        throw new Error('project-settings.json is invalid: missing projectId or projectSecret');
+    }
+    return {
+        projectId: parsed.projectId,
+        projectSecret: parsed.projectSecret,
+    };
+}
+/**
+ * Write project settings to .requirements/project-settings.json
+ * Creates .requirements/ directory if it doesn't exist
+ */
+export function writeProjectSettings(projectRoot, settings) {
+    const requirementsDir = path.join(projectRoot, REQUIREMENTS_DIR);
+    const settingsPath = path.join(requirementsDir, SETTINGS_FILE);
+    // Create .requirements/ directory if needed
+    if (!fs.existsSync(requirementsDir)) {
+        fs.mkdirSync(requirementsDir, { recursive: true });
+    }
+    const content = JSON.stringify(settings, null, 2) + '\n';
+    fs.writeFileSync(settingsPath, content, 'utf-8');
+}
+/**
+ * Get project info including status and credentials
+ * Returns undefined if no project found
+ */
+export function getProjectInfo(startDir = process.cwd()) {
+    const rootPath = findProjectRoot(startDir);
+    if (!rootPath) {
+        return undefined;
+    }
+    let credentials;
+    try {
+        credentials = readProjectSettings(rootPath);
+    }
+    catch {
+        // Invalid settings file means local-only (credentials not usable)
+        credentials = undefined;
+    }
+    return {
+        rootPath,
+        status: credentials ? 'cloud-connected' : 'local-only',
+        credentials,
+    };
+}
+/**
+ * Get project credentials, throwing helpful error if not available
+ */
+export function getProjectCredentials(startDir = process.cwd()) {
+    const info = getProjectInfo(startDir);
+    if (!info) {
+        throw new Error('No dotrequirements project found. Run "dotrequirements init" to create one.');
+    }
+    if (!info.credentials) {
+        throw new Error('Project is not connected to cloud. Run "dotrequirements link" to connect.');
+    }
+    return info.credentials;
+}
+//# sourceMappingURL=project-settings.js.map

package/dist/utils/templates.d.ts

@@ -2,28 +2,4 @@
  * Load a template file and replace placeholders
  */
 export declare function loadTemplate(templateName: string, replacements?: Record<string, string>): string;
-/**
- * Load the behavioral core content (requirements capture guidance)
- */
-export declare function loadBehavioralCore(): string;
-/**
- * Load the test writing core content
- */
-export declare function loadTestWritingCore(): string;
-/**
- * Load the overview core content
- */
-export declare function loadOverviewCore(): string;
-/**
- * Load the requirements skill template with core content injected
- */
-export declare function loadPlatformTemplate(templateName: string): string;
-/**
- * Load the test writing skill template with core content injected
- */
-export declare function loadTestWritingTemplate(templateName: string): string;
-/**
- * Load the overview skill template with core content injected
- */
-export declare function loadOverviewTemplate(templateName: string): string;
 //# sourceMappingURL=templates.d.ts.map

package/dist/utils/templates.js

@@ -25,43 +25,4 @@ export function loadTemplate(templateName, replacements = {}) {
     }
     return content;
 }
-/**
- * Load the behavioral core content (requirements capture guidance)
- */
-export function loadBehavioralCore() {
-    return loadTemplate('behavioral-core.md');
-}
-/**
- * Load the test writing core content
- */
-export function loadTestWritingCore() {
-    return loadTemplate('test-writing-core.md');
-}
-/**
- * Load the overview core content
- */
-export function loadOverviewCore() {
-    return loadTemplate('overview-core.md');
-}
-/**
- * Load the requirements skill template with core content injected
- */
-export function loadPlatformTemplate(templateName) {
-    const behavioralCore = loadBehavioralCore();
-    return loadTemplate(templateName, { BEHAVIORAL_CORE: behavioralCore });
-}
-/**
- * Load the test writing skill template with core content injected
- */
-export function loadTestWritingTemplate(templateName) {
-    const testWritingCore = loadTestWritingCore();
-    return loadTemplate(templateName, { TEST_WRITING_CORE: testWritingCore });
-}
-/**
- * Load the overview skill template with core content injected
- */
-export function loadOverviewTemplate(templateName) {
-    const overviewCore = loadOverviewCore();
-    return loadTemplate(templateName, { OVERVIEW_CORE: overviewCore });
-}
 //# sourceMappingURL=templates.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@popoverai/dotrequirements",
-  "version": "0.12.1",
+  "version": "0.14.0",
   "description": "Requirements tracking CLI, test harness, and MCP server",
   "type": "module",
   "bin": {

package/dist/harness/localReporting.d.ts

@@ -1,6 +0,0 @@
-import { TrackedRequirement } from "./tracking.js";
-/**
- * Generate a simple console report showing which requirements were tested
- */
-export declare function reportLocalCoverage(trackedReqs?: Map<string, TrackedRequirement>): void;
-//# sourceMappingURL=localReporting.d.ts.map

package/dist/harness/localReporting.js

@@ -1,49 +0,0 @@
-import { getAllRequirements } from "./requirementsLoader.js";
-/**
- * Generate a simple console report showing which requirements were tested
- */
-export function reportLocalCoverage(trackedReqs) {
-    const allRequirements = getAllRequirements();
-    // If no tracked requirements provided, return empty report
-    if (!trackedReqs) {
-        trackedReqs = new Map();
-    }
-    const allRequirementKeys = Array.from(allRequirements.keys());
-    const testedKeys = Array.from(trackedReqs.keys());
-    const untestedKeys = allRequirementKeys.filter((key) => !trackedReqs.has(key));
-    const coverage = allRequirementKeys.length > 0
-        ? ((testedKeys.length / allRequirementKeys.length) * 100).toFixed(1)
-        : "0.0";
-    let report = "\n=== Requirements Coverage Report ===\n";
-    report += `\nTotal Requirements: ${allRequirementKeys.length}\n`;
-    report += `Tested Requirements: ${testedKeys.length}\n`;
-    report += `Untested Requirements: ${untestedKeys.length}\n`;
-    report += `Coverage: ${coverage}%\n`;
-    // Show tested requirements
-    if (testedKeys.length > 0) {
-        report += "\n✓ Tested Requirements:\n";
-        testedKeys.forEach((key) => {
-            const req = allRequirements.get(key);
-            const label = req?.label || "";
-            const content = req?.content || "";
-            const preview = content.length > 60 ? content.substring(0, 60) + "..." : content;
-            const labelPart = label ? ` (${label})` : "";
-            report += `  - ${key}${labelPart}: ${preview}\n`;
-        });
-    }
-    // Show untested requirements
-    if (untestedKeys.length > 0) {
-        report += "\n✗ Untested Requirements:\n";
-        untestedKeys.forEach((key) => {
-            const req = allRequirements.get(key);
-            const label = req?.label || "";
-            const content = req?.content || "";
-            const preview = content.length > 60 ? content.substring(0, 60) + "..." : content;
-            const labelPart = label ? ` (${label})` : "";
-            report += `  - ${key}${labelPart}: ${preview}\n`;
-        });
-    }
-    report += "\n====================================\n";
-    console.log(report);
-}
-//# sourceMappingURL=localReporting.js.map

package/dist/templates/antigravity-gemini.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-requirements -->
-{{BEHAVIORAL_CORE}}
-<!-- END dotreq-requirements -->

package/dist/templates/antigravity-overview-rule.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-overview -->
-{{OVERVIEW_CORE}}
-<!-- END dotreq-overview -->

package/dist/templates/antigravity-test-rule.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-tests -->
-{{TEST_WRITING_CORE}}
-<!-- END dotreq-tests -->

package/dist/templates/behavioral-core.md

@@ -1,25 +0,0 @@
-# Requirements Capture
-
-ALWAYS ask about capturing requirements when the user requests new functionality (not bug fixes or refactoring).
-
-Ask: "Should we capture what this should do before we build it?"
-
-If yes, use the MCP tools for requirements writing.
-
-## Workflow
-
-1. **Ask questions** only if there are major gaps in expected behavior
-2. **Use requirements as alignment** - Get assumptions on paper quickly instead of playing twenty questions
-3. **Think MVP** - Don't expand scope without consulting the user
-4. **After building** - Suggest testing against the requirements using the project's standard testing tools
-
-Be helpful, consultative, and encouraging; not obstructive.
-
-## MCP Tools for Requirements
-
-- `create_requirement_document` - Get template with codebase-aware format guidance and style principles
-- `validate_requirements` - Check syntax before pushing (works offline)
-- `style_check` - Get AI feedback on writing quality and clarity
-- `push_requirements` - Sync to cloud (shows diff preview, then confirms)
-
-Note: Users can also explicitly trigger this workflow with `/capture-requirements`.

package/dist/templates/claude-code-overview-skill.md

@@ -1,6 +0,0 @@
----
-name: dotreq-overview
-description: Use this to understand what the system is supposed to do. ALWAYS use it when exploring expected behavior.
----
-
-{{OVERVIEW_CORE}}

package/dist/templates/claude-code-skill.md

@@ -1,6 +0,0 @@
----
-name: dotreq-requirements
-description: Use this when adding new expected behavior to the system. ALWAYS use it when implementing new functionality.
----
-
-{{BEHAVIORAL_CORE}}

package/dist/templates/claude-code-test-skill.md

@@ -1,6 +0,0 @@
----
-name: dotreq-tests
-description: Use this when validating expected behavior. ALWAYS use it when writing tests.
----
-
-{{TEST_WRITING_CORE}}

package/dist/templates/codex-agents.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-requirements -->
-{{BEHAVIORAL_CORE}}
-<!-- END dotreq-requirements -->

package/dist/templates/codex-overview-agents.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-overview -->
-{{OVERVIEW_CORE}}
-<!-- END dotreq-overview -->

package/dist/templates/codex-test-agents.md

@@ -1,3 +0,0 @@
-<!-- BEGIN dotreq-tests -->
-{{TEST_WRITING_CORE}}
-<!-- END dotreq-tests -->

package/dist/templates/cursor-overview-rule.mdc

@@ -1,5 +0,0 @@
----
-description: Use this to understand what the system is supposed to do. ALWAYS use it when exploring expected behavior.
----
-
-{{OVERVIEW_CORE}}

package/dist/templates/cursor-rule.mdc

@@ -1,5 +0,0 @@
----
-description: Use this when adding new expected behavior to the system. ALWAYS use it when implementing new functionality.
----
-
-{{BEHAVIORAL_CORE}}

package/dist/templates/cursor-test-rule.mdc

@@ -1,5 +0,0 @@
----
-description: Use this when validating expected behavior. ALWAYS use it when writing tests.
----
-
-{{TEST_WRITING_CORE}}

package/dist/templates/overview-core.md

@@ -1,27 +0,0 @@
-# Understanding Expected Behavior
-
-ALWAYS use this when you want to understand what the system is supposed to do.
-
-## Where to Find Expected Behavior
-
-This project uses **requirements as the source of truth** for expected behavior.
-
-**Location:** `.requirements/` directory contains `*.requirements.md` files
-
-**Format:** Requirements are structured as:
-- Requirement IDs (e.g., `AUTH-1`, `LOGIN-2`)
-- Descriptions of expected behavior
-- Hierarchical structure (parent requirements with child criteria)
-
-## MCP Tools for Exploration
-
-- `list_all_requirements` - Get overview of all requirements in the project
-- `get_requirement` - Get detailed requirement tree with test coverage
-- `search_requirements` - Search by text/regex across all requirements
-- `get_requirements_by_test` - See what a test file validates
-
-## Next Steps
-
-Once you understand the expected behavior:
-- **Adding new behavior?** Use the `dotreq-requirements` skill
-- **Writing tests?** Use the `dotreq-tests` skill

package/dist/templates/test-writing-core.md

@@ -1,72 +0,0 @@
-# Test Writing with Requirements
-
-ALWAYS use this guidance when writing tests based on requirements.
-
-## Core Principle
-
-Use `requirement()` AS the test description, not in the body or comments.
-
-```typescript
-// ✅ Good
-test(requirement('AUTH-1'), () => { /* test */ });
-
-// ❌ Bad
-test("user can log in", () => { requirement('AUTH-1'); });
-```
-
-## Test Structure
-
-**Match the requirement hierarchy:**
-
-For structured requirements, nest describe/it blocks:
-
-```typescript
-describe(requirement('LOGIN-1'), () => {
-  describe(requirement('LOGIN-1.given'), () => {
-    // Arrange
-  });
-  describe(requirement('LOGIN-1.when'), () => {
-    // Act
-    it(requirement('LOGIN-1.then'), () => {
-      // Assert
-    });
-  });
-});
-```
-
-For simple requirements, use a single test block.
-
-## Comments
-
-Comments should describe the TEST implementation, not copy the requirement text verbatim.
-
-**NEVER document coverage in comments.** Our MCP tools track coverage automatically.
-
-```typescript
-// ❌ Bad - creates second source of truth
-/**
- * Requirements coverage:
- * - AUTH-9.0: Backend creates project ✓
- * - AUTH-9.1: CLI writes to .env.local ✓
- */
-
-// ✅ Good - use MCP tools instead
-// Use get_requirement, get_requirements_by_test to see coverage
-```
-
-## Workflow
-
-After writing tests:
-
-1. Run tests to ensure they don't throw errors
-2. **ALWAYS run `review_test`** on the test file to validate tests actually check what requirements specify
-3. Fix any issues identified by the review
-
-## MCP Tools for Test Writing
-
-- `get_requirement` - Get requirement tree with existing coverage
-- `get_requirements_by_test` - See requirements referenced in a test file
-- `list_untested_requirements` - Find requirements without tests
-- `review_test` - Validate test actually checks what requirement specifies (run after writing tests)
-
-Note: Users can also explicitly trigger this workflow with `/write-tests`.

package/dist/utils/detect-existing-project.d.ts

@@ -1,5 +0,0 @@
-/**
- * Detect if .requirements/ directory exists and extract projectId from files
- */
-export declare function detectExistingProject(cwd: string): string | null;
-//# sourceMappingURL=detect-existing-project.d.ts.map

package/dist/utils/detect-existing-project.js

@@ -1,34 +0,0 @@
-import * as fs from 'fs';
-import * as path from 'path';
-import { parseRequirementsFromFile } from '../schema/index.js';
-/**
- * Detect if .requirements/ directory exists and extract projectId from files
- */
-export function detectExistingProject(cwd) {
-    const requirementsDir = path.join(cwd, '.requirements');
-    if (!fs.existsSync(requirementsDir)) {
-        return null;
-    }
-    // Look for .requirements.md files
-    const files = fs.readdirSync(requirementsDir)
-        .filter(f => f.endsWith('.requirements.md'));
-    if (files.length === 0) {
-        return null;
-    }
-    // Try to parse first file to get projectId
-    for (const file of files) {
-        try {
-            const filePath = path.join(requirementsDir, file);
-            const parsed = parseRequirementsFromFile(filePath);
-            if (parsed.metadata.projectId) {
-                return parsed.metadata.projectId;
-            }
-        }
-        catch (error) {
-            // Skip files that can't be parsed
-            continue;
-        }
-    }
-    return null;
-}
-//# sourceMappingURL=detect-existing-project.js.map