gh issue close 91 --comment "$(cat <<'COMMENT'
This is already supported via the existing `(sebuf.http.unwrap) = true` annotation on repeated fields. No new annotation is needed.
 
**Usage:**
\`\`\`proto
message ListItemsResponse {
  repeated Item items = 1 [(sebuf.http.unwrap) = true];
}
\`\`\`
 
**Result:** The response serializes as `[{...}, {...}]` instead of `{"items": [{...}, {...}]}`.
 
The implementation generates custom `MarshalJSON`/`UnmarshalJSON` methods on the response message that marshal/unmarshal the repeated field directly at the root level.
 
**Test coverage:**
- Proto fixture: `internal/httpgen/testdata/proto/unwrap.proto` (`RootRepeatedResponse` message)
- Implementation: `internal/httpgen/unwrap.go` (`generateRootRepeatedUnwrapMarshalJSON`, `generateRootRepeatedUnwrapUnmarshalJSON`)
- Tests: `internal/httpgen/unwrap_test.go` (`TestRootUnwrapFileGeneration`)
 
**Documentation:** See the "Root-level unwrap" section in CLAUDE.md for full examples including root repeated, root map, and combined unwrap patterns.
 
This works across all generators: go-http (server marshal/unmarshal), go-client (same marshaling), and openapiv3 (array schema at root level).
COMMENT
)"

gh issue view 94 --json state,comments

gh issue close 94 --comment "$(cat <<'COMMENT'
Closing -- proto3's built-in \`json_name\` field option provides per-field JSON name override:
 
\`\`\`proto
message User {
  string first_name = 1 [json_name = "firstName"];  // camelCase in JSON
  string last_name = 2 [json_name = "LastName"];     // PascalCase in JSON
  string user_id = 3;                                // defaults to "userId" per proto3 spec
}
\`\`\`
 
For global snake_case output, use \`protojson.MarshalOptions{UseProtoNames: true}\` when marshaling.
 
See https://protobuf.dev/programming-guides/proto3/#json for the proto3 JSON mapping specification.
 
No sebuf-specific annotation is needed -- this is handled entirely by proto3 and protojson.
COMMENT
)"

# Verify issue is closed
gh issue view 94 --json state | jq '.state'
# Should output: "CLOSED"
 
# Verify closing comment exists and mentions json_name
gh issue view 94 --json comments | jq '.comments[0].body' | grep -q "json_name"