test(workflow-executor): PRD-552 legacy and deterministic Load Related Record coexist#1688
Open
Scra3 wants to merge 3 commits into
Conversation
… coexist (PRD-552) Explicit backward-compatibility regression: within one run, the same executor takes the AI path for a legacy prompt-only step (no preRecordedArgs) and the deterministic no-AI path for a step with source + relation pinned. fixes PRD-552 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
…ed' into feature/prd-552-backward-compat-load-related
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
1 participant
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.
Context
Joint backward-compat guard for the Deterministic Load Related Record epic (PRD-471), stacked on #1687 (PRD-551).
What
An explicit regression test: within one run the same executor takes the AI path for a legacy prompt-only step (no
preRecordedArgs) and the deterministic no-AI path for a step with source + relation pinned. Coexistence was already implied by the green suite; this names it as a guard.Where the rest of the coexistence is covered
forest:preRecordedArgs→ forwarded unchanged (parser test).guidancepanel (gating).Tests
82/82 in the load-related suite (run locally).
fixes PRD-552
🤖 Generated with Claude Code
Note
Add coexistence tests for legacy and deterministic
LoadRelatedRecordStepExecutorpathsAdds a Jest describe block in load-related-record-step-executor.test.ts verifying that both execution modes work correctly within the same run.
bindTools.preRecordedArgs(selectedRecordStepId,relationName) fetch related records directly via the agent port using prior step results, return success, and skipbindTools.Macroscope summarized a6f608d.