Support stack categories and facets across package discovery - #45
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
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.
Stack discovery now uses the same category and namespaced facet contract as skills, so search, list, and info consistently describe and filter both package types. Stack IDs, ownership behavior, and skill-only role semantics remain stable. The generated CLI bundle is committed separately from source changes.
Validation: 811 CLI tests passed; frozen-lockfile build and package checks passed. The final source and generated bundle were independently reviewed and verified on the admin Mac. The companion registry change supplies classification for all 51 stacks.
Scope, red/green proof, review dispositions, and known limits are recorded in docs/swe-compliance/2026-09-06-stack-catalog-facets.md.