edsger 0.76.0 → 0.78.0

package/dist/commands/init/prompts.js

@@ -1,128 +0,0 @@
-/**
- * Prompts for Claude Code SDK to analyze codebase and generate documentation
- */
-export function createSystemPrompt() {
-    return `You are a technical documentation expert analyzing a codebase to generate comprehensive project documentation.
-
-Your task is to analyze the codebase structure, code files, configuration, and dependencies to create accurate, detailed documentation.
-
-IMPORTANT INSTRUCTIONS:
-1. Use available tools to explore the codebase (Glob, Read, Grep, Bash)
-2. Analyze actual code, not assumptions
-3. Use the Write tool to save the documentation to the specified file path
-4. Write ONLY markdown documentation content to the file - no conversational text
-5. Be thorough but concise - focus on what developers need to know
-6. Use proper markdown formatting with headers, lists, and code blocks`;
-}
-export function createProjectOverviewPrompt(filename) {
-    return `Analyze this codebase and generate a comprehensive project overview document.
-
-Please explore the codebase and create a markdown document covering:
-
-1. **Project Name** - Extract from package.json or similar
-2. **Description** - What the project does (from package.json description or README)
-3. **Goals and Objectives** - Infer from the codebase purpose
-4. **Core Issues** - List main issues by analyzing code structure
-5. **Target Users** - Who would use this project
-6. **Key Business Logic** - Important business rules or logic patterns
-7. **Important Notes** - Any critical information for developers
-
-Use Glob to find package.json, README, and main source directories.
-Use Read to examine key files.
-Use Grep to search for patterns if needed.
-
-When done analyzing, use the Write tool to save the markdown documentation to: ${filename}`;
-}
-export function createTechStackPrompt(filename) {
-    return `Analyze this codebase and generate a comprehensive technology stack document.
-
-Please explore the codebase and create a markdown document covering:
-
-1. **Programming Languages** - Identify from file extensions and package.json
-2. **Frameworks and Libraries** - From package.json dependencies
-3. **Frontend** - If applicable (React, Vue, etc.)
-4. **Backend** - If applicable (Express, Fastify, etc.)
-5. **Database** - If applicable (MongoDB, PostgreSQL, etc.)
-6. **Development Tools** - Package manager, build tools, testing frameworks, linters
-7. **Infrastructure** - Hosting, CI/CD (from config files)
-8. **External Services and APIs** - From code imports and API calls
-9. **Environment Variables** - List from .env.example or code
-
-Use Glob to find package.json, tsconfig.json, .env.example, and config files.
-Use Read to examine dependencies and configurations.
-Check for Docker, CI/CD configs, and other infrastructure files.
-
-When done analyzing, use the Write tool to save the markdown documentation to: ${filename}`;
-}
-export function createArchitecturePrompt(filename) {
-    return `Analyze this codebase and generate a comprehensive system architecture document.
-
-Please explore the codebase and create a markdown document covering:
-
-1. **High-Level Architecture** - Overall structure (monolith, microservices, etc.)
-2. **Directory Structure** - Map the main directories and their purposes
-3. **Key Components** - Important modules, classes, or services with their purposes
-4. **Data Flow** - How data flows through the system
-5. **Integration Points** - External systems, APIs, or services
-6. **Design Patterns** - Common patterns used in the codebase
-7. **Key Design Decisions** - Important architectural choices
-8. **Security Considerations** - Security measures in place
-9. **Performance Considerations** - Optimization strategies
-
-Use Glob to explore the directory structure.
-Use Read to examine main entry points and key files.
-Use Grep to find patterns like classes, interfaces, API endpoints.
-Look for architecture diagrams or documentation.
-
-When done analyzing, use the Write tool to save the markdown documentation to: ${filename}`;
-}
-export function createCodingGuidelinesPrompt(filename) {
-    return `Analyze this codebase and generate a comprehensive coding guidelines document.
-
-Please explore the codebase and create a markdown document covering:
-
-1. **Code Style** - General principles observed in the codebase
-2. **Naming Conventions** - How files, variables, functions, classes are named
-3. **File Organization** - How code is organized within directories
-4. **Import Order** - Standard order for imports (from actual code)
-5. **Function Guidelines** - Common patterns for function structure
-6. **Error Handling** - How errors are handled in the codebase
-7. **Testing Requirements** - Testing approach and frameworks used
-8. **Code Review Checklist** - Common items to check
-9. **Common Patterns to Use** - Patterns frequently used in this project
-10. **Anti-Patterns to Avoid** - Things to avoid based on codebase conventions
-11. **Git Commit Guidelines** - If present in docs or config
-
-Use Glob to find source files and configuration files.
-Use Read to examine code style, ESLint, Prettier configs.
-Use Grep to find common patterns in function declarations, imports, error handling.
-Check for CONTRIBUTING.md or similar files.
-
-When done analyzing, use the Write tool to save the markdown documentation to: ${filename}`;
-}
-export function createDevelopmentSetupPrompt(filename) {
-    return `Analyze this codebase and generate a comprehensive development setup document.
-
-Please explore the codebase and create a markdown document covering:
-
-1. **Prerequisites** - Required tools and versions (from package.json engines, etc.)
-2. **Initial Setup** - Steps to clone and set up the project
-3. **Install Dependencies** - Command to install (npm/yarn/pnpm)
-4. **Environment Configuration** - How to set up .env (from .env.example)
-5. **Database Setup** - If applicable, how to set up databases
-6. **Development Workflow**:
-   - Running the development server
-   - Building the project
-   - Running tests
-   - Linting and formatting
-7. **Common Commands** - List all npm scripts from package.json
-8. **Debugging** - How to debug the application
-9. **Troubleshooting** - Common issues and solutions
-10. **Resources** - Links to relevant documentation
-
-Use Glob to find package.json, .env.example, docker-compose, and README.
-Use Read to examine package.json scripts, env variables, and setup instructions.
-Check for Docker, database migrations, or setup scripts.
-
-When done analyzing, use the Write tool to save the markdown documentation to: ${filename}`;
-}

