edsger 0.77.0 → 0.78.0

package/dist/phases/user-stories-analysis/prompts.d.ts

@@ -1,7 +0,0 @@
-import { type ChecklistVerificationResult } from '../issue-analysis-verification/agent.js';
-export declare const createUserStoriesAnalysisSystemPrompt: (projectDir?: string) => Promise<string>;
-export declare const createUserStoriesAnalysisPromptWithContext: (issueId: string, contextInfo: string) => string;
-export declare const createUserStoriesFeedbackFocusedPromptWithContext: (issueId: string, contextInfo: string) => string;
-export declare const createUserStoriesImprovementPrompt: (verificationResult: ChecklistVerificationResult, previousAnalysis: {
-    created_user_stories: Record<string, unknown>[];
-}) => string;

package/dist/phases/user-stories-analysis/prompts.js

@@ -1,194 +0,0 @@
-import { resolveSkill } from '../../services/skill-resolver.js';
-import { OUTPUT_CONTRACTS } from '../output-contracts.js';
-export const createUserStoriesAnalysisSystemPrompt = async (projectDir) => {
-    const skill = await resolveSkill('phase/user-stories-analysis', {
-        projectDir,
-    });
-    if (!skill) {
-        throw new Error('Failed to load skill: phase/user-stories-analysis');
-    }
-    return `${skill.prompt}\n\n${OUTPUT_CONTRACTS['user-stories-analysis']}`;
-};
-export const createUserStoriesAnalysisPromptWithContext = (issueId, contextInfo) => {
-    return `Please create comprehensive, professional user stories for issue ID: ${issueId}
-
-${contextInfo}
-
-## Analysis Instructions
-
-Follow this systematic approach:
-
-1. **Deeply Understand the Issue**: Read the issue description, product context, and any provided images carefully. Understand the full scope of what this issue needs to accomplish.
-
-2. **Identify All User Personas**: List every type of user who will interact with this issue (e.g., admin, manager, regular user, analyst, coach, etc.)
-
-3. **Map Functional Areas**: Group the issue's functionality into logical categories (e.g., "Core Interface & Navigation", "Data Display & Visualization", "Configuration & Settings", "Notifications & Alerts")
-
-4. **Review Existing Stories**: Check existing user stories for:
-   - What's already well-covered
-   - What's missing or has gaps
-   - What should be deleted (duplicates, low quality)
-
-5. **Create Professional User Stories**: For each functional area, create stories that:
-   - Use sequential IDs with a consistent prefix
-   - Have descriptive shortnames
-   - Include specific user roles (not generic "user")
-   - Provide detailed descriptions with context
-   - List 4-8 specific, testable requirements per story
-
-6. **Validate Complete Coverage**: Ensure stories cover:
-   - All identified user personas
-   - All functional areas
-   - Happy paths AND edge cases
-   - Error states and graceful degradation
-   - Accessibility considerations
-   - Integration with existing issues
-
-7. **Output Results**: Return your analysis in the required JSON format
-
-## Important Notes
-- Focus on creating NEW user stories that add business value
-- Avoid duplicating existing user stories
-- Think comprehensively about ALL user types and scenarios
-- Write requirements that are testable and specific
-- Group stories logically by functional area
-- Be thorough but focus on practical, implementable stories
-
-Begin your systematic analysis based on the above context.`;
-};
-export const createUserStoriesFeedbackFocusedPromptWithContext = (issueId, contextInfo) => {
-    return `Please update user stories for issue ID: ${issueId} based on human feedback.
-
-${contextInfo}
-
-## Feedback-Focused Instructions
-
-This is a RE-RUN with human feedback. Existing user stories have already been created in a previous analysis. Your task is to **apply the human feedback changes only** — do NOT redo the full analysis from scratch.
-
-**What you MUST do:**
-1. **Read the Human Feedbacks section carefully** — these are the changes requested by the team
-2. **Apply each feedback**: modify, delete, or create user stories as the feedback instructs
-3. **Preserve unchanged stories** — do NOT recreate or delete stories that are not mentioned in the feedback
-4. **Keep all [APPROVED] stories untouched** — they are immutable
-
-**What you MUST NOT do:**
-- Do NOT re-analyze the entire issue from scratch
-- Do NOT create a full new set of user stories
-- Do NOT delete or recreate stories just to "improve" them unless feedback specifically requests it
-- Do NOT ignore any feedback item
-
-**Scope of changes:**
-- If feedback says to modify a story → delete the old draft and create an updated version
-- If feedback says to add a story → create it
-- If feedback says to remove a story → delete it (only if [DELETABLE])
-- If feedback says to change wording/requirements → delete old draft and create improved version
-- If no feedback mentions a story → leave it as-is (do NOT include it in created_user_stories)
-
-**Output**: Return ONLY new/updated stories in created_user_stories. Stories that are unchanged should NOT appear in your output.
-
-Begin applying the human feedback to the existing user stories.`;
-};
-export const createUserStoriesImprovementPrompt = (verificationResult, previousAnalysis) => {
-    const rejectedItemsSection = verificationResult.item_verifications
-        .filter((v) => v.verification_status === 'rejected')
-        .map((v, index) => {
-        return `### Rejected Requirement ${index + 1}
-**Checklist Item ID**: ${v.checklist_item_id}
-**Satisfaction Status**: ${v.is_satisfied ? '✅ Satisfied' : '❌ Not Satisfied'}
-**Verification Result**: ❌ REJECTED
-**Reason**: ${v.verification_reason}
-${v.concerns && v.concerns.length > 0 ? `**Specific Concerns**:\n${v.concerns.map((c) => `- ${c}`).join('\n')}` : ''}
-${v.improvement_suggestions && v.improvement_suggestions.length > 0 ? `\n**Improvement Suggestions**:\n${v.improvement_suggestions.map((s) => `- ${s}`).join('\n')}` : ''}
-`;
-    })
-        .join('\n---\n');
-    const uncertainItemsSection = verificationResult.item_verifications
-        .filter((v) => v.verification_status === 'uncertain')
-        .map((v, index) => {
-        return `### Uncertain Requirement ${index + 1}
-**Checklist Item ID**: ${v.checklist_item_id}
-**Satisfaction Status**: ${v.is_satisfied ? '✅ Satisfied' : '⚠️ Partially Satisfied'}
-**Verification Result**: ⚠️ UNCERTAIN
-**Reason**: ${v.verification_reason}
-${v.concerns && v.concerns.length > 0 ? `**Specific Concerns**:\n${v.concerns.map((c) => `- ${c}`).join('\n')}` : ''}
-${v.improvement_suggestions && v.improvement_suggestions.length > 0 ? `\n**Improvement Suggestions**:\n${v.improvement_suggestions.map((s) => `- ${s}`).join('\n')}` : ''}
-`;
-    })
-        .join('\n---\n');
-    return `# Verification Feedback - Improvements Required
-
-Your previous user stories analysis was verified, and **${verificationResult.rejected_count} checklist requirements were NOT SATISFIED** and **${verificationResult.uncertain_count} requirements are PARTIALLY SATISFIED**.
-
-## Verification Summary
-${verificationResult.summary}
-
-## Results Breakdown
-- Satisfied: ${verificationResult.confirmed_count}
-- Not Satisfied: ${verificationResult.rejected_count}
-- Partially Satisfied: ${verificationResult.uncertain_count}
-
-${verificationResult.overall_suggestions && verificationResult.overall_suggestions.length > 0 ? `## Overall Improvement Suggestions\n\n${verificationResult.overall_suggestions.map((s) => `- ${s}`).join('\n')}\n\n` : ''}
-
-${verificationResult.rejected_count > 0 ? `## Unsatisfied Requirements\n\n${rejectedItemsSection}` : ''}
-
-${verificationResult.uncertain_count > 0 ? `## Partially Satisfied Requirements\n\n${uncertainItemsSection}` : ''}
-
-## Your Previous Work
-
-### User Stories You Created (${previousAnalysis.created_user_stories.length})
-${previousAnalysis.created_user_stories
-        .map((story, index) => `${index + 1}. **${story.title}**
-   ${story.description}
-   Status: ${story.status || 'draft'}`)
-        .join('\n\n')}
-
----
-
-## Your Task: Improve Your User Stories
-
-You need to **revise and improve** your user stories to satisfy the checklist requirements.
-
-**What You Should Do**:
-1. **Review the improvement suggestions** provided above
-2. **Follow the specific, actionable suggestions**
-3. **Add NEW user stories** as suggested by the verifier
-4. **DELETE user stories** that are duplicates or don't add value
-5. **Improve quality and specificity** of your stories
-
-**CRITICAL - Output Format**:
-Return ONLY the JSON object. Do NOT include any text before or after the JSON.
-
-\`\`\`json
-{
-  "analysis": {
-    "issue_id": "...",
-    "status": "success",
-    "summary": "Improved user stories based on verification feedback",
-    "id_prefix": "XX",
-    "created_user_stories": [
-      {
-        "title": "XX-001: Shortname Here",
-        "description": "**Category**: [Area]\\n\\n**User Story**: As a **[role]**, I would like **[goal]** so that **[benefit]**.\\n\\n**Description**: [Detailed description]\\n\\n**Requirements**:\\n- [Requirement 1]\\n- [Requirement 2]",
-        "status": "draft",
-        "differentiation": "REQUIRED: Explain difference from existing stories"
-      }
-    ],
-    "deleted_user_story_ids": [],
-    "deletion_reasons": {},
-    "checklist_item_results": [
-      {
-        "checklist_item_id": "EXACT_UUID",
-        "is_passed": true,
-        "value": "Result value",
-        "notes": "Optional notes"
-      }
-    ],
-    "recommendations": "..."
-  }
-}
-\`\`\`
-
-MANDATORY: Include checklist_item_results for ALL checklist items.
-
-Return ONLY the JSON above.`;
-};

