edsger 0.54.0 → 0.55.0

package/dist/commands/sync-sentry-issues/index.js

@@ -0,0 +1,73 @@
+/**
+ * CLI command: `edsger sync-sentry-issues <productId>`
+ *
+ * Reads Sentry credentials from process.env (populated by `edsger config
+ * set` via ~/.edsger/env.json or by real environment variables). For an
+ * MVP we intentionally don't put per-product Sentry config in the
+ * database — the auth token is user-scoped, and org/project rarely
+ * change. If the friction shows up, follow up by adding columns on the
+ * products table and a settings UI.
+ */
+import { syncSentryIssues } from '../../phases/sync-sentry-issues/index.js';
+import { logError, logInfo, logSuccess } from '../../utils/logger.js';
+/**
+ * Pull Sentry creds from env. Returns a list of missing variable names so
+ * the CLI can give one clear "set these" message instead of dribbling
+ * errors.
+ */
+function readSentryEnv() {
+    const authToken = process.env.SENTRY_AUTH_TOKEN ?? '';
+    const org = process.env.SENTRY_ORG ?? '';
+    const project = process.env.SENTRY_PROJECT ?? '';
+    // SENTRY_URL is the official sentry-cli convention. SENTRY_BASE_URL is
+    // the older name we shipped first; accept both with the new one winning
+    // so users with the old desktop install + new CLI keep working.
+    const url = process.env.SENTRY_URL || process.env.SENTRY_BASE_URL || undefined;
+    const missing = [];
+    if (!authToken) {
+        missing.push('SENTRY_AUTH_TOKEN');
+    }
+    if (!org) {
+        missing.push('SENTRY_ORG');
+    }
+    if (!project) {
+        missing.push('SENTRY_PROJECT');
+    }
+    if (missing.length > 0) {
+        return { ok: false, missing };
+    }
+    return { ok: true, env: { authToken, org, project, baseUrl: url } };
+}
+export async function runSyncSentryIssues(productId, options = {}) {
+    const { verbose } = options;
+    logInfo(`Starting Sentry issue sync for product ${productId}`);
+    const env = readSentryEnv();
+    if (!env.ok) {
+        logError(`Sentry not configured. Missing: ${env.missing.join(', ')}. ` +
+            `Configure in the desktop app (Product Settings → Credentials) or ` +
+            `set them with \`edsger config set <KEY>=<VALUE>\`. ` +
+            `Optional: SENTRY_URL for self-hosted Sentry.`);
+        process.exit(1);
+    }
+    const result = await syncSentryIssues({
+        productId,
+        authToken: env.env.authToken,
+        org: env.env.org,
+        project: env.env.project,
+        baseUrl: env.env.baseUrl,
+        verbose,
+    });
+    if (result.status === 'success') {
+        logSuccess(`Sentry sync completed: ${result.message}`);
+        if (result.source) {
+            logInfo(`Source: ${result.source}`);
+        }
+        if (result.fetchedCount !== undefined) {
+            logInfo(`Fetched ${result.fetchedCount} · created ${result.createdCount ?? 0} · updated ${result.updatedCount ?? 0} · refreshed ${result.refreshedCount ?? 0} · deleted ${result.deletedCount ?? 0}`);
+        }
+    }
+    else {
+        logError(`Sentry sync failed: ${result.message}`);
+        process.exit(1);
+    }
+}

package/dist/commands/technical-design/index.d.ts

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

package/dist/commands/technical-design/index.js

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

package/dist/commands/test-cases-analysis/index.d.ts

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

package/dist/commands/test-cases-analysis/index.js

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

package/dist/commands/user-stories-analysis/index.d.ts

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

package/dist/commands/user-stories-analysis/index.js

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

package/dist/commands/workflow/executors/phase-executor.js

@@ -130,9 +130,7 @@ async function validateAndLogChecklists(options, name, checklistContext, issueId
     }
 }
 // Higher-order function for phase execution
-export const createPhaseRunner = (phaseConfig) => 
-// eslint-disable-next-line complexity
-async (options, config) => {
+export const createPhaseRunner = (phaseConfig) => async (options, config) => {
     const { issueId, verbose } = options;
     const { name, execute } = phaseConfig;
     // Track phase duration for logging
@@ -143,7 +141,11 @@ async (options, config) => {
         if (verbose) {
             logDebug(`Checking approval before executing ${name} phase...`, verbose);
         }
-        const approvalCheck = await checkApprovalBeforePhaseExecution(issueId, verbose);
+        // The approval system keys configs on snake_case phase names
+        // (matching the workflow JSONB vocabulary), so convert from the
+        // kebab-case orchestrator name before checking.
+        const phaseSnakeCase = name.replace(/-/g, '_');
+        const approvalCheck = await checkApprovalBeforePhaseExecution(issueId, phaseSnakeCase, verbose);
         if (!approvalCheck.canProceed) {
             // Current status requires approval but hasn't been approved yet
             // Block phase execution and return blocked result

package/dist/commands/workflow/phase-orchestrator.js

@@ -36,7 +36,6 @@ const logAndMarkPhaseCompleted = async (result, verbose) => {
  * Orchestrate phase execution based on execution mode
  * Routes to appropriate phase sequence based on mode (only_*, from_*, full_pipeline)
  */
-// eslint-disable-next-line complexity
 export const runPipelineByMode = async (options, config, executionMode) => {
     const { issueId, verbose } = options;
     if (verbose) {

package/dist/config/issue-status.d.ts

@@ -1,56 +1,29 @@
 /**
- * Issue status configuration
- * Defines the progression order and mappings for issue statuses
- */
-import type { IssueStatus } from '../types/index.js';
-/**
- * Status progression order - higher index means more advanced status
- * This defines the allowed forward progression through the issue workflow
- *
- * Business Logic Rules:
- * - Issues can only move forward or stay at the same status level
- * - No regression to earlier stages is allowed (e.g., cannot go back to 'backlog' from 'code_implementation')
- * - Status updates preserve development momentum and prevent accidental rollbacks
+ * Issue lifecycle status configuration.
  *
- * Special Cases:
- * - testing_failed → testing_in_progress: Allowed for retry attempts after fixing issues
- * - Same status → same status: Allowed for retries, reprocessing, or status confirmation
- * - code_refine_verification → code_refine: Handled by specific retry logic, not this progression
+ * Under the 2D model, issues.status carries 7 lifecycle values. Phase
+ * progress lives in the workflow JSONB column instead.
  *
- * Note: The order reflects the typical development workflow from initial planning
- * through to final shipping. All status values must match the database constraint
- * in migration 20251019000000_update_feature_status_constraint.sql
+ * The map kebab-case→workflow used by the worker is in
+ *   ../api/issues/status-updater.ts (PHASE_NAME_TO_WORKFLOW)
+ * — this file only owns the lifecycle status enum + ordering used by
+ * isForwardProgression().
  */
-export declare const STATUS_PROGRESSION_ORDER: readonly IssueStatus[];
+import type { IssueStatus } from '../types/index.js';
 /**
- * Phase to status mapping
- * Maps pipeline phase names to their corresponding issue statuses
- *
- * This mapping ensures that each pipeline phase updates the issue to the appropriate
- * status. Phase names use kebab-case (e.g., 'issue-analysis') while status values
- * use snake_case (e.g., 'issue_analysis') to match database schema.
+ * Lifecycle progression order. Used by isForwardProgression() to reject
+ * regressions — e.g. you can move backlog → ready_for_ai but not the
+ * other way around.
  *
- * All status values must match the database constraint in migration 20251019000000_update_feature_status_constraint.sql
- *
- * If a phase is not found in this mapping, updateIssueStatusForPhase will return null
- * and skip the status update to prevent unintended regression to 'backlog'.
+ * Special-cases (handled in isForwardProgression):
+ *   - any status → archived: always allowed
+ *   - archived → backlog: always allowed (unarchive)
  */
-export declare const PHASE_STATUS_MAP: Record<string, IssueStatus>;
+export declare const STATUS_PROGRESSION_ORDER: readonly IssueStatus[];
 /**
- * Human-selectable statuses
- * These are the statuses that a human user can manually set.
- *
- * Excluded statuses (system-managed):
- * - *_verification statuses: Automatically entered after completing the corresponding phase
- * - testing_in_progress: Automatically set when functional testing begins
- * - testing_passed: Automatically set when all tests pass
- * - testing_failed: Automatically set when tests fail
- *
- * These excluded statuses should not be shown in UI dropdowns for manual status changes
- * because they represent intermediate states that are managed by the workflow system.
+ * Statuses a human can pick from a dropdown. AI-managed states
+ * (assigned_to_ai, in_progress) are written by the worker and not
+ * exposed for manual selection.
  */
 export declare const HUMAN_SELECTABLE_STATUSES: readonly IssueStatus[];
-/**
- * Check if a status can be manually selected by a human user
- */
 export declare function isHumanSelectableStatus(status: IssueStatus): boolean;

package/dist/config/issue-status.js

@@ -1,130 +1,44 @@
 /**
- * Issue status configuration
- * Defines the progression order and mappings for issue statuses
- */
-/**
- * Status progression order - higher index means more advanced status
- * This defines the allowed forward progression through the issue workflow
+ * Issue lifecycle status configuration.
  *
- * Business Logic Rules:
- * - Issues can only move forward or stay at the same status level
- * - No regression to earlier stages is allowed (e.g., cannot go back to 'backlog' from 'code_implementation')
- * - Status updates preserve development momentum and prevent accidental rollbacks
+ * Under the 2D model, issues.status carries 7 lifecycle values. Phase
+ * progress lives in the workflow JSONB column instead.
  *
- * Special Cases:
- * - testing_failed → testing_in_progress: Allowed for retry attempts after fixing issues
- * - Same status → same status: Allowed for retries, reprocessing, or status confirmation
- * - code_refine_verification → code_refine: Handled by specific retry logic, not this progression
+ * The map kebab-case→workflow used by the worker is in
+ *   ../api/issues/status-updater.ts (PHASE_NAME_TO_WORKFLOW)
+ * — this file only owns the lifecycle status enum + ordering used by
+ * isForwardProgression().
+ */
+/**
+ * Lifecycle progression order. Used by isForwardProgression() to reject
+ * regressions — e.g. you can move backlog → ready_for_ai but not the
+ * other way around.
  *
- * Note: The order reflects the typical development workflow from initial planning
- * through to final shipping. All status values must match the database constraint
- * in migration 20251019000000_update_feature_status_constraint.sql
+ * Special-cases (handled in isForwardProgression):
+ *   - any status → archived: always allowed
+ *   - archived → backlog: always allowed (unarchive)
  */
 export const STATUS_PROGRESSION_ORDER = [
     'backlog',
     'ready_for_ai',
     'assigned_to_ai',
-    'issue_analysis',
-    'issue_analysis_verification',
-    'user_stories_analysis',
-    'user_stories_analysis_verification',
-    'test_cases_analysis',
-    'test_cases_analysis_verification',
-    'technical_design',
-    'technical_design_verification',
-    'branch_planning',
-    'branch_planning_verification',
-    'code_implementation',
-    'code_implementation_verification',
-    'pr_splitting',
-    'pr_splitting_verification',
-    'pr_execution',
-    'code_refine',
-    'code_refine_verification',
-    'bug_fixing',
-    'code_review',
-    'functional_testing',
-    'testing_in_progress',
-    'testing_passed',
-    'testing_failed',
-    'ready_for_review',
+    'in_progress',
     'shipped',
+    'failed',
     'archived',
 ];
 /**
- * Phase to status mapping
- * Maps pipeline phase names to their corresponding issue statuses
- *
- * This mapping ensures that each pipeline phase updates the issue to the appropriate
- * status. Phase names use kebab-case (e.g., 'issue-analysis') while status values
- * use snake_case (e.g., 'issue_analysis') to match database schema.
- *
- * All status values must match the database constraint in migration 20251019000000_update_feature_status_constraint.sql
- *
- * If a phase is not found in this mapping, updateIssueStatusForPhase will return null
- * and skip the status update to prevent unintended regression to 'backlog'.
- */
-export const PHASE_STATUS_MAP = {
-    'issue-analysis': 'issue_analysis',
-    'issue-analysis-verification': 'issue_analysis_verification',
-    'user-stories-analysis': 'user_stories_analysis',
-    'user-stories-analysis-verification': 'user_stories_analysis_verification',
-    'test-cases-analysis': 'test_cases_analysis',
-    'test-cases-analysis-verification': 'test_cases_analysis_verification',
-    'technical-design': 'technical_design',
-    'technical-design-verification': 'technical_design_verification',
-    'branch-planning': 'branch_planning',
-    'branch-planning-verification': 'branch_planning_verification',
-    'code-implementation': 'code_implementation',
-    'code-implementation-verification': 'code_implementation_verification',
-    'pr-splitting': 'pr_splitting',
-    'pr-splitting-verification': 'pr_splitting_verification',
-    'pr-execution': 'pr_execution',
-    'code-refine': 'code_refine',
-    'code-refine-verification': 'code_refine_verification',
-    'bug-fixing': 'bug_fixing',
-    'code-review': 'code_review',
-    'functional-testing': 'functional_testing',
-    'testing-in-progress': 'testing_in_progress',
-    'testing-passed': 'testing_passed',
-    'testing-failed': 'testing_failed',
-    'ready-for-review': 'ready_for_review',
-};
-/**
- * Human-selectable statuses
- * These are the statuses that a human user can manually set.
- *
- * Excluded statuses (system-managed):
- * - *_verification statuses: Automatically entered after completing the corresponding phase
- * - testing_in_progress: Automatically set when functional testing begins
- * - testing_passed: Automatically set when all tests pass
- * - testing_failed: Automatically set when tests fail
- *
- * These excluded statuses should not be shown in UI dropdowns for manual status changes
- * because they represent intermediate states that are managed by the workflow system.
+ * Statuses a human can pick from a dropdown. AI-managed states
+ * (assigned_to_ai, in_progress) are written by the worker and not
+ * exposed for manual selection.
  */
 export const HUMAN_SELECTABLE_STATUSES = [
     'backlog',
     'ready_for_ai',
-    'issue_analysis',
-    'user_stories_analysis',
-    'test_cases_analysis',
-    'technical_design',
-    'branch_planning',
-    'code_implementation',
-    'pr_splitting',
-    'pr_execution',
-    'code_refine',
-    'bug_fixing',
-    'code_review',
-    'functional_testing',
-    'ready_for_review',
     'shipped',
     'archived',
+    'failed',
 ];
-/**
- * Check if a status can be manually selected by a human user
- */
 export function isHumanSelectableStatus(status) {
     return HUMAN_SELECTABLE_STATUSES.includes(status);
 }

package/dist/index.js

@@ -13,20 +13,29 @@ import { runBuild } from './commands/build/index.js';
 import { runChecklists } from './commands/checklists/index.js';
 import { runCodeReview } from './commands/code-review/index.js';
 import { runConfigGet, runConfigList, runConfigSet, runConfigUnset, } from './commands/config/index.js';
+import { runFinancingDeck } from './commands/financing-deck/index.js';
+import { runFindArchitecture } from './commands/find-architecture/index.js';
 import { runFindBugs } from './commands/find-bugs/index.js';
 import { runFindFeatures } from './commands/find-features/index.js';
 import { parseCategoriesOption, runFindSmells, } from './commands/find-smells/index.js';
 import { runGrowthAnalysis } from './commands/growth-analysis/index.js';
 import { runInit } from './commands/init/index.js';
 import { runIntelligence } from './commands/intelligence/index.js';
+import { runIssueAnalysisCommand } from './commands/issue-analysis/index.js';
 import { runPRResolve } from './commands/pr-resolve/index.js';
 import { runPRReview } from './commands/pr-review/index.js';
 import { runRefactor } from './commands/refactor/refactor.js';
 import { runReleaseSyncCommand } from './commands/release-sync/index.js';
 import { runRunSheetCommand } from './commands/run-sheet/index.js';
 import { runSmokeTestCommand } from './commands/smoke-test/index.js';
+import { runSyncGithubIssues } from './commands/sync-github-issues/index.js';
+import { runSyncSentryIssues } from './commands/sync-sentry-issues/index.js';
 import { runTaskWorker } from './commands/task-worker/index.js';
+import { runTechnicalDesignCommand } from './commands/technical-design/index.js';
+import { runTestCasesAnalysisCommand } from './commands/test-cases-analysis/index.js';
+import { runUserStoriesAnalysisCommand } from './commands/user-stories-analysis/index.js';
 import { runWorkflow } from './commands/workflow/index.js';
+import { DEFAULT_MAX_FILES as FIND_ARCHITECTURE_DEFAULT_MAX_FILES } from './phases/find-architecture/index.js';
 import { DEFAULT_MAX_FILES as FIND_SMELLS_DEFAULT_MAX_FILES } from './phases/find-smells/index.js';
 import { SMELL_CATEGORIES, } from './phases/find-smells/types.js';
 import { logError, logInfo } from './utils/logger.js';
@@ -147,6 +156,27 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger financing-deck <productId>
+// ============================================================
+program
+    .command('financing-deck <productId>')
+    .description('Draft an investor pitch deck for a product (AI-generated)')
+    .requiredOption('--target-stage <stage>', 'Target stage: pre_seed | seed | series_a | series_b | series_c | growth')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (productId, opts) => {
+    try {
+        await runFinancingDeck({
+            financingDeck: productId,
+            financingTargetStage: opts.targetStage,
+            verbose: opts.verbose,
+        });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger intel <productId>
 // ============================================================
 program
@@ -240,18 +270,26 @@ program
     }
 });
 // ============================================================
-// Subcommand: edsger checklists <productId>
+// Subcommand: edsger checklists [productId] [--team-id <id>]
 // ============================================================
 program
-    .command('checklists <productId>')
-    .description('Analyse a local directory and sync product checklists (create/update/delete) using AI')
+    .command('checklists [productId]')
+    .description('Analyse a local directory and sync product OR team checklists (create/update/delete) using AI. Pass a product ID positionally for product scope, or --team-id for team scope.')
     .option('-v, --verbose', 'Verbose output')
     .option('--dir <path>', 'Directory to analyse (defaults to current working directory)')
     .option('--prompt <text>', 'Additional instructions for the AI agent')
+    .option('--team-id <id>', 'Sync TEAM-level checklists for this team instead of a product. The directory is treated as team standards / reference material.')
     .action(async (productId, opts) => {
     try {
+        if (!productId && !opts.teamId) {
+            throw new Error('Provide a product ID positionally or pass --team-id <id> for team scope.');
+        }
+        if (productId && opts.teamId) {
+            throw new Error('Pass either a product ID or --team-id, not both.');
+        }
         await runChecklists({
             checklistsProductId: productId,
+            checklistsTeamId: opts.teamId,
             checklistsDir: opts.dir,
             checklistsPrompt: opts.prompt,
             verbose: opts.verbose,
@@ -301,6 +339,70 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger issue-analysis <issueId>
+// ============================================================
+program
+    .command('issue-analysis <issueId>')
+    .description('Generate or refine the execution plan for an issue (issue_analysis phase, with verification loop)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (issueId, opts) => {
+    try {
+        await runIssueAnalysisCommand({ issueId, verbose: opts.verbose });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
+// Subcommand: edsger user-stories-analysis <issueId>
+// ============================================================
+program
+    .command('user-stories-analysis <issueId>')
+    .description('Generate or refine user stories for an issue (user_stories_analysis phase, with verification loop)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (issueId, opts) => {
+    try {
+        await runUserStoriesAnalysisCommand({ issueId, verbose: opts.verbose });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
+// Subcommand: edsger test-cases-analysis <issueId>
+// ============================================================
+program
+    .command('test-cases-analysis <issueId>')
+    .description('Generate or refine test cases for an issue (test_cases_analysis phase, with verification loop)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (issueId, opts) => {
+    try {
+        await runTestCasesAnalysisCommand({ issueId, verbose: opts.verbose });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
+// Subcommand: edsger technical-design <issueId>
+// ============================================================
+program
+    .command('technical-design <issueId>')
+    .description('Generate or refine the technical design for an issue (technical_design phase, with verification loop)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (issueId, opts) => {
+    try {
+        await runTechnicalDesignCommand({ issueId, verbose: opts.verbose });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger smoke-test <releaseId>
 // ============================================================
 program
@@ -384,6 +486,41 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger sync-github-issues <productId>
+// ============================================================
+program
+    .command('sync-github-issues <productId>')
+    .description("Mirror the product's connected GitHub repo issues into the local issues list (handles new, updated, closed, and deleted)")
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (productId, opts) => {
+    try {
+        await runSyncGithubIssues(productId, opts);
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
+// Subcommand: edsger sync-sentry-issues <productId>
+//
+// Requires SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT in env (set via
+// `edsger config set`). Optional SENTRY_BASE_URL for self-hosted Sentry.
+// ============================================================
+program
+    .command('sync-sentry-issues <productId>')
+    .description('Mirror Sentry project issues into the local issues list (requires SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT env)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (productId, opts) => {
+    try {
+        await runSyncSentryIssues(productId, opts);
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger find-features <productId>
 // ============================================================
 program
@@ -443,6 +580,31 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger find-architecture <productId>
+// ============================================================
+program
+    .command('find-architecture <productId>')
+    .description("AI-audit a product's repository for architectural concerns (layering, coupling, cycles, missing/duplicated abstractions, responsibility creep) and file each new finding as an issue")
+    .option('--full', 'Force a full scan even if previous-scan state exists')
+    .option('--branch <name>', 'Branch to scan (defaults to repo default branch)')
+    .option('--max-files <n>', `Upper bound on files the auditor may Read (default ${FIND_ARCHITECTURE_DEFAULT_MAX_FILES})`, (value) => {
+    const n = parseInt(value, 10);
+    if (Number.isNaN(n) || n <= 0) {
+        throw new Error('--max-files must be a positive integer');
+    }
+    return n;
+})
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (productId, opts) => {
+    try {
+        await runFindArchitecture(productId, opts);
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger pr-resolve <productId>
 // ============================================================
 program
@@ -475,7 +637,17 @@ program
     .option('--concurrency <number>', 'Max concurrent issues to process (default: 3)', parseInt)
     .option('-c, --config <path>', 'Path to config file')
     .option('-v, --verbose', 'Verbose output');
-program.action(async (options) => {
+program.action(async (options, command) => {
+    // Commander silently falls through to this default action when the user
+    // passes a subcommand name that isn't registered (e.g. an old binary that
+    // doesn't yet know about `sync-sentry-issues`). That makes version-skew
+    // bugs look like the agent inexplicably running with the wrong intent.
+    // Treat any leftover positional arg as an unknown command and abort.
+    if (command.args.length > 0) {
+        logError(`Unknown command: ${command.args[0]}`);
+        logError(`Run 'edsger --help' to see available commands.`);
+        process.exit(1);
+    }
     try {
         await runEdsger(options);
     }

package/dist/phases/app-store-generation/agent.js

@@ -94,7 +94,8 @@ export async function executeAppStoreQuery(currentPrompt, systemPrompt, config,
                     logDebug(`${content.text}`, verbose);
                 }
                 else if (content.type === 'tool_use') {
-                    const desc = content.input?.description || content.input?.command || 'Running...';
+                    const input = (content.input ?? {});
+                    const desc = input.description ?? input.command ?? 'Running...';
                     logInfo(`[Turn ${turnCount}] ${content.name}: ${typeof desc === 'string' ? desc.slice(0, 120) : 'Running...'}`);
                 }
             }