For RESTfulAPIService:

1. Path consistency: Read the generated server routing config, Go client URL construction, TS client URL construction, and OpenAPI paths. Verify they all produce the same paths for each RPC:

   • ListResources: /api/v1/resources
   • GetResource: /api/v1/resources/{resource_id}
   • GetNestedResource: /api/v1/orgs/{org_id}/teams/{team_id}/resources/{resource_id}
   • CreateResource: /api/v1/resources
   • UpdateResource: /api/v1/resources/{resource_id}
   • PatchResource: /api/v1/resources/{resource_id}
   • DeleteResource: /api/v1/resources/{resource_id}
   • SearchResources: /api/v1/resources/search (new from plan 01)

2. HTTP method consistency: Verify all 4 generators agree on the HTTP method for each RPC.

3. Query parameter consistency: For ListResources and SearchResources, verify:

   • Same parameter names across all 4 generators
   • Same types (especially int64/uint64 as string in OpenAPI)
   • Same required/optional semantics

4. Request body schema consistency: For CreateResource, UpdateResource, PatchResource:

   • Verify field names match (protojson camelCase)
   • Verify field types match (especially maps, nested messages, enums)
   • Verify the Go client sends what the server expects
   • Verify the TS client sends what the server expects
   • Verify OpenAPI documents what the server accepts

5. Response body schema consistency: For all RPCs returning Resource:

   • Verify field names match across all 4 generators
   • Verify int64 fields (created_at, updated_at) are handled correctly (string in JSON per protojson)
   • Verify enum fields (status) are string names
   • Verify nested message fields (metadata_detail) are present

6. Error response consistency:

   • Verify all generators agree on 400 = ValidationError, default = Error
   • Verify error schema fields match

7. Header consistency:

   • Verify service header X-API-Key appears in all generators
   • Verify method header X-Request-ID appears for CreateResource in all generators

For BackwardCompatService:

• Verify default paths are consistent across all 4 generators
• Verify default HTTP method (POST) is used

Unwrap verification (from unwrap.proto):

• Verify all unwrap variants produce consistent schemas/types across all 4 generators
• Map-value unwrap: server JSON {"bars": {"AAPL": [...]}} matches client expectations
• Root repeated unwrap: server JSON [{...}, {...}] matches client expectations
• Root map unwrap: server JSON {"key": {...}} matches client expectations
• Combined unwrap: server JSON {"AAPL": [...]} matches client expectations

If any inconsistency is found during comparison, fix it immediately. This may involve modifying generator source files (generator.go, types.go) in any of the 4 generators. After fixing, update the affected golden files and re-run tests. All tests still pass: ./scripts/run_tests.sh. If any fixes were made, golden files were updated. The cross-generator comparison confirms semantic consistency for all RPCs in the shared test proto. make lint-fix produces no changes. Cross-generator semantic comparison complete. All 4 generators produce semantically consistent output for every RPC in the shared exhaustive test proto:

• Paths match across server, Go client, TS client, OpenAPI
• HTTP methods match
• Query/path parameters match (names, types, required/optional)
• Request/response body schemas match (field names, types, protojson conventions)
• Error responses match (ValidationError, Error)
• Headers match
• Unwrap variants are consistent across all 4 generators
• Backward compat defaults are consistent
• Any inconsistencies found are fixed (not deferred)