package/dist/services/audit-logs.d.ts

@@ -1,73 +0,0 @@
-/**
- * Issue Audit Logs Service
- * Provides functions to log issue lifecycle events to the database
- */
-export interface LogPhaseEventParams {
-    issueId: string;
-    eventType: 'phase_started' | 'phase_completed' | 'phase_failed' | 'autonomous_iteration_completed' | 'autonomous_iteration_failed' | 'hook_started' | 'hook_completed' | 'hook_failed';
-    phase: 'issue_analysis' | 'user_stories_analysis' | 'test_cases_analysis' | 'technical_design' | 'branch_planning' | 'code_implementation' | 'pr_splitting' | 'pr_execution' | 'functional_testing' | 'pull_request' | 'code_review' | 'code_refine' | 'code_refine_verification' | 'autonomous' | (string & {});
-    result?: 'success' | 'error' | 'warning' | 'info';
-    metadata?: Record<string, unknown>;
-    errorMessage?: string;
-}
-export interface LogChecklistEventParams {
-    issueId: string;
-    eventType: 'checklist_validated' | 'checklist_verified';
-    checklistId: string;
-    result?: 'success' | 'error' | 'warning' | 'info';
-    metadata?: Record<string, unknown>;
-}
-export interface LogVerificationEventParams {
-    issueId: string;
-    phase: 'issue_analysis' | 'user_stories_analysis' | 'test_cases_analysis' | 'technical_design' | 'branch_planning' | 'code_implementation' | 'pr_splitting' | 'pr_execution' | 'functional_testing' | 'pull_request' | 'code_review' | 'code_refine' | 'code_refine_verification';
-    iteration: number;
-    result: 'success' | 'error';
-    verificationData: {
-        confirmed_count: number;
-        rejected_count: number;
-        uncertain_count: number;
-        rejected_items?: {
-            checklist_item_id: string;
-            reason: string;
-            concerns?: string[];
-            improvement_suggestions?: string[];
-        }[];
-        uncertain_items?: {
-            checklist_item_id: string;
-            reason: string;
-            concerns?: string[];
-            improvement_suggestions?: string[];
-        }[];
-        feedbacks_confirmed_count?: number;
-        feedbacks_rejected_count?: number;
-        feedbacks_uncertain_count?: number;
-        rejected_feedbacks?: {
-            feedback_id: string;
-            feedback_title: string;
-            reason: string;
-            concerns?: string[];
-            improvement_suggestions?: string[];
-        }[];
-        uncertain_feedbacks?: {
-            feedback_id: string;
-            feedback_title: string;
-            reason: string;
-            concerns?: string[];
-            improvement_suggestions?: string[];
-        }[];
-        summary?: string;
-        overall_suggestions?: string[];
-    };
-}
-/**
- * Log a phase event (start, completion, or failure)
- */
-export declare function logIssuePhaseEvent(params: LogPhaseEventParams, verbose?: boolean): Promise<string | null>;
-/**
- * Log a checklist validation event
- */
-export declare function logIssueChecklistEvent(params: LogChecklistEventParams, verbose?: boolean): Promise<string | null>;
-/**
- * Log a verification event (dual-agent verification result)
- */
-export declare function logIssueVerificationEvent(params: LogVerificationEventParams, verbose?: boolean): Promise<string | null>;