package/dist/commands/init/templates.d.ts

@@ -1,9 +0,0 @@
-/**
- * Template files for .edsger directory initialization
- * These files help edsger phases understand the project context
- */
-export declare const projectOverviewTemplate = "# Project Overview\n\n## Project Name\n[Your project name]\n\n## Description\n[Brief description of what this project does]\n\n## Goals and Objectives\n- [Goal 1]\n- [Goal 2]\n- [Goal 3]\n\n## Core Issues\n1. **[Issue 1]**: [Description]\n2. **[Issue 2]**: [Description]\n3. **[Issue 3]**: [Description]\n\n## Target Users\n[Who uses this project?]\n\n## Key Business Logic\n[Describe the core business logic and rules]\n\n## Important Notes\n[Any critical information that developers should know]\n";
-export declare const techStackTemplate = "# Technology Stack\n\n## Programming Languages\n- [Language 1]: [Version and usage]\n- [Language 2]: [Version and usage]\n\n## Frameworks and Libraries\n\n### Frontend (if applicable)\n- [Framework]: [Version]\n- [Library 1]: [Usage]\n- [Library 2]: [Usage]\n\n### Backend (if applicable)\n- [Framework]: [Version]\n- [Library 1]: [Usage]\n- [Library 2]: [Usage]\n\n### Database\n- [Database]: [Version and purpose]\n- [ORM/Query builder]: [If applicable]\n\n## Development Tools\n- Package Manager: [npm/yarn/pnpm]\n- Build Tool: [Webpack/Vite/etc]\n- Testing Framework: [Jest/Vitest/Playwright/etc]\n- Linting: [ESLint/etc]\n- Formatting: [Prettier/etc]\n\n## Infrastructure\n- Hosting: [Platform]\n- CI/CD: [Tool]\n- Monitoring: [Tool]\n\n## External Services and APIs\n- [Service 1]: [Purpose]\n- [Service 2]: [Purpose]\n\n## Environment Variables\n```\n[List key environment variables and their purposes]\n```\n";
-export declare const architectureTemplate = "# System Architecture\n\n## High-Level Architecture\n[Describe the overall architecture - monolith, microservices, etc.]\n\n## Directory Structure\n```\nproject-root/\n\u251C\u2500\u2500 [directory 1]/  # [Purpose]\n\u251C\u2500\u2500 [directory 2]/  # [Purpose]\n\u2514\u2500\u2500 [directory 3]/  # [Purpose]\n```\n\n## Key Components\n\n### [Component 1]\n- **Location**: [Path]\n- **Purpose**: [What it does]\n- **Dependencies**: [What it depends on]\n\n### [Component 2]\n- **Location**: [Path]\n- **Purpose**: [What it does]\n- **Dependencies**: [What it depends on]\n\n## Data Flow\n[Describe how data flows through the system]\n\n## Integration Points\n- [External system 1]: [How it integrates]\n- [External system 2]: [How it integrates]\n\n## Design Patterns\n[List key design patterns used in the project]\n\n## Key Design Decisions\n1. **[Decision 1]**: [Rationale]\n2. **[Decision 2]**: [Rationale]\n\n## Security Considerations\n[Key security measures and considerations]\n\n## Performance Considerations\n[Key performance optimization strategies]\n";
-export declare const codingGuidelinesTemplate = "# Coding Guidelines\n\n## Code Style\n\n### General Principles\n- [Principle 1]\n- [Principle 2]\n- [Principle 3]\n\n### Naming Conventions\n- **Files**: [Convention, e.g., kebab-case, PascalCase]\n- **Variables**: [Convention, e.g., camelCase]\n- **Functions**: [Convention, e.g., camelCase, descriptive verbs]\n- **Classes**: [Convention, e.g., PascalCase]\n- **Constants**: [Convention, e.g., UPPER_SNAKE_CASE]\n\n## File Organization\n[How files should be organized within directories]\n\n## Import Order\n[Standard order for imports]\n```typescript\n// Example:\n// 1. External libraries\n// 2. Internal modules\n// 3. Types\n// 4. Styles\n```\n\n## Function Guidelines\n- Maximum function length: [X lines]\n- Function complexity: [Guidelines]\n- Documentation: [When to add comments]\n\n## Error Handling\n[Standard error handling approach]\n\n## Testing Requirements\n- Unit tests: [Requirements]\n- Integration tests: [Requirements]\n- Test coverage: [Target percentage]\n\n## Code Review Checklist\n- [ ] Code follows style guidelines\n- [ ] Tests are included and passing\n- [ ] Documentation is updated\n- [ ] No security vulnerabilities\n- [ ] Performance considerations addressed\n\n## Common Patterns to Use\n[List common patterns used in this project]\n\n## Anti-Patterns to Avoid\n[List patterns that should be avoided]\n\n## Git Commit Guidelines\n- Format: [Convention, e.g., Conventional Commits]\n- Example: `feat: add user authentication`\n";
-export declare const developmentSetupTemplate = "# Development Setup\n\n## Prerequisites\n- [Tool 1]: [Version]\n- [Tool 2]: [Version]\n- [Tool 3]: [Version]\n\n## Initial Setup\n\n### 1. Clone Repository\n```bash\ngit clone [repository-url]\ncd [project-directory]\n```\n\n### 2. Install Dependencies\n```bash\n[package-manager] install\n```\n\n### 3. Environment Configuration\n```bash\n# Copy environment template\ncp .env.example .env\n\n# Update with your values\n[Instructions for required environment variables]\n```\n\n### 4. Database Setup (if applicable)\n```bash\n[Commands to set up database]\n```\n\n## Development Workflow\n\n### Running the Development Server\n```bash\n[command to start dev server]\n```\n\n### Building the Project\n```bash\n[build command]\n```\n\n### Running Tests\n```bash\n# All tests\n[test command]\n\n# Watch mode\n[watch command]\n\n# Coverage\n[coverage command]\n```\n\n### Linting and Formatting\n```bash\n# Lint\n[lint command]\n\n# Format\n[format command]\n```\n\n## Common Commands\n```bash\n# [Command 1]: [Description]\n# [Command 2]: [Description]\n```\n\n## Debugging\n[Instructions for debugging the application]\n\n## Troubleshooting\n\n### Common Issues\n1. **[Issue 1]**: [Solution]\n2. **[Issue 2]**: [Solution]\n\n## Resources\n- [Resource 1]: [Link]\n- [Resource 2]: [Link]\n";

