Repository navigation
test(org-plan): preserve Gestalt skill references and clarify loading - #136
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.
Mobile already accepts
$gestalt:*references in Org Plans. Add regression coverage for Gestalt-only, mixed, and conditional skill declarations, and clarify that advertised skills are available to load rather than automatically loaded.Document declared skills as required preparation while allowing executors to load additional relevant skills on demand without revising the plan. Conditional capabilities still require runtime readiness.
Validation:
npm run format:check,npm run license:check,npm run check,npm test(2,731 passed; 2 skipped),npm run lint,npm run build, andgit diff --checkpassed. No browser behavior changed.