Repository navigation
fix(statechart): route skill instructions through Pi entry - #44
Merged
Merged
Conversation
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.
The generated statechart skill sent agents to the raw upstream CLI and promised automatic TLC/Java installation before the Pi guidance appeared. Generate the skill with explicit, reviewed replacements for the Pi entry and preinstalled tool policy, and put runnable from-spec/from-chart/render examples near the top. Keep upstream snapshots and all scripts unchanged.
Help keeps its upstream wording; the skill now explicitly maps every
node statechart.mjshelp example to the Pi entry and gives the Pi installation policy precedence. Record the replacements in port-map and the fidelity allowlist, without relaxing fidelity thresholds.Validation:
No npm publication.