edsger 0.57.0 → 0.59.0

package/dist/api/cross-product.js

@@ -56,7 +56,6 @@ export async function listAllReadyIssues(verbose) {
             const allIssues = (data || []).map((row) => {
                 // The `product` join lands as a nested object; lift its name onto
                 // the row to keep the wire shape stable.
-                // eslint-disable-next-line @typescript-eslint/no-explicit-any -- shape from PostgREST join
                 const r = row;
                 return {
                     ...r,

package/dist/api/issues/issue-utils.js

@@ -41,7 +41,6 @@ export async function claimNextIssue(productId, verbose) {
             }
             // RPC returns rows with `issue_*` prefixed column names — unwrap to
             // the IssueInfo shape callers already consume.
-            // eslint-disable-next-line @typescript-eslint/no-explicit-any -- raw RPC row
             const r = row;
             const issue = {
                 id: r.issue_id,

package/dist/api/issues/update-issue.js

@@ -91,7 +91,7 @@ export async function markWorkflowPhaseCompleted(issueId, phaseName, verbose) {
                 // Fall through to MCP
             }
         }
-        if (issue == null) {
+        if (!issue) {
             const response = (await callMcpEndpoint('issues/get', {
                 issue_id: issueId,
             }));

package/dist/commands/agent-workflow/chat-worker.js

@@ -354,7 +354,7 @@ function startRealtime() {
             registerChannel(payload.new);
             // A channel created with messages already in it (unlikely but
             // possible if INSERTs race) deserves an immediate sweep.
-            const id = payload.new.id;
+            const { id } = payload.new;
             if (id) {
                 void claimAndProcess(id);
             }

package/dist/commands/checklists/index.js

@@ -116,7 +116,7 @@ export async function runChecklists(options) {
         ? createChecklistsMcpServer({ kind: 'team', teamId: teamId })
         : createChecklistsMcpServer({
             kind: 'product',
-            productId: productId,
+            productId,
         });
     const promptParts = isTeamScope
         ? [

package/dist/commands/product-techniques/index.d.ts

@@ -0,0 +1,15 @@
+/**
+ * CLI command: edsger product-techniques <productId> --techniques-id <id>
+ *
+ * Clones the product's repo, asks Claude to write a catalogue of the
+ * techniques the repo uses, and stores the markdown body in
+ * product_techniques. The desktop UI creates a pending row first then
+ * invokes the CLI with --techniques-id; the CLI flips status running →
+ * success/failed and populates the content/summary fields.
+ */
+export interface ProductTechniquesCliOptions {
+    techniquesId: string;
+    guidance?: string;
+    verbose?: boolean;
+}
+export declare function runProductTechniques(productId: string, options: ProductTechniquesCliOptions): Promise<void>;

package/dist/commands/product-techniques/index.js

@@ -0,0 +1,37 @@
+/**
+ * CLI command: edsger product-techniques <productId> --techniques-id <id>
+ *
+ * Clones the product's repo, asks Claude to write a catalogue of the
+ * techniques the repo uses, and stores the markdown body in
+ * product_techniques. The desktop UI creates a pending row first then
+ * invokes the CLI with --techniques-id; the CLI flips status running →
+ * success/failed and populates the content/summary fields.
+ */
+import { runProductTechniquesPhase } from '../../phases/product-techniques/index.js';
+import { logError, logInfo, logSuccess } from '../../utils/logger.js';
+export async function runProductTechniques(productId, options) {
+    const { techniquesId, guidance, verbose } = options;
+    if (!productId) {
+        throw new Error('Product ID is required for product-techniques');
+    }
+    if (!techniquesId) {
+        throw new Error('--techniques-id is required (the pending product_techniques row id)');
+    }
+    logInfo(`Starting techniques generation for product ${productId}`);
+    const result = await runProductTechniquesPhase({
+        productId,
+        techniquesId,
+        guidance,
+        verbose,
+    });
+    if (result.status === 'success') {
+        logSuccess(result.message);
+        if (result.summary) {
+            logInfo(`\nSummary: ${result.summary}`);
+        }
+    }
+    else {
+        logError(result.message);
+        process.exit(1);
+    }
+}

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

@@ -3,7 +3,7 @@
  */
 import { checkApprovalBeforePhaseExecution } from '../../../api/issues/approval-checker.js';
 import { updateIssueStatusForPhase } from '../../../api/issues/index.js';
-import { logIssuePhaseEvent, } from '../../../services/audit-logs.js';
+import { logIssuePhaseEvent } from '../../../services/audit-logs.js';
 import { getChecklistsForPhase, processChecklistItemResultsFromResponse, processChecklistResultsFromResponse, validateChecklistsForPhase, validateRequiredChecklistResults, } from '../../../services/checklist.js';
 import { runHooksForPhase } from '../../../services/phase-hooks/index.js';
 import { logDebug, logInfo, logWarning } from '../../../utils/logger.js';

package/dist/index.js

@@ -19,17 +19,18 @@ 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 { runScreenFlow } from './commands/screen-flow/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 { runProductTechniques } from './commands/product-techniques/index.js';
 import { runProductTestCases } from './commands/product-test-cases/index.js';
 import { runQualityBenchmarkCli } from './commands/quality-benchmark/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 { runScreenFlow } from './commands/screen-flow/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';
@@ -694,6 +695,28 @@ program
     }
 });
 // ============================================================
+// Subcommand: edsger product-techniques <productId>
+// ============================================================
+program
+    .command('product-techniques <productId>')
+    .description("Generate a catalogue of the techniques a product's repo uses (languages, frameworks, patterns, state idioms, build & deploy, notable bits). Writes the result to the pending product_techniques row identified by --techniques-id.")
+    .requiredOption('--techniques-id <id>', 'Pending product_techniques row id to populate')
+    .option('-g, --guidance <text>', 'Human direction for the AI (focus areas, exclusions)')
+    .option('-v, --verbose', 'Verbose output')
+    .action(async (productId, opts) => {
+    try {
+        await runProductTechniques(productId, {
+            techniquesId: opts.techniquesId,
+            guidance: opts.guidance,
+            verbose: opts.verbose,
+        });
+    }
+    catch (error) {
+        logError(error instanceof Error ? error.message : String(error));
+        process.exit(1);
+    }
+});
+// ============================================================
 // Subcommand: edsger pr-resolve <productId>
 // ============================================================
 program

package/dist/phases/analyze-logs/index.js

@@ -5,11 +5,11 @@
  * user's session logs (only if the latest log is >1 hour old), and creates
  * product_user_feedbacks for any issues or improvement suggestions found.
  */
+import { callMcpEndpoint } from '../../api/mcp-client.js';
 import { getProduct } from '../../api/products.js';
 import { getPendingLogsByUser, markLogsAnalyzed, } from '../../services/product-logs.js';
 import { getSupabase, hasSupabaseSession } from '../../supabase/client.js';
 import { logError, logInfo, logSuccess } from '../../utils/logger.js';
-import { callMcpEndpoint } from '../../api/mcp-client.js';
 import { executeLogAnalysis } from './agent.js';
 import { createAnalyzeLogsSystemPrompt, createAnalyzeLogsUserPrompt, } from './prompts.js';
 /**

package/dist/phases/bug-fixing/context-fetcher.js

@@ -41,8 +41,10 @@ export async function fetchBugFixingContext(issueId, verbose) {
                     // Fall through to MCP
                 }
             }
-            if (raw == null) {
-                const testReportResult = (await callMcpEndpoint('test_reports/latest', { issue_id: issueId }));
+            if (!raw) {
+                const testReportResult = (await callMcpEndpoint('test_reports/latest', {
+                    issue_id: issueId,
+                }));
                 raw = testReportResult.test_report ?? null;
             }
             if (raw) {

package/dist/phases/find-features/index.js

@@ -267,7 +267,7 @@ async function fetchIntelligenceReports(productId, focusReportId) {
                 if (error) {
                     throw new Error(error.message);
                 }
-                reports = (data || []);
+                reports = data || [];
                 usedSdk = true;
             }
             catch {

package/dist/phases/output-contracts.js

@@ -897,46 +897,57 @@ You MUST end your response with a JSON object containing the code refine results
 \`\`\`
 `,
     'screen-flow': `
-**CRITICAL — Output Format**:
+**CRITICAL — How to return the result**:
 
-After finishing your investigation, emit a single fenced code block tagged \`screen_flow\` containing the structured extraction. Do not emit any other JSON blocks.
+Return the extraction by calling the MCP tool
+\`mcp__screen-flow__submit_screen_flow\` **exactly once** with three arguments:
 
-\`\`\`screen_flow
-{
-  "summary": "1-3 sentence narrative of what kind of app this is and its primary user flows",
-  "nodes": [
-    {
-      "slug": "login",
-      "name": "Login",
-      "route": "/signin",
-      "file": "src/pages/Login.tsx",
-      "kind": "page",
-      "layout": "centered",
-      "header": { "title": "Sign in", "actions": [{ "label": "Sign up", "variant": "ghost" }] },
-      "body": [
-        {
-          "type": "form",
-          "submitLabel": "Sign in",
-          "fields": [
-            { "label": "Email", "kind": "email", "required": true },
-            { "label": "Password", "kind": "password", "required": true }
-          ]
-        }
-      ]
-    }
+- \`summary\` — 1-3 sentence narrative of what kind of app this is and its primary user flows
+- \`nodes\` — array of ScreenSchema objects (every user-facing screen, modal, drawer, tab, or named state)
+- \`edges\` — array of ScreenEdge objects (transitions between screens)
+
+The tool validates the arguments against the schema. If it returns an error,
+fix the issue it describes and call the tool again. After a successful call,
+end your turn — do not also paste the same data as a fenced text block.
+
+You can also call \`mcp__screen-flow__record_progress({ phase, message })\` at
+each phase boundary (detection / routing / screens / transitions / submission)
+to keep the user informed during long runs. This is observability only — it
+does not affect the extraction.
+
+ScreenSchema fields:
+- \`slug\` (unique within the flow), \`name\`, \`route?\`, \`file?\`
+- \`kind\`: one of \`page\`, \`modal\`, \`drawer\`, \`tab\`, \`state\`
+- \`layout\`: one of \`centered\`, \`sidebar\`, \`split\`, \`list-detail\`, \`tabs\`, \`stacked\`
+- \`header?\`: \`{ title, subtitle?, back?, actions?: [{ label, variant?, icon? }] }\`
+- \`body\`: array of sections; each section \`type\` is one of \`form\`, \`list\`, \`card-grid\`, \`table\`, \`kanban\`, \`text\`, \`image\`, \`chart\`, \`stats\`, \`empty-state\`, \`tabs\`, \`custom\`
+
+ScreenEdge fields:
+- \`fromSlug\`, \`toSlug\` (both MUST appear in nodes), \`triggerLabel\`, \`triggerFile?\`
+- \`kind\`: one of \`navigate\`, \`modal\`, \`redirect\`, \`back\`
+
+Schematic example of the tool call:
+
+\`\`\`
+submit_screen_flow({
+  summary: "Two-screen demo: sign in then land on home.",
+  nodes: [
+    { slug: "login", name: "Login", route: "/signin", file: "src/pages/Login.tsx",
+      kind: "page", layout: "centered",
+      header: { title: "Sign in", actions: [{ label: "Sign up", variant: "ghost" }] },
+      body: [{ type: "form", submitLabel: "Sign in", fields: [
+        { label: "Email", kind: "email", required: true },
+        { label: "Password", kind: "password", required: true }
+      ]}]
+    },
+    { slug: "home", name: "Home", route: "/", file: "src/pages/Home.tsx",
+      kind: "page", layout: "sidebar", body: [] }
   ],
-  "edges": [
-    {
-      "fromSlug": "login",
-      "toSlug": "home",
-      "triggerLabel": "Submit credentials",
-      "triggerFile": "src/pages/Login.tsx",
-      "kind": "navigate"
-    }
+  edges: [
+    { fromSlug: "login", toSlug: "home", triggerLabel: "Submit credentials",
+      triggerFile: "src/pages/Login.tsx", kind: "navigate" }
   ]
-}
+})
 \`\`\`
-
-All node \`slug\` values must be unique. Every \`fromSlug\` / \`toSlug\` in edges must reference a slug that appears in \`nodes\`. Section \`type\` values are restricted to: \`form\`, \`list\`, \`card-grid\`, \`table\`, \`kanban\`, \`text\`, \`image\`, \`chart\`, \`stats\`, \`empty-state\`, \`tabs\`, \`custom\`. Edge \`kind\` values are restricted to: \`navigate\`, \`modal\`, \`redirect\`, \`back\`.
 `,
 };

package/dist/phases/pr-shared/agent-utils.d.ts

@@ -24,16 +24,24 @@ export declare function createPromptGenerator(prompt: string): AsyncGenerator<{
 }>;
 /**
  * Extract text content from assistant message content array.
+ *
+ * When `verbose`, also surfaces tool_use / tool_result blocks via
+ * logDebug so it's visible whether the agent is making MCP / file /
+ * bash calls — without these, a long-running session looks frozen
+ * between text emissions.
  */
 export declare function extractTextFromContent(content: any[], verbose?: boolean): string;
 /**
  * Try to parse a JSON result from agent response text.
- * Looks for ```json code blocks first, then falls back to raw JSON parsing.
- * Returns the parsed object or null on failure.
+ * Tries a custom fenceTag (e.g. ```screen_flow) first when provided, then
+ * ```json, then falls back to raw JSON parsing. Returns the parsed object or
+ * null on failure.
  */
-export declare function tryParseJsonFromResponse(responseText: string): unknown | null;
+export declare function tryParseJsonFromResponse(responseText: string, fenceTag?: string): unknown | null;
 /**
  * Extract a specific keyed result from agent response.
  * e.g., tryExtractResult(text, 'review_result') extracts the review_result key.
+ * The key is also tried as the fenced code-block tag so phases whose output
+ * contract uses a custom fence (e.g. ```screen_flow) parse correctly.
  */
 export declare function tryExtractResult(responseText: string, key: string): unknown | null;

package/dist/phases/pr-shared/agent-utils.js

@@ -23,6 +23,11 @@ export async function* createPromptGenerator(prompt) {
 }
 /**
  * Extract text content from assistant message content array.
+ *
+ * When `verbose`, also surfaces tool_use / tool_result blocks via
+ * logDebug so it's visible whether the agent is making MCP / file /
+ * bash calls — without these, a long-running session looks frozen
+ * between text emissions.
  */
 export function extractTextFromContent(
 // eslint-disable-next-line @typescript-eslint/no-explicit-any
@@ -33,16 +38,50 @@ content, verbose) {
             text += `${item.text}\n`;
             logDebug(item.text, verbose);
         }
+        else if (verbose && item.type === 'tool_use') {
+            logDebug(`→ ${item.name}(${previewJson(item.input)})`, verbose);
+        }
+        else if (verbose && item.type === 'tool_result') {
+            const preview = Array.isArray(item.content)
+                ? item.content
+                    .filter((c) => c?.type === 'text')
+                    .map((c) => c.text ?? '')
+                    .join(' ')
+                : String(item.content ?? '');
+            const flag = item.is_error ? '✗' : '←';
+            logDebug(`${flag} ${truncate(preview, 200)}`, verbose);
+        }
     }
     return text;
 }
+function previewJson(value, max = 200) {
+    try {
+        return truncate(JSON.stringify(value), max);
+    }
+    catch {
+        return truncate(String(value), max);
+    }
+}
+function truncate(text, max) {
+    if (text.length <= max) {
+        return text;
+    }
+    return `${text.slice(0, max - 1)}…`;
+}
 /**
  * Try to parse a JSON result from agent response text.
- * Looks for ```json code blocks first, then falls back to raw JSON parsing.
- * Returns the parsed object or null on failure.
+ * Tries a custom fenceTag (e.g. ```screen_flow) first when provided, then
+ * ```json, then falls back to raw JSON parsing. Returns the parsed object or
+ * null on failure.
  */
-export function tryParseJsonFromResponse(responseText) {
+export function tryParseJsonFromResponse(responseText, fenceTag = 'json') {
     try {
+        if (fenceTag !== 'json') {
+            const taggedMatch = responseText.match(new RegExp(`\`\`\`${escapeRegExp(fenceTag)}\\s*\\n([\\s\\S]*?)\\n\\s*\`\`\``));
+            if (taggedMatch) {
+                return JSON.parse(taggedMatch[1]);
+            }
+        }
         const jsonBlockMatch = responseText.match(/```json\s*\n([\s\S]*?)\n\s*```/);
         return jsonBlockMatch
             ? JSON.parse(jsonBlockMatch[1])
@@ -55,9 +94,11 @@ export function tryParseJsonFromResponse(responseText) {
 /**
  * Extract a specific keyed result from agent response.
  * e.g., tryExtractResult(text, 'review_result') extracts the review_result key.
+ * The key is also tried as the fenced code-block tag so phases whose output
+ * contract uses a custom fence (e.g. ```screen_flow) parse correctly.
  */
 export function tryExtractResult(responseText, key) {
-    const parsed = tryParseJsonFromResponse(responseText);
+    const parsed = tryParseJsonFromResponse(responseText, key);
     if (parsed &&
         typeof parsed === 'object' &&
         key in parsed) {
@@ -66,3 +107,6 @@ export function tryExtractResult(responseText, key) {
     // If top-level has the expected shape, return the whole thing
     return parsed;
 }
+function escapeRegExp(value) {
+    return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+}

package/dist/phases/product-techniques/index.d.ts

@@ -0,0 +1,52 @@
+/**
+ * product-techniques phase: clone the product's repo, ask Claude (via the
+ * `submit_techniques` MCP tool) to write a catalogue of the techniques the
+ * repo uses, and persist the result to product_techniques via the Supabase
+ * SDK.
+ *
+ * Mirrors the screen-flow pattern. Production-grade behaviours layered on
+ * top of the basic generate-and-write loop:
+ *
+ *   - Heartbeat: `last_heartbeat_at` is refreshed on every assistant message
+ *     so the reader can detect stalled / crashed runs (see services/db/
+ *     product-techniques.ts for the lazy reaper).
+ *   - Cancellation-safe writes: markRunning / markSuccess / markFailed only
+ *     touch rows whose status is in {pending, running}. If the user clicked
+ *     Stop and the row is now 'cancelled', the final write no-ops.
+ *   - Tool-based submission: validated server-side via Zod + content checks
+ *     (mcp-server.ts). Falls back to fenced JSON parsing for resilience.
+ */
+import type { SupabaseClient } from '@supabase/supabase-js';
+export interface ProductTechniquesOptions {
+    productId: string;
+    techniquesId: string;
+    guidance?: string;
+    verbose?: boolean;
+}
+export interface ProductTechniquesResult {
+    status: 'success' | 'error' | 'cancelled';
+    message: string;
+    summary?: string;
+}
+export declare function runProductTechniquesPhase(options: ProductTechniquesOptions): Promise<ProductTechniquesResult>;
+/**
+ * Claim the row by flipping `pending` → `running`. Returns true on success
+ * (we won the claim) and false when the row has already moved on (e.g. user
+ * cancelled before the CLI started). Bounded by the status filter so we
+ * can't accidentally resurrect a 'cancelled' row.
+ */
+export declare function markRunning(supabase: SupabaseClient, techniquesId: string): Promise<boolean>;
+/**
+ * Touch the heartbeat. Best-effort — if it fails (network blip, RLS), the
+ * agent loop keeps running; the reader treats this row as stale and marks
+ * it failed on next read, which is the correct behaviour.
+ */
+export declare function heartbeat(supabase: SupabaseClient, techniquesId: string): Promise<void>;
+/**
+ * Write failure status iff the row is still in an active state. Returns
+ * true if the row was actually updated (so the caller knows whether the
+ * agent's verdict made it to the DB). Returns false when the row has
+ * already been cancelled or otherwise resolved by someone else.
+ */
+export declare function markFailed(supabase: SupabaseClient, techniquesId: string, errorMessage: string): Promise<boolean>;
+export declare function markSuccess(supabase: SupabaseClient, techniquesId: string, summary: string, content: string): Promise<boolean>;