substrate-ai 0.19.9 → 0.19.10

package/dist/cli/index.js

@@ -4,7 +4,7 @@ import { createLogger } from "../logger-KeHncl-f.js";
 import { createEventBus } from "../helpers-CElYrONe.js";
 import { AdapterRegistry, BudgetConfigSchema, CURRENT_CONFIG_FORMAT_VERSION, CURRENT_TASK_GRAPH_VERSION, ConfigError, CostTrackerConfigSchema, DEFAULT_CONFIG, DoltClient, DoltNotInstalled, GlobalSettingsSchema, IngestionServer, MonitorDatabaseImpl, OPERATIONAL_FINDING, PartialGlobalSettingsSchema, PartialProviderConfigSchema, ProvidersSchema, RoutingRecommender, STORY_METRICS, TelemetryConfigSchema, addTokenUsage, aggregateTokenUsageForRun, checkDoltInstalled, compareRunMetrics, createAmendmentRun, createConfigSystem, createDecision, createDoltClient, createPipelineRun, getActiveDecisions, getAllCostEntriesFiltered, getBaselineRunMetrics, getDecisionsByCategory, getDecisionsByPhaseForRun, getLatestCompletedRun, getLatestRun, getPipelineRunById, getPlanningCostTotal, getRetryableEscalations, getRunMetrics, getSessionCostSummary, getSessionCostSummaryFiltered, getStoryMetricsForRun, getTokenUsageSummary, incrementRunRestarts, initSchema, initializeDolt, listRunMetrics, loadParentRunDecisions, supersedeDecision, tagRunAsBaseline, updatePipelineRun } from "../dist-adzGUKPc.js";
 import "../adapter-registry-DXLMTmfD.js";
-import { AdapterTelemetryPersistence, AppError, DoltRepoMapMetaRepository, DoltSymbolRepository, ERR_REPO_MAP_STORAGE_WRITE, EpicIngester, GitClient, GrammarLoader, RepoMapInjector, RepoMapModule, RepoMapQueryEngine, RepoMapStorage, SymbolParser, createContextCompiler, createDispatcher, createEventEmitter, createImplementationOrchestrator, createPackLoader, createPhaseOrchestrator, createStopAfterGate, createTelemetryAdvisor, formatPhaseCompletionSummary, getFactoryRunSummaries, getScenarioResultsForRun, getTwinRunsForRun, listGraphRuns, registerExportCommand, registerFactoryCommand, registerRunCommand, registerScenariosCommand, resolveStoryKeys, runAnalysisPhase, runPlanningPhase, runSolutioningPhase, validateStopAfterFromConflict } from "../run-Dg_BEJB6.js";
+import { AdapterTelemetryPersistence, AppError, DoltRepoMapMetaRepository, DoltSymbolRepository, ERR_REPO_MAP_STORAGE_WRITE, EpicIngester, GitClient, GrammarLoader, RepoMapInjector, RepoMapModule, RepoMapQueryEngine, RepoMapStorage, SymbolParser, createContextCompiler, createDispatcher, createEventEmitter, createImplementationOrchestrator, createPackLoader, createPhaseOrchestrator, createStopAfterGate, createTelemetryAdvisor, formatPhaseCompletionSummary, getFactoryRunSummaries, getScenarioResultsForRun, getTwinRunsForRun, listGraphRuns, registerExportCommand, registerFactoryCommand, registerRunCommand, registerScenariosCommand, resolveStoryKeys, runAnalysisPhase, runPlanningPhase, runSolutioningPhase, validateStopAfterFromConflict } from "../run-NJQHRIYt.js";
 import "../errors-CZdr5Wqb.js";
 import "../routing-CcBOCuC9.js";
 import "../decisions-C0pz9Clx.js";
