Standardise API date range validation

[skyfallwastaken]

Summary of the problem

API date ranges are parsed differently across hours, heartbeats, summary and stats endpoints. Malformed values can raise, be ignored or return inconsistent errors, while reversed ranges are accepted. Project discovery also skips malformed aliases and the aggregate stats error responses are documented with the wrong media type.

Describe your changes

Centralise range validation in the existing DateParsing controller concern while preserving each endpoint's documented formats, aliases and defaults. Malformed, incomplete and reversed supplied ranges now return the same 400 JSON error. Validate project discovery aliases at the controller boundary while preserving their precedence and 30-day defaults. Keep the aggregate stats success response as text while documenting its errors as JSON. Add request and Rswag coverage, then regenerate Swagger.

Screenshots / Media

Not applicable. This is an API-only change.

[greptile-apps]

Greptile Summary

The PR centralizes API date-range parsing and validation while retaining endpoint-specific formats, aliases, and defaults.

• Adds shared malformed, incomplete, and reversed-range validation through DateParsing.
• Applies the shared validation to summary, hours, heartbeat, and stats endpoints.
• Adds request, controller, and generated Swagger coverage for the standardized responses.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
app/controllers/concerns/date_parsing.rb	Introduces the shared range parser, ordering validation, and standardized bad-request response.
app/controllers/api/summary_controller.rb	Routes explicit summary ranges through shared validation and stops processing after rendered errors.
app/controllers/api/v1/authenticated/hours_controller.rb	Replaces independent date conversion with shared range parsing while preserving defaults.
app/controllers/api/v1/my/heartbeats_controller.rb	Validates heartbeat time bounds consistently before querying the authenticated user's records.
app/controllers/api/v1/stats_controller.rb	Applies shared validation across global, user, span, and project-stat date ranges.
swagger/v1/swagger.yaml	Regenerates API documentation for standardized invalid-range responses.

_{Reviews (2): Last reviewed commit: "Validate project discovery date ranges" | Re-trigger Greptile}