edsger 0.77.0 → 0.78.0

package/dist/utils/formatters.js

@@ -1,166 +0,0 @@
-import { downloadImagesForClaudeCode, } from './image-downloader.js';
-/**
- * Format user stories for display in prompts
- */
-export function formatUserStories(stories) {
-    if (stories.length === 0) {
-        return 'No user stories defined.';
-    }
-    return stories
-        .map((story, index) => `${index + 1}. **${story.title}** (Status: ${story.status})
-   ID: ${story.id}${story.status === 'draft' ? ' [DELETABLE]' : ''}${story.status === 'approved' ? ' [APPROVED - DO NOT MODIFY]' : ''}
-   ${story.description}`)
-        .join('\n\n');
-}
-/**
- * Format test cases for display in prompts
- */
-export function formatTestCases(cases) {
-    if (cases.length === 0) {
-        return 'No test cases defined.';
-    }
-    return cases
-        .map((testCase, index) => `${index + 1}. **${testCase.name}** ${testCase.is_critical ? '[CRITICAL]' : '[OPTIONAL]'} (Status: ${testCase.status || 'unknown'})
-   ID: ${testCase.id}${testCase.status === 'draft' ? ' [DELETABLE]' : ''}${testCase.status === 'approved' ? ' [APPROVED - DO NOT MODIFY]' : ''}
-   ${testCase.description}`)
-        .join('\n\n');
-}
-/**
- * Format technical design context for Claude Code prompts
- */
-export async function formatTechnicalDesignContext(context) {
-    const { processedMarkdown, downloadedImages } = await downloadImagesForClaudeCode(context.issue.description || 'No description provided', context.issue.id // Use issue ID for directory naming
-    );
-    const content = `# Technical Design Context
-
-## Issue Information
-- **ID**: ${context.issue.id}
-- **Name**: ${context.issue.name}
-- **Description**:
-${processedMarkdown}
-
-${downloadedImages.length > 0 ? '**IMPORTANT**: The description contains images that have been downloaded locally. Please use the Read tool to view these images to fully understand the requirements.' : ''}
-
-- **Current Status**: ${context.issue.status}
-
-## Product Information
-- **Product**: ${context.product.name}
-- **Product ID**: ${context.product.id}
-- **Description**: ${context.product.description || 'No product description'}
-
-## User Stories (${context.user_stories.length})
-${formatUserStories(context.user_stories)}
-
-## Test Cases (${context.test_cases.length})
-${formatTestCases(context.test_cases)}
-
-## Current Technical Design
-${context.issue.technical_design || 'No existing technical design found'}
-
----
-
-**Design Instructions**: Based on the above issue requirements, user stories, and test cases, create or enhance the comprehensive technical design. Focus on system architecture, component design, database schema, API specifications, security considerations, and implementation strategy.`;
-    return { content, downloadedImages };
-}
-/**
- * Format issue analysis context for Claude Code prompts
- */
-export async function formatIssueAnalysisContext(context) {
-    const { processedMarkdown, downloadedImages } = await downloadImagesForClaudeCode(context.issue.description || 'No description provided', context.issue.id // Use issue ID for directory naming
-    );
-    const content = `# Issue Analysis Context
-
-## Issue Information
-- **ID**: ${context.issue.id}
-- **Name**: ${context.issue.name}
-- **Description**:
-${processedMarkdown}
-
-${downloadedImages.length > 0 ? '**IMPORTANT**: The description contains images that have been downloaded locally. Please use the Read tool to view these images to fully understand the requirements.' : ''}
-
-- **Current Status**: ${context.issue.status}
-
-## Product Information
-- **Product**: ${context.product.name}
-- **Product ID**: ${context.product.id}
-- **Description**: ${context.product.description || 'No product description'}
-
-## Current Technical Design
-${context.issue.technical_design || 'No technical design available yet'}
-
----
-
-**Analysis Instructions**: Based on the issue and product context above, produce an execution plan describing which artifacts this issue needs (user stories, test cases, technical design, branch plan, code implementation, functional testing, code review), in what order, with concrete success criteria and known risks.`;
-    return { content, downloadedImages };
-}
-/**
- * Format code implementation context for Claude Code prompts
- */
-export async function formatCodeImplementationContext(context) {
-    const { processedMarkdown, downloadedImages } = await downloadImagesForClaudeCode(context.issue.description || 'No description provided', context.issue.id // Use issue ID for directory naming
-    );
-    const content = `# Code Implementation Context
-
-## Issue Information
-- **ID**: ${context.issue.id}
-- **Name**: ${context.issue.name}
-- **Description**:
-${processedMarkdown}
-
-${downloadedImages.length > 0 ? '**IMPORTANT**: The description contains images that have been downloaded locally. Please use the Read tool to view these images to fully understand the requirements.' : ''}
-
-- **Current Status**: ${context.issue.status}
-
-## Product Information
-- **Product**: ${context.product.name}
-- **Product ID**: ${context.product.id}
-- **Description**: ${context.product.description || 'No product description'}
-
-## User Stories to Implement (${context.user_stories.length})
-${formatUserStories(context.user_stories)}
-
-## Test Cases to Satisfy (${context.test_cases.length})
-${formatTestCases(context.test_cases)}
-
-## Technical Design
-${context.technical_design || 'No technical design available - implement based on user stories and test cases'}
-
----
-
-**Implementation Instructions**: Based on the above requirements, user stories, test cases, and technical design, implement the complete issue functionality. Ensure all user stories are implemented and all test cases can pass.`;
-    return { content, downloadedImages };
-}
-/**
- * Format functional testing context for Claude Code prompts
- */
-export async function formatFunctionalTestingContext(context) {
-    const { processedMarkdown, downloadedImages } = await downloadImagesForClaudeCode(context.issue.description || 'No description provided', context.issue.id // Use issue ID for directory naming
-    );
-    const content = `# Functional Testing Context
-
-## Issue Information
-- **ID**: ${context.issue.id}
-- **Name**: ${context.issue.name}
-- **Description**:
-${processedMarkdown}
-
-${downloadedImages.length > 0 ? '**IMPORTANT**: The description contains images that have been downloaded locally. Please use the Read tool to view these images to fully understand the requirements.' : ''}
-
-- **Current Status**: ${context.issue.status}
-
-## Product Information
-- **Product**: ${context.product.name}
-- **Product ID**: ${context.product.id}
-- **Description**: ${context.product.description || 'No product description'}
-
-## User Stories to Test (${context.user_stories.length})
-${formatUserStories(context.user_stories)}
-
-## Test Cases to Execute (${context.test_cases.length})
-${formatTestCases(context.test_cases)}
-
----
-
-**Testing Instructions**: The issue has been implemented. Execute comprehensive functional testing using headless Playwright to verify all user stories work correctly and all test cases pass. Test both positive and negative scenarios.`;
-    return { content, downloadedImages };
-}

package/dist/utils/git-branch-manager-async.d.ts

@@ -1,127 +0,0 @@
-/**
- * Git Branch Manager - Async Operations
- * Async git operations that support automatic conflict resolution via Claude agent.
- * These functions build on the sync operations from git-branch-manager.ts.
- */
-/**
- * Sync feat branch with main using GitHub API
- * This ensures the feat branch (PR base) is up to date with main,
- * preventing extra commits from appearing in PRs when dev branch is rebased.
- *
- * @param featBranch - The feat branch name (e.g., "feat/abc123/1-database")
- * @param githubToken - GitHub personal access token or app token
- * @param owner - Repository owner
- * @param repo - Repository name
- * @param baseBranch - The base branch to sync from (default: "main")
- * @param verbose - Whether to log verbose output
- * @returns true if feat branch was actually updated, false if already up-to-date or error
- */
-export interface SyncFeatBranchOptions {
-    featBranch: string;
-    githubToken: string;
-    owner: string;
-    repo: string;
-    baseBranch?: string;
-    verbose?: boolean;
-}
-export declare function syncFeatBranchWithMain(opts: SyncFeatBranchOptions): Promise<boolean>;
-/**
- * Options for async rebase with conflict resolution
- */
-export interface RebaseWithConflictResolutionOptions {
-    issueBranch: string;
-    /**
-     * Base branch to create new branches from.
-     * For merged parent branches, this is feat/xxx.
-     * For completed parent branches, this is main.
-     */
-    baseBranch?: string;
-    /**
-     * Target branch for --onto rebase.
-     * When set, uses `git rebase --onto rebaseTargetBranch originalBaseBranch`.
-     * If not set, baseBranch is used as the rebase target.
-     */
-    rebaseTargetBranch?: string;
-    /**
-     * Original base branch before squash merge.
-     * When set, uses `git rebase --onto <target> originalBaseBranch` to only
-     * rebase commits that are new relative to originalBaseBranch.
-     * This is required when the base branch was squash-merged, otherwise
-     * git will try to reapply all the original commits causing many conflicts.
-     */
-    originalBaseBranch?: string;
-    verbose?: boolean;
-    resolveConflicts?: boolean;
-    conflictResolverConfig?: {
-        model?: string;
-        maxTurns?: number;
-    };
-    /**
-     * When true, indicates the base branch's feat was already squash-merged to main.
-     * The conflict resolver should use "theirs" (main) for all conflicts to drop
-     * duplicate commits from the base branch.
-     */
-    baseBranchCompleted?: boolean;
-    /**
-     * Force push the branch after rebase.
-     * This is needed when feat branch was synced to main, to trigger
-     * GitHub to recalculate the PR diff.
-     */
-    forcePushAfterRebase?: boolean;
-    /** GitHub App installation token for authenticated push */
-    githubToken?: string;
-}
-/**
- * Switch to issue branch and rebase with base branch, with optional automatic conflict resolution
- * This is the async version that supports conflict resolution using Claude agent
- *
- * @param options - Options for the rebase operation
- * @returns Object containing the previous branch name and conflict resolution result
- */
-export declare function switchToIssueBranchAndRebaseAsync(options: RebaseWithConflictResolutionOptions): Promise<{
-    previousBranch: string;
-    conflictsResolved?: boolean;
-    resolvedFiles?: string[];
-}>;
-/**
- * Async version of prepareCustomBranchGitEnvironment with conflict resolution support.
- *
- * Usage:
- *   const cleanup = await prepareCustomBranchGitEnvironmentAsync({
- *     issueBranch: 'feat/123/2-api',
- *     baseBranch: 'feat/123/1-database',
- *     verbose: true,
- *     resolveConflicts: true,
- *   })
- *   try {
- *     // ... phase logic ...
- *   } finally {
- *     cleanup()
- *   }
- *
- * @param options - Options for the git environment preparation
- * @returns Cleanup function that will return to main branch
- */
-export declare function prepareCustomBranchGitEnvironmentAsync(options: RebaseWithConflictResolutionOptions): Promise<{
-    cleanup: () => void;
-    conflictsResolved?: boolean;
-    resolvedFiles?: string[];
-}>;
-/**
- * Async version of preparePhaseGitEnvironment with conflict resolution support.
- *
- * @param issueId - The issue ID (will be used to construct branch name "dev/{issueId}")
- * @param baseBranch - The base branch to rebase from (default: "main")
- * @param verbose - Whether to log verbose output
- * @param resolveConflicts - Whether to automatically resolve conflicts using Claude
- * @param conflictResolverConfig - Configuration for the conflict resolver
- * @returns Cleanup function and conflict resolution info
- */
-export declare function preparePhaseGitEnvironmentAsync(issueId: string, baseBranch?: string, verbose?: boolean, resolveConflicts?: boolean, conflictResolverConfig?: {
-    model?: string;
-    maxTurns?: number;
-}): Promise<{
-    cleanup: () => void;
-    conflictsResolved?: boolean;
-    resolvedFiles?: string[];
-}>;