package/dist/commands/init/templates.js

@@ -1,264 +0,0 @@
-/**
- * Template files for .edsger directory initialization
- * These files help edsger phases understand the project context
- */
-export const projectOverviewTemplate = `# Project Overview
-
-## Project Name
-[Your project name]
-
-## Description
-[Brief description of what this project does]
-
-## Goals and Objectives
-- [Goal 1]
-- [Goal 2]
-- [Goal 3]
-
-## Core Issues
-1. **[Issue 1]**: [Description]
-2. **[Issue 2]**: [Description]
-3. **[Issue 3]**: [Description]
-
-## Target Users
-[Who uses this project?]
-
-## Key Business Logic
-[Describe the core business logic and rules]
-
-## Important Notes
-[Any critical information that developers should know]
-`;
-export const techStackTemplate = `# Technology Stack
-
-## Programming Languages
-- [Language 1]: [Version and usage]
-- [Language 2]: [Version and usage]
-
-## Frameworks and Libraries
-
-### Frontend (if applicable)
-- [Framework]: [Version]
-- [Library 1]: [Usage]
-- [Library 2]: [Usage]
-
-### Backend (if applicable)
-- [Framework]: [Version]
-- [Library 1]: [Usage]
-- [Library 2]: [Usage]
-
-### Database
-- [Database]: [Version and purpose]
-- [ORM/Query builder]: [If applicable]
-
-## Development Tools
-- Package Manager: [npm/yarn/pnpm]
-- Build Tool: [Webpack/Vite/etc]
-- Testing Framework: [Jest/Vitest/Playwright/etc]
-- Linting: [ESLint/etc]
-- Formatting: [Prettier/etc]
-
-## Infrastructure
-- Hosting: [Platform]
-- CI/CD: [Tool]
-- Monitoring: [Tool]
-
-## External Services and APIs
-- [Service 1]: [Purpose]
-- [Service 2]: [Purpose]
-
-## Environment Variables
-\`\`\`
-[List key environment variables and their purposes]
-\`\`\`
-`;
-export const architectureTemplate = `# System Architecture
-
-## High-Level Architecture
-[Describe the overall architecture - monolith, microservices, etc.]
-
-## Directory Structure
-\`\`\`
-project-root/
-├── [directory 1]/  # [Purpose]
-├── [directory 2]/  # [Purpose]
-└── [directory 3]/  # [Purpose]
-\`\`\`
-
-## Key Components
-
-### [Component 1]
-- **Location**: [Path]
-- **Purpose**: [What it does]
-- **Dependencies**: [What it depends on]
-
-### [Component 2]
-- **Location**: [Path]
-- **Purpose**: [What it does]
-- **Dependencies**: [What it depends on]
-
-## Data Flow
-[Describe how data flows through the system]
-
-## Integration Points
-- [External system 1]: [How it integrates]
-- [External system 2]: [How it integrates]
-
-## Design Patterns
-[List key design patterns used in the project]
-
-## Key Design Decisions
-1. **[Decision 1]**: [Rationale]
-2. **[Decision 2]**: [Rationale]
-
-## Security Considerations
-[Key security measures and considerations]
-
-## Performance Considerations
-[Key performance optimization strategies]
-`;
-export const codingGuidelinesTemplate = `# Coding Guidelines
-
-## Code Style
-
-### General Principles
-- [Principle 1]
-- [Principle 2]
-- [Principle 3]
-
-### Naming Conventions
-- **Files**: [Convention, e.g., kebab-case, PascalCase]
-- **Variables**: [Convention, e.g., camelCase]
-- **Functions**: [Convention, e.g., camelCase, descriptive verbs]
-- **Classes**: [Convention, e.g., PascalCase]
-- **Constants**: [Convention, e.g., UPPER_SNAKE_CASE]
-
-## File Organization
-[How files should be organized within directories]
-
-## Import Order
-[Standard order for imports]
-\`\`\`typescript
-// Example:
-// 1. External libraries
-// 2. Internal modules
-// 3. Types
-// 4. Styles
-\`\`\`
-
-## Function Guidelines
-- Maximum function length: [X lines]
-- Function complexity: [Guidelines]
-- Documentation: [When to add comments]
-
-## Error Handling
-[Standard error handling approach]
-
-## Testing Requirements
-- Unit tests: [Requirements]
-- Integration tests: [Requirements]
-- Test coverage: [Target percentage]
-
-## Code Review Checklist
-- [ ] Code follows style guidelines
-- [ ] Tests are included and passing
-- [ ] Documentation is updated
-- [ ] No security vulnerabilities
-- [ ] Performance considerations addressed
-
-## Common Patterns to Use
-[List common patterns used in this project]
-
-## Anti-Patterns to Avoid
-[List patterns that should be avoided]
-
-## Git Commit Guidelines
-- Format: [Convention, e.g., Conventional Commits]
-- Example: \`feat: add user authentication\`
-`;
-export const developmentSetupTemplate = `# Development Setup
-
-## Prerequisites
-- [Tool 1]: [Version]
-- [Tool 2]: [Version]
-- [Tool 3]: [Version]
-
-## Initial Setup
-
-### 1. Clone Repository
-\`\`\`bash
-git clone [repository-url]
-cd [project-directory]
-\`\`\`
-
-### 2. Install Dependencies
-\`\`\`bash
-[package-manager] install
-\`\`\`
-
-### 3. Environment Configuration
-\`\`\`bash
-# Copy environment template
-cp .env.example .env
-
-# Update with your values
-[Instructions for required environment variables]
-\`\`\`
-
-### 4. Database Setup (if applicable)
-\`\`\`bash
-[Commands to set up database]
-\`\`\`
-
-## Development Workflow
-
-### Running the Development Server
-\`\`\`bash
-[command to start dev server]
-\`\`\`
-
-### Building the Project
-\`\`\`bash
-[build command]
-\`\`\`
-
-### Running Tests
-\`\`\`bash
-# All tests
-[test command]
-
-# Watch mode
-[watch command]
-
-# Coverage
-[coverage command]
-\`\`\`
-
-### Linting and Formatting
-\`\`\`bash
-# Lint
-[lint command]
-
-# Format
-[format command]
-\`\`\`
-
-## Common Commands
-\`\`\`bash
-# [Command 1]: [Description]
-# [Command 2]: [Description]
-\`\`\`
-
-## Debugging
-[Instructions for debugging the application]
-
-## Troubleshooting
-
-### Common Issues
-1. **[Issue 1]**: [Solution]
-2. **[Issue 2]**: [Solution]
-
-## Resources
-- [Resource 1]: [Link]
-- [Resource 2]: [Link]
-`;

