Repository navigation
refactor(registry): share source fields for generated entries - #115
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review endedClawSweeper stopped reviewing this revision because the pull request closed. |
vincentkoc
marked this pull request as ready for review
November 20, 2026 12:24
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: refactor(registry): share source fields for generated entries This is item 1/1 in the current shard. Shard 0/1. This temporary status tracks the active review worker. The completed review will appear in the durable ClawSweeper review comment. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
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
Generated native tools and commands carry the same app, plugin, exported name, original name and description. One type and one runtime check now define those fields. Tools still require their kind and object schema, and both command lists still require an argument hint. Output styles reuse the bundle style type.
Verification
A mixed registry fixture preserves valid tools and both kinds of commands while filtering invalid apps, schemas, source fields and argument hints. Package declaration validation covers the shared types. The full local build, test suite and installed-package consumer check passed.