package/dist/services/audit-logs.js

@@ -1,174 +0,0 @@
-/**
- * Issue Audit Logs Service
- * Provides functions to log issue lifecycle events to the database
- */
-import { callMcpEndpoint } from '../api/mcp-client.js';
-import { getSupabase, hasSupabaseSession } from '../supabase/client.js';
-import { logError, logInfo } from '../utils/logger.js';
-/** Insert one row into issue_audit_logs and return its id, or null on failure. */
-async function insertAuditLogSdk(payload) {
-    const { data, error } = await getSupabase()
-        .from('issue_audit_logs')
-        .insert(payload)
-        .select('id')
-        .single();
-    if (error) {
-        throw new Error(error.message);
-    }
-    return data?.id ?? null;
-}
-/**
- * Log a phase event (start, completion, or failure)
- */
-export async function logIssuePhaseEvent(params, verbose) {
-    try {
-        const payload = {
-            issue_id: params.issueId,
-            event_type: params.eventType,
-            phase: params.phase,
-            source: 'pipeline',
-            result: params.result || 'info',
-            metadata: params.metadata || {},
-            error_message: params.errorMessage || null,
-        };
-        let logId = null;
-        let usedSdk = false;
-        if (hasSupabaseSession()) {
-            try {
-                logId = await insertAuditLogSdk(payload);
-                usedSdk = true;
-            }
-            catch {
-                // Fall through to MCP
-            }
-        }
-        if (!usedSdk) {
-            const result = await callMcpEndpoint('issue_audit_logs/create', payload);
-            logId = result?.id || null;
-        }
-        if (verbose) {
-            logInfo(`✅ Logged ${params.eventType} for phase ${params.phase}`);
-        }
-        // Send email notification for phase_completed events
-        if (params.eventType === 'phase_completed') {
-            try {
-                await callMcpEndpoint('notifications/send_phase_completion_email', {
-                    issue_id: params.issueId,
-                    phase: params.phase,
-                    result: params.result || 'success',
-                    metadata: params.metadata,
-                });
-                if (verbose) {
-                    logInfo(`📧 Phase completion email sent for ${params.phase}`);
-                }
-            }
-            catch (emailError) {
-                // Email failures should not block the main operation
-                if (verbose) {
-                    logError(`Failed to send phase completion email: ${emailError instanceof Error ? emailError.message : String(emailError)}`);
-                }
-            }
-        }
-        return logId;
-    }
-    catch (error) {
-        // Always log errors, not just in verbose mode
-        logError(`Failed to log phase event: ${error instanceof Error ? error.message : String(error)}`);
-        if (verbose && error instanceof Error && error.stack) {
-            logError(`Stack trace: ${error.stack}`);
-        }
-        return null;
-    }
-}
-/**
- * Log a checklist validation event
- */
-export async function logIssueChecklistEvent(params, verbose) {
-    try {
-        const payload = {
-            issue_id: params.issueId,
-            event_type: params.eventType,
-            source: 'pipeline',
-            result: params.result || 'success',
-            metadata: {
-                checklist_id: params.checklistId,
-                ...(params.metadata || {}),
-            },
-        };
-        let logId = null;
-        let usedSdk = false;
-        if (hasSupabaseSession()) {
-            try {
-                logId = await insertAuditLogSdk(payload);
-                usedSdk = true;
-            }
-            catch {
-                // Fall through to MCP
-            }
-        }
-        if (!usedSdk) {
-            const result = await callMcpEndpoint('issue_audit_logs/create', payload);
-            logId = result?.id || null;
-        }
-        if (verbose) {
-            logInfo(`✅ Logged ${params.eventType} for checklist ${params.checklistId}`);
-        }
-        return logId;
-    }
-    catch (error) {
-        // Always log errors, not just in verbose mode
-        logError(`Failed to log checklist event: ${error instanceof Error ? error.message : String(error)}`);
-        if (verbose && error instanceof Error && error.stack) {
-            logError(`Stack trace: ${error.stack}`);
-        }
-        return null;
-    }
-}
-/**
- * Log a verification event (dual-agent verification result)
- */
-export async function logIssueVerificationEvent(params, verbose) {
-    try {
-        const eventType = params.result === 'success'
-            ? 'verification_passed'
-            : 'verification_failed';
-        const payload = {
-            issue_id: params.issueId,
-            event_type: eventType,
-            phase: params.phase,
-            source: 'pipeline',
-            result: params.result,
-            metadata: {
-                iteration: params.iteration,
-                ...params.verificationData,
-            },
-        };
-        let logId = null;
-        let usedSdk = false;
-        if (hasSupabaseSession()) {
-            try {
-                logId = await insertAuditLogSdk(payload);
-                usedSdk = true;
-            }
-            catch {
-                // Fall through to MCP
-            }
-        }
-        if (!usedSdk) {
-            const result = await callMcpEndpoint('issue_audit_logs/create', payload);
-            logId = result?.id || null;
-        }
-        if (verbose) {
-            logInfo(`✅ Logged verification ${params.result} for phase ${params.phase} (iteration ${params.iteration})`);
-        }
-        return logId;
-    }
-    catch (error) {
-        // Always log errors, not just in verbose mode
-        logError(`Failed to log verification event: ${error instanceof Error ? error.message : String(error)}`);
-        if (verbose && error instanceof Error && error.stack) {
-            logError(`Stack trace: ${error.stack}`);
-        }
-        return null;
-    }
-}

