fix(scheduler): restore context loading for skill-based runNow entries - #672
Merged
Conversation
The scheduler refactoring accidentally removed the contextFile loading logic from the skill-based runNow path. This restores it so that skill entries with a contextFile set will load context from that file, falling back to loadContext(contextDir) if the file doesn't exist.
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.
Description
Restores the
contextFileloading logic that was accidentally removed during the scheduler refactoring in PR #671. Skill-basedrunNowentries now correctly load context fromentry.contextFile, falling back toloadContext(contextDir)if the file doesn't exist.Type of Change
Testing
scheduler - ScheduleManagertest suite already coversrunNowwith skill entries (which implicitly tests context loading).Coverage
Checklist
npm run lintpasses