ores.cpp.history-provider-registrar

Two templates forming the per-entity history-provider registrar pair. The header declares register_<entity>_history_provider(). The implementation builds the entity's history provider and registers it into the ores::history::service::dispatch_registry the caller passes in. The provider reads the entity's version history through its service and renders each version through its field mapper. The per-component service registrar delegates to each per-entity registrar, so a compile failure in one entity's provider cannot block registration of the rest. Consumed by the default (no --address) generation set for every domain_entity.

Projects the entity model onto its generic-history registration surface: the entity_type key the generic history.v1.get subject dispatches on, the service read that produces the version history, and the field mapper that renders each version for display. It consumes the same domain_entity model and the same presentation::render_<entity>_fields mapper the ores.cpp.presentation facet emits. It derives its entity_type key identically to the entity_name the notify_trigger SQL facet stamps on each row change (product_component_entity_singular), so the two sides of the pipeline can never drift out of sync.

Replaces the pattern of hand-wiring one ~10-line register_history_provider() lambda per entity directly into each component's registrar.cpp. That hand-maintained surface has already drifted: refdata's registrar registers only 53 of its 64 mapper-bearing entities. A small per-component aggregator (not generated; it mirrors ores::refdata::core::messaging::registrar) calls each generated per-entity function, the same way it already calls the CRUD register_<entity>_handlers() functions. refdata's registrar keeps its current 53 calls, so the registered key set is unchanged. The 11 mapper-bearing entities with no provider today stay unregistered, with identical runtime behaviour, until their own wiring work adds them.

• ores.cpp.presentation — the mapper this facet's provider renders through.
• Entity-composed registrars — the architecture meta-pattern this facet is the history instance of.
• ores.cpp.nats-sub-registrar — the request/response registrar pair this facet sits alongside in .core messaging.
• Codegen template library — the groups overview.