package/dist/services/branches.d.ts

@@ -1,103 +0,0 @@
-/**
- * Branches service for pipeline integration
- * Allows phases to manage branches via MCP
- */
-import { type PipelinePhaseOptions } from '../types/pipeline.js';
-export interface Branch {
-    id: string;
-    issue_id: string;
-    name: string;
-    description: string | null;
-    branch_name: string | null;
-    base_branch_id: string | null;
-    pull_request_url: string | null;
-    pull_request_number: number | null;
-    status: 'pending' | 'in_progress' | 'ready_for_review' | 'reviewed' | 'refined' | 'merged' | 'completed' | 'closed';
-    created_at: string;
-    updated_at: string;
-}
-export interface CreateBranchInput {
-    name: string;
-    description?: string;
-    branch_name?: string;
-    base_branch_id?: string;
-    status?: Branch['status'];
-}
-/**
- * List all branches for an issue
- */
-export declare function getBranches(options: PipelinePhaseOptions): Promise<Branch[]>;
-/**
- * Get the current active branch for an issue
- */
-export declare function getCurrentBranch(options: PipelinePhaseOptions): Promise<Branch | null>;
-/**
- * Create branches
- */
-export declare function createBranches(options: PipelinePhaseOptions, branches: CreateBranchInput[]): Promise<Branch[]>;
-/**
- * Update a branch
- */
-export declare function updateBranch(branchId: string, updates: Partial<Omit<Branch, 'id' | 'issue_id' | 'created_at' | 'updated_at'>>, verbose?: boolean): Promise<Branch>;
-/**
- * Clear all branches for an issue (used before re-planning)
- */
-export declare function clearBranches(options: PipelinePhaseOptions, force?: boolean): Promise<number>;
-/**
- * Format branches for context (to include in prompts)
- */
-export declare function formatBranchesForContext(branches: Branch[]): string;
-/**
- * Check if issue has multiple branches planned
- */
-export declare function hasMultipleBranches(options: PipelinePhaseOptions): Promise<boolean>;
-/**
- * Get next pending branch to work on
- */
-export declare function getNextPendingBranch(options: PipelinePhaseOptions): Promise<Branch | null>;
-/**
- * Check if all branches are completed (feat merged to main)
- */
-export declare function allBranchesCompleted(options: PipelinePhaseOptions): Promise<boolean>;
-/**
- * Get the base branch information for a branch.
- *
- * Rebase strategies based on base branch status:
- * - no base_branch_id: create from main, no rebase (first branch in chain)
- * - completed (feat merged to main): rebase onto main using --onto dev/xxx
- * - merged (dev merged to feat): create from feat/xxx, rebase onto feat/xxx using --onto dev/xxx
- * - in_progress/pending: create from dev/xxx, no rebase (base on parent dev branch)
- *
- * For 'merged' status:
- * - New branches are created from feat/xxx (which contains squashed commits)
- * - Existing branches (created from dev/xxx) are rebased onto feat/xxx
- * - Uses --onto to skip commits inherited from parent's dev branch
- * - Rebase to main happens later when base branch becomes 'completed'
- */
-export declare function getBaseBranchInfo(branch: Branch, allBranches: Branch[], mainBranch?: string): {
-    baseBranch: string;
-    rebaseTargetBranch?: string;
-    originalBaseBranch?: string;
-    needsRebase: boolean;
-    baseBranchMerged: boolean;
-    baseBranchCompleted?: boolean;
-};
-/**
- * Get branch by ID
- */
-export declare function getBranchById(branchId: string, verbose?: boolean): Promise<Branch | null>;
-/**
- * Get the branch that is ready for review (for post-implementation phases)
- * Returns the first branch with status 'ready_for_review'
- */
-export declare function getReadyForReviewBranch(options: PipelinePhaseOptions): Promise<Branch | null>;
-/**
- * Get the branch that has been reviewed (for code-refine phase)
- * Returns the first branch with status 'reviewed'
- */
-export declare function getReviewedBranch(options: PipelinePhaseOptions): Promise<Branch | null>;
-/**
- * Get the branch that is in progress (in_progress or ready_for_review)
- * Useful for phases that need to work on the current active branch
- */
-export declare function getActiveBranch(options: PipelinePhaseOptions): Promise<Branch | null>;