feat(workflow-executor): use the step title as the AI prompt fallback#1635
Merged
Scra3 merged 1 commit intoJun 8, 2026
Merged
Conversation
1 new issue
|
|
Coverage Impact Unable to calculate total coverage change because base branch coverage was not found. Modified Files with Diff Coverage (2)
🛟 Help
|
The orchestrator sends a `title` on every step (ServerWorkflowStepBase.title) but the mapper dropped it. Carry it into the domain StepDefinition and, in buildContextMessage, fall back to it ONLY when the step has no prompt — the prompt, when present, is the authoritative intent, so the title would just be noise. This rescues steps whose prompt arrives empty (e.g. a load-related step whose prompt is "" while the title says "Load the store"). - add optional `title` to the shared StepDefinition fields - map `task.title` / `condition.title` in step-definition-mapper - buildContextMessage appends `Step title: "<title>"` only when prompt is absent Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Scra3
force-pushed
the
fix/workflow-thread-step-title-ai-context
branch
from
6fe3d3c to
4c1b8e9
Compare
Scra3
changed the title
nbouliol
approved these changes
Jun 8, 2026
Scra3
pushed a commit
that referenced
this pull request
Jun 8, 2026
…RD-433 + title fallback) Rebasing the relation-by-target-collection fusion onto a mapper that gained PRD-426 (technical-name preRecordedArgs), PRD-433 (previousSteps-driven record pool) and the step-title-as-prompt-fallback rule (#1635): - pin pre-recorded relations by technical relationName, matched exactly on field.fieldName (drops the displayName fuzzy matchesRelation) - tests pass loaded records via previousSteps so getAvailableRecordRefs surfaces them, and use select-relation-to-follow / technical names - the step title now reaches the select-relation context only when the prompt is absent (fallback rule), so its test drives an empty prompt Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The orchestrator sends a
titleon every step (ServerWorkflowStepBase.title) but the mapper dropped it. Carry it into the domainStepDefinitionand, inbuildContextMessage, fall back to it only when the step has no prompt.The prompt, when present, is the authoritative intent (surfaced by each executor), so showing the title too would just be noise. The title rescues steps whose prompt arrives empty (e.g. a load-related step whose prompt is
""while the title says"Load the store").Rule
Step title: "<title>"is added to the contextChanges
titleto the sharedStepDefinitionfieldstask.title/condition.titleinstep-definition-mapperbuildContextMessageappends the title only when the prompt is absentbuildContextMessagecases (fallback / prompt-wins / neither)Small, self-contained slice extracted from the load-related work (#1630). Build + lint clean, 952 tests green.
🤖 Generated with Claude Code
Note
Use step title as AI prompt fallback in workflow executor
titlefield to allStepDefinitionvariants in step-definition.ts and propagates it through the task and condition mappers in step-definition-mapper.ts.BaseStepExecutor.buildContextMessagein base-step-executor.ts to append aStep title:line to the system context message when the step has no prompt; the title is omitted when a prompt is present.Macroscope summarized 4c1b8e9.