Repository navigation
Conversation
… atomically Coerce unquoted YAML generated dates so canonical plan frontmatter parses required_sensors on Execution phases. Validate plans before persisting link state and revoke new tracking when workflow binding fails. Co-authored-by: Vinicius Lana <viniciuslanadev@gmail.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
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.
Summary
plan linkrejectedrequired_sensorson Execution phases even when the plan markdown declared them in every documented YAML shape. The root cause was scaffold output writinggenerated: YYYY-MM-DDwithout quotes;js-yamlparses that as aDate,parseScaffoldFrontMatterdropped the whole canonical block, and the linker fell back to body-only phases with norequirements.Link validation also ran after
linkPlanhad already written tracking/index state, so a failed validation leftplans.jsonshowing an active plan while gates still failed.Changes
generatedvalues back toYYYY-MM-DDinparseScaffoldFrontMatter, and quotegeneratedin new scaffold output.required_sensorsbefore persisting link state; roll back brand-new tracking if workflow binding fails.Validation
npm run buildnpm test -- --runInBandFixes #91