feat(mcp): Phase 12 — initialize scope capabilities - #382
Merged
Conversation
Refs #292 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
무엇
MCP initialize 응답에 parsec 전용 GitHub scope capability metadata를 광고하도록 추가했습니다.
왜
Refs #292. docs/mcp/spec.md의 delegated auth metadata 계약은 클라이언트가 초기화 단계에서 지원 scope를 확인할 수 있어야 한다고 정의합니다.
변경
다음 Phase 힌트
리스크
Low. MCP initialize 응답 metadata 추가이며 기존 CLI surface와 worktree/git 핵심 로직은 변경하지 않았습니다.
롤백
해당 커밋을 revert하면 initialize capabilities가 이전 tools-only 응답으로 돌아갑니다.
Test plan
@erishforG