@@ -4547,7 +4547,7 @@ async function runSupervisorAction(options, deps = {}) {
 								await initSchema(expAdapter);
 								const { runRunAction: runPipeline } = await import(
 									/* @vite-ignore */
-									"../run-0y5KOffG.js"
+									"../run-CAMKyu0F.js"
 );
 								const runStoryFn = async (opts) => {
 									const exitCode = await runPipeline({

package/dist/index.d.ts

@@ -94,6 +94,8 @@ interface PipelineStartEvent {
   stories: string[];
   /** Maximum parallel conflict groups */
   concurrency: number;
+  /** Execution engine: 'linear' or 'graph' */
+  engine?: string;
 }
 /**
  * Emitted as the last event when the pipeline finishes.

package/dist/{run-0y5KOffG.js → run-CAMKyu0F.js}

@@ -2,7 +2,7 @@ import "./health-DJgGZhW-.js";
 import "./logger-KeHncl-f.js";
 import "./helpers-CElYrONe.js";
 import "./dist-adzGUKPc.js";
-import { normalizeGraphSummaryToStatus, registerRunCommand, runRunAction } from "./run-Dg_BEJB6.js";
+import { normalizeGraphSummaryToStatus, registerRunCommand, runRunAction } from "./run-NJQHRIYt.js";
 import "./routing-CcBOCuC9.js";
 import "./decisions-C0pz9Clx.js";
 

package/dist/{run-Dg_BEJB6.js → run-NJQHRIYt.js}

@@ -5284,6 +5284,15 @@ async function runCreateStory(deps, params) {
 	const implementationDecisions = await getImplementationDecisions(deps);
 	const epicShardContent = getEpicShard(implementationDecisions, epicId, deps.projectRoot, storyKey);
 	const prevDevNotesContent = getPrevDevNotes(implementationDecisions, epicId);
+	let storyDefinitionContent = "";
+	try {
+		const storyDecisions = await getDecisionsByPhase(deps.db, "solutioning");
+		const storyDef = storyDecisions.find((d) => d.category === "stories" && d.key === storyKey);
+		if (storyDef) {
+			storyDefinitionContent = storyDef.value;
+			logger$18.debug({ storyKey }, "Injected story definition from solutioning decisions");
+		}
+	} catch {}
 	const archConstraintsContent = await getArchConstraints$3(deps);
 	const storyTemplateContent = await getStoryTemplate(deps);
 	const { prompt, tokenCount, truncated } = assemblePrompt(template, [
@@ -5297,6 +5306,11 @@ async function runCreateStory(deps, params) {
 			content: epicShardContent,
 			priority: "required"
 		},
+		{
+			name: "story_definition",
+			content: storyDefinitionContent,
+			priority: "required"
+		},
 		{
 			name: "arch_constraints",
 			content: archConstraintsContent,
@@ -41620,4 +41634,4 @@ function registerRunCommand(program, _version = "0.0.0", projectRoot = process.c
 
 //#endregion
 export { AdapterTelemetryPersistence, AppError, DoltRepoMapMetaRepository, DoltSymbolRepository, ERR_REPO_MAP_STORAGE_WRITE, EpicIngester, GitClient, GrammarLoader, RepoMapInjector, RepoMapModule, RepoMapQueryEngine, RepoMapStorage, SymbolParser, createContextCompiler, createDispatcher, createEventEmitter, createImplementationOrchestrator, createPackLoader, createPhaseOrchestrator, createStopAfterGate, createTelemetryAdvisor, formatPhaseCompletionSummary, getFactoryRunSummaries, getScenarioResultsForRun, getTwinRunsForRun, listGraphRuns, normalizeGraphSummaryToStatus, registerExportCommand, registerFactoryCommand, registerRunCommand, registerScenariosCommand, resolveStoryKeys, runAnalysisPhase, runPlanningPhase, runRunAction, runSolutioningPhase, validateStopAfterFromConflict };
-//# sourceMappingURL=run-Dg_BEJB6.js.map
+//# sourceMappingURL=run-NJQHRIYt.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "substrate-ai",
-  "version": "0.19.9",
+  "version": "0.19.10",
   "description": "Substrate — multi-agent orchestration daemon for AI coding agents",
   "type": "module",
   "license": "MIT",

package/packs/bmad/prompts/create-story.md

@@ -16,13 +16,22 @@
 
 ---
 
+### Story Definition (from Solutioning Phase)
+{{story_definition}}
+
+---
+
 ## Mission
 
 Using the context above, write a complete, implementation-ready story file for story **{{story_key}}**.
 
+**CRITICAL**: The Story Definition above is the authoritative specification for this story's scope.
+Use the title, description, and acceptance criteria from the Story Definition — do NOT substitute
+a different story from the epic scope. The story key, title, and core scope are non-negotiable.
+
 ## Instructions
 
-1. **Parse the epic scope** to understand what this epic is building and where this story fits
+1. **Use the Story Definition as your primary input** — it specifies exactly what this story builds. The epic scope provides surrounding context only.
 2. **Apply architecture constraints** — every constraint listed above is mandatory (file paths, import style, test framework, etc.)
 3. **Use previous dev notes** as guardrails — don't repeat mistakes, build on patterns that worked
 4. **Fill out the story template** with:

package/packs/bmad/prompts/readiness-check.md

@@ -88,7 +88,21 @@ For EVERY story with dependencies on other stories:
 3. Flag invalid references as **blocker** findings
 4. Flag potentially circular dependencies as **major** findings
 
-### Step 7: Final Verdict
+### Step 7: Cross-Epic Story Duplication Check
+
+For EVERY pair of stories from DIFFERENT epics:
+1. Do they implement the same core functionality? (e.g., both create a MatchRunner, both build a tournament CLI, both implement a logging module)
+2. Do they have overlapping acceptance criteria? (same testable condition appears in both)
+3. Does a later epic's story RE-IMPLEMENT what an earlier epic's story already built, rather than extending or depending on it?
+4. Flag duplicate stories as **major** findings with both story keys in affected_items
+5. Flag near-duplicates (>50% AC overlap) as **major** findings
+
+Common duplication patterns:
+- Infrastructure stories (logging, CLI, config) appearing in multiple epics
+- Runner/harness classes duplicated across epics
+- The same data model or service being created by stories in different epics
+
+### Step 8: Final Verdict
 
 Determine your verdict:
 - **NOT_READY**: Any of these conditions are true:
@@ -130,7 +144,7 @@ findings:
 ```
 
 Valid verdict values: READY, NEEDS_WORK, NOT_READY
-Valid category values: fr_coverage, architecture_compliance, story_quality, constraint_adherence, ux_alignment, dependency_validity
+Valid category values: fr_coverage, architecture_compliance, story_quality, constraint_adherence, ux_alignment, dependency_validity, story_duplication
 Valid severity values: blocker, major, minor
 
 If you cannot perform the review:

package/packs/bmad/prompts/story-generation.md

@@ -42,12 +42,19 @@ Break down the requirements and architecture above into **epics and stories**
    - If architecture specifies a project structure, Epic 1 Story 1 should be project scaffolding
    - Database tables, API endpoints, and infrastructure are created in the epic where they are FIRST NEEDED
 
-5. **Size stories appropriately:**
+5. **Eliminate cross-epic duplication (CRITICAL):**
+   - Before finalizing, compare EVERY story against stories in OTHER epics
+   - If two stories from different epics implement the same core functionality (e.g., both create a MatchRunner, both build a tournament CLI), consolidate into ONE story in the earliest epic that needs it
+   - The later epic should DEPEND ON the earlier epic's story, not re-implement it
+   - Common duplication patterns to watch for: logging infrastructure, CLI subcommands, runner/harness classes, configuration modules
+   - A story that "extends" functionality from an earlier epic is OK; a story that "re-implements" the same functionality is NOT
+
+6. **Size stories appropriately:**
    - Each story should be completable by one developer in 1-3 days
    - If a story feels too large, split it into multiple stories within the same epic
    - If an epic has more than 8 stories, consider splitting the epic
 
-6. **Amendment awareness**: If amendment context from a parent run is provided below, generate stories for the NEW scope introduced by the amendment. Do not regenerate stories for unchanged requirements.
+7. **Amendment awareness**: If amendment context from a parent run is provided below, generate stories for the NEW scope introduced by the amendment. Do not regenerate stories for unchanged requirements.
 
 ## Output Contract