Summary
tools/scanner/backend/proto_scanner.go:126 hard-codes Service: "SessionService" for every discovered RPC regardless of which service block the RPC appears in. This produces an incorrect registry if the proto file contains multiple services, and will silently mislabel any future service additions.
Fix
Track the current service name while scanning the proto file — when the parser encounters a service Foo { block, capture "Foo" and use it as the Service field for all RPCs found inside that block.
Impact
- Registry output (
docs/registry/backend-features.json) will be wrong for any non-SessionService RPCs.
- CI registry drift check will not catch the mislabeling.
Source
Deferred from PR #37 review comment: #37 (comment)
Summary
tools/scanner/backend/proto_scanner.go:126hard-codesService: "SessionService"for every discovered RPC regardless of which service block the RPC appears in. This produces an incorrect registry if the proto file contains multiple services, and will silently mislabel any future service additions.Fix
Track the current service name while scanning the proto file — when the parser encounters a
service Foo {block, capture"Foo"and use it as theServicefield for all RPCs found inside that block.Impact
docs/registry/backend-features.json) will be wrong for any non-SessionServiceRPCs.Source
Deferred from PR #37 review comment: #37 (comment)