feat(governance): add typed label and governance outputs - #3402
Draft
SamMorrowDrums wants to merge 1 commit into
Draft
SamMorrowDrums wants to merge 1 commit into
SamMorrowDrums wants to merge 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
SamMorrowDrums
added this pull request to stack #3385
October 2, 2026 21:35
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
Add concrete output types and schemas for all label tools, repository rulesets, and custom properties. Structured content is exposed only to the supported modern protocol; legacy text output, error behavior, level/method routing, scopes, and IFC metadata remain compatible.
Why
Continue the sequential typed-output stack on top of the Projects layer. Builds on #3401; no issue linked.
What changed
get_labelregistrations,list_label,label_write,repository_ruleset_read,create_repository_ruleset, and custom properties read/write.MCP impact
Prompts tested (tool changes only)
Security / limits
Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint(invoked asscript/lint; passed with 0 issues)../script/test(invoked asscript/test; passed, includinggo test -race ./...).Validation in order:
UPDATE_TOOLSNAPS=true go test ./...— passed;script/lint— passed (0 issues);script/test— passed;script/generate-docs— passed and updated generated docs;git diff --check— passed.Docs