feat: separate customer resources into individual sections

[dfcoffin]

Summary

Separates customer resources into individual documentation sections, matching the organization pattern used for energy resources. Previously, all customer resources were grouped under a single "Customer Data" section, making navigation difficult.

Changes

Tag Updates (openapi.yaml)

• Before: Single Customer Resources tag for all customer endpoints
• After: 9 individual tags, one per resource type:
  • Customer
  • CustomerAccount
  • CustomerAgreement
  • ServiceLocation
  • ServiceSupplier
  • EndDevice
  • Meter
  • Statement
  • ProgramDateIdMappings

Path File Updates (18 files)

Updated tag references in all customer resource path files:

• Customer.yaml → uses Customer tag
• Customer_{customerId}.yaml → uses Customer tag
• CustomerAccount.yaml → uses CustomerAccount tag
• CustomerAccount_{customerAccountId}.yaml → uses CustomerAccount tag
• CustomerAgreement.yaml → uses CustomerAgreement tag
• CustomerAgreement_{customerAgreementId}.yaml → uses CustomerAgreement tag
• ServiceLocation.yaml → uses ServiceLocation tag
• ServiceLocation_{serviceLocationId}.yaml → uses ServiceLocation tag
• ServiceSupplier.yaml → uses ServiceSupplier tag
• ServiceSupplier_{serviceSupplierId}.yaml → uses ServiceSupplier tag
• EndDevice.yaml → uses EndDevice tag
• EndDevice_{endDeviceId}.yaml → uses EndDevice tag
• Meter.yaml → uses Meter tag
• Meter_{meterId}.yaml → uses Meter tag
• Statement.yaml → uses Statement tag
• Statement_{statementId}.yaml → uses Statement tag
• ProgramDateIdMappings.yaml → uses ProgramDateIdMappings tag
• ProgramDateIdMappings_{programDateIdMappingsId}.yaml → uses ProgramDateIdMappings tag

x-tagGroups Update

Updated the Customer Data tag group to reference all 9 individual tags instead of the single parent tag.

Impact

Redocly Documentation: Customer resources now appear as 9 separate sections in the sidebar, matching the organization of energy resources (UsagePoint, MeterReading, IntervalBlock, etc.)

Swagger UI: Customer resources now appear as 9 separate sections, improving discoverability and navigation

Developer Experience: Easier to locate specific customer resource endpoints without scrolling through a single large section

Test Plan

• OpenAPI spec validates successfully (npm test)
• Documentation builds without errors (npm run build)
• Redocly preview shows 9 separate customer sections
• Swagger UI preview shows 9 separate customer sections
• All customer endpoints remain functional with correct examples

🤖 Generated with Claude Code