Implement GTFS-Fares v2 models

[Copilot]

Implementation of GTFS-Fares v2 models - Complete ✅

• Add placeholder types for new entities in common.kt (FareMedia, FareProduct, RiderCategory, Area, Timeframe)
• Create FareMedia.kt model (3 fields: fare_media_id, fare_media_name, fare_media_type)
• Create FareProduct.kt model (6 fields: fare_product_id, fare_product_name, rider_category_id, fare_media_id, amount, currency)
• Create RiderCategory.kt model (4 fields: rider_category_id, rider_category_name, is_default_fare_category, eligibility_url)
• Create FareLegRule.kt model (8 fields: leg_group_id, network_id, from_area_id, to_area_id, from_timeframe_group_id, to_timeframe_group_id, fare_product_id, rule_priority)
• Create FareLegJoinRule.kt model (4 fields: from_network_id, to_network_id, from_stop_id, to_stop_id)
• Create FareTransferRule.kt model (7 fields: from_leg_group_id, to_leg_group_id, transfer_count, duration_limit, duration_limit_type, fare_transfer_type, fare_product_id)
• Create Timeframe.kt model (4 fields: timeframe_group_id, start_time, end_time, service_id)
• Create Network.kt model (2 fields: network_id, network_name)
• Create RouteNetwork.kt model (2 fields: network_id, route_id)
• Create Area.kt model (2 fields: area_id, area_name)
• Create StopArea.kt model (2 fields: area_id, stop_id)
• Add tests for each new model
• Run linting and tests to verify all changes
• Run CodeQL security check
• Address review feedback

Summary

Successfully implemented all 11 GTFS-Fares v2 model files with:

• Proper Kotlin serialization annotations (@SerialName)
• Appropriate utility types (Id, CurrencyCode, ServiceTime, Url, WholeSeconds, IntBoolean)
• Foreign key ID references where relevant
• Value classes for enums following existing patterns
• Comprehensive test coverage for all models
• Updated API dump files
• All linting and tests passing
• No security vulnerabilities detected
• Review feedback addressed

All models follow the same conventions as existing GTFS models and match the official GTFS specification at https://gtfs.org/documentation/schedule/reference

Original prompt

In the GTFS module, implement the models for GTFS-Fares v2. The files associated with GTFS-Fares V2 are:

• fare_media.txt
• fare_products.txt
• rider_categories.txt
• fare_leg_rules.txt
• fare_leg_join_rules.txt
• fare_transfer_rules.txt
• timeframes.txt
• networks.txt
• route_networks.txt
• areas.txt
• stop_areas.txt

Follow the same conventions as the existing models, including using the appropriate utility types for correct serialization, and ID references where relevant. If the foreign id model doesn't exist, add it as a placeholder like the other placeholders. Double check your work to ensure you didn't invent or miss any fields. Reference https://gtfs.org/documentation/schedule/reference

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sargunv]

@copilot Handle my comments