package/dist/commands/intelligence/index.d.ts

@@ -1,15 +0,0 @@
-export interface IntelCommandOptions {
-    productId: string;
-    reportType?: string;
-    verbose?: boolean;
-    guidance?: string;
-    reportId?: string;
-    listCompetitors?: boolean;
-    confirmCompetitor?: string;
-    dismissCompetitor?: string;
-}
-/**
- * Run intelligence analysis for a product.
- * Discovers competitors, analyzes market, and produces actionable reports.
- */
-export declare const runIntelligence: (options: IntelCommandOptions) => Promise<void>;

package/dist/commands/intelligence/index.js

@@ -1,138 +0,0 @@
-import { getCompetitors, updateCompetitor } from '../../api/intelligence.js';
-import { analyseIntelligence, } from '../../phases/intelligence-analysis/index.js';
-import { deregisterSession, registerSession, } from '../../system/session-manager.js';
-import { logError, logInfo, logSuccess, logWarning, } from '../../utils/logger.js';
-import { validateConfiguration } from '../../utils/validation.js';
-/**
- * Run intelligence analysis for a product.
- * Discovers competitors, analyzes market, and produces actionable reports.
- */
-export const runIntelligence = async (options) => {
-    const { productId } = options;
-    // Handle competitor management subcommands
-    if (options.listCompetitors) {
-        return listCompetitors(productId, options.verbose);
-    }
-    if (options.confirmCompetitor) {
-        return setCompetitorStatus(options.confirmCompetitor, 'confirmed', options.verbose);
-    }
-    if (options.dismissCompetitor) {
-        return setCompetitorStatus(options.dismissCompetitor, 'dismissed', options.verbose);
-    }
-    // Run full analysis
-    const config = validateConfiguration({
-        verbose: options.verbose,
-    });
-    await registerSession({ command: 'intel', productId });
-    logInfo(`Starting intelligence analysis for product: ${productId}`);
-    try {
-        const result = await analyseIntelligence({
-            productId,
-            reportType: options.reportType,
-            verbose: options.verbose,
-            guidance: options.guidance,
-            reportId: options.reportId,
-        }, config);
-        if (result.status === 'success') {
-            displayResults(result, options.verbose);
-        }
-        else {
-            logError(`Intelligence analysis failed: ${result.error || 'Unknown error'}`);
-        }
-    }
-    catch (error) {
-        logError(`Intelligence analysis error: ${error instanceof Error ? error.message : String(error)}`);
-    }
-    finally {
-        await deregisterSession();
-    }
-};
-function displayResults(result, verbose) {
-    logSuccess('Intelligence analysis completed!');
-    if (result.discoveredCompetitors.length > 0) {
-        logInfo(`\nDiscovered ${result.discoveredCompetitors.length} competitor candidates:`);
-        for (const c of result.discoveredCompetitors) {
-            logInfo(`  ✦ ${c.name} (suggested) — ${c.discovery_reason || 'No reason'}`);
-        }
-        logInfo('\n  Review and confirm/dismiss in the Desktop app → Intelligence tab');
-    }
-    if (result.snapshots.length > 0) {
-        logInfo(`\nSaved ${result.snapshots.length} competitor snapshots`);
-    }
-    if (result.report) {
-        displayReport(result.report, verbose);
-    }
-    logInfo('\nView full results in Desktop app → Intelligence tab');
-}
-function displayReport(report, verbose) {
-    logInfo(`\nReport: ${report.title}`);
-    const findings = report.key_findings || [];
-    if (findings.length > 0) {
-        logInfo('\nKey Findings:');
-        for (const f of findings) {
-            const icon = severityIcon(f.severity);
-            logInfo(`  ${icon} [${f.severity.toUpperCase()}] ${f.finding}`);
-        }
-    }
-    const recs = report.recommendations || [];
-    if (recs.length > 0) {
-        logInfo('\nRecommendations:');
-        for (const r of recs) {
-            logInfo(`  [${r.priority.toUpperCase()}] ${r.action}`);
-            if (verbose && r.rationale) {
-                logInfo(`    → ${r.rationale}`);
-            }
-        }
-    }
-    logInfo(`\nReport ID: ${report.id}`);
-}
-function severityIcon(severity) {
-    if (severity === 'critical') {
-        return '🔴';
-    }
-    if (severity === 'important') {
-        return '🟡';
-    }
-    return '🔵';
-}
-async function listCompetitors(productId, verbose) {
-    const competitors = await getCompetitors(productId, undefined, verbose);
-    if (competitors.length === 0) {
-        logInfo('No competitors found. Run `edsger intel <productId>` to discover competitors.');
-        return;
-    }
-    const groups = {
-        confirmed: competitors.filter((c) => c.status === 'confirmed'),
-        suggested: competitors.filter((c) => c.status === 'suggested'),
-        dismissed: competitors.filter((c) => c.status === 'dismissed'),
-    };
-    if (groups.confirmed.length > 0) {
-        logInfo(`\nConfirmed (${groups.confirmed.length}):`);
-        for (const c of groups.confirmed) {
-            logInfo(`  ✓ ${c.name} — ${c.url || 'No URL'} [${c.id}]`);
-        }
-    }
-    if (groups.suggested.length > 0) {
-        logInfo(`\nSuggested (${groups.suggested.length}):`);
-        for (const c of groups.suggested) {
-            logInfo(`  ✦ ${c.name} — ${c.discovery_reason || 'No reason'} [${c.id}]`);
-        }
-        logInfo('\n  Confirm: edsger intel <productId> --confirm-competitor <id>');
-        logInfo('  Dismiss: edsger intel <productId> --dismiss-competitor <id>');
-    }
-    if (groups.dismissed.length > 0 && verbose) {
-        logWarning(`\nDismissed (${groups.dismissed.length}):`);
-        for (const c of groups.dismissed) {
-            logInfo(`  ✗ ${c.name} [${c.id}]`);
-        }
-    }
-}
-async function setCompetitorStatus(competitorId, status, verbose) {
-    const updated = await updateCompetitor(competitorId, { status }, verbose);
-    if (updated) {
-        logSuccess(`Competitor "${updated.name}" ${status === 'confirmed' ? 'confirmed ✓' : 'dismissed ✗'}`);
-    }
-    else {
-        logError(`Failed to update competitor ${competitorId}`);
-    }
-}

package/dist/commands/issue-analysis/index.d.ts

@@ -1,5 +0,0 @@
-export interface IssueAnalysisCliOptions {
-    issueId: string;
-    verbose?: boolean;
-}
-export declare const runIssueAnalysisCommand: (options: IssueAnalysisCliOptions) => Promise<void>;

package/dist/commands/issue-analysis/index.js

@@ -1,9 +0,0 @@
-import { analyseIssue } from '../../phases/issue-analysis/index.js';
-import { runIssuePhaseCli } from '../../utils/issue-phase-cli.js';
-export const runIssueAnalysisCommand = (options) => runIssuePhaseCli({
-    command: 'issue-analysis',
-    description: 'Issue analysis',
-    issueId: options.issueId,
-    verbose: options.verbose,
-    execute: analyseIssue,
-});

package/dist/commands/pr-resolve/index.d.ts

@@ -1,13 +0,0 @@
-/**
- * CLI command: edsger pr-resolve <productId> --pr-url <url>
- * Resolves PR change requests: fixes what's genuinely better, explains what it won't change.
- */
-export interface PRResolveCliOptions {
-    prUrl: string;
-    prId?: string;
-    /** Repo-only mode: resolve GitHub config from a repositories row. */
-    repoId?: string;
-    verbose?: boolean;
-    learn?: boolean;
-}
-export declare function runPRResolve(productId: string | undefined, options: PRResolveCliOptions): Promise<void>;

package/dist/commands/pr-resolve/index.js

@@ -1,50 +0,0 @@
-/**
- * CLI command: edsger pr-resolve <productId> --pr-url <url>
- * Resolves PR change requests: fixes what's genuinely better, explains what it won't change.
- */
-import { getGitHubConfigByProduct, getGitHubConfigByRepository, } from '../../api/github.js';
-import { resolveStandalonePR } from '../../phases/pr-resolve/index.js';
-import { logError, logInfo, logSuccess } from '../../utils/logger.js';
-export async function runPRResolve(productId, options) {
-    const { prUrl, prId, repoId, verbose } = options;
-    const scopeLabel = repoId ? `repository ${repoId}` : `product ${productId}`;
-    logInfo(`Starting PR resolve for ${scopeLabel}`);
-    logInfo(`PR URL: ${prUrl}`);
-    // Resolve GitHub config from the repository (repo-only mode) or the product.
-    const githubConfig = repoId
-        ? await getGitHubConfigByRepository(repoId, verbose)
-        : await getGitHubConfigByProduct(productId ?? '', verbose);
-    if (!githubConfig.configured ||
-        !githubConfig.token ||
-        !githubConfig.owner ||
-        !githubConfig.repo) {
-        logError(`GitHub not configured for ${scopeLabel}: ${githubConfig.message || 'No installation found'}`);
-        process.exit(1);
-    }
-    const result = await resolveStandalonePR({
-        productId,
-        repositoryId: repoId,
-        pullRequestUrl: prUrl,
-        githubToken: githubConfig.token,
-        owner: githubConfig.owner,
-        repo: githubConfig.repo,
-        prId,
-        verbose,
-        // Checklist learning is product-scoped; skip it in repo-only mode.
-        learn: repoId ? false : options.learn,
-    });
-    if (result.status === 'success') {
-        logSuccess(`PR resolve completed: ${result.message}`);
-        if (result.summary) {
-            logInfo(`Summary: ${result.summary}`);
-        }
-        if (result.threadsAddressed !== undefined) {
-            logInfo(`Threads addressed: ${result.threadsAddressed}`);
-            logInfo(`Threads skipped: ${result.threadsSkipped}`);
-        }
-    }
-    else {
-        logError(`PR resolve failed: ${result.message}`);
-        process.exit(1);
-    }
-}

package/dist/commands/pr-review/index.d.ts

@@ -1,12 +0,0 @@
-/**
- * CLI command: edsger pr-review <productId> --pr-url <url>
- * Reviews a standalone GitHub PR and posts comments.
- */
-export interface PRReviewCliOptions {
-    prUrl: string;
-    prId?: string;
-    /** Repo-only mode: resolve GitHub config from a repositories row. */
-    repoId?: string;
-    verbose?: boolean;
-}
-export declare function runPRReview(productId: string | undefined, options: PRReviewCliOptions): Promise<void>;