Task: Consolidate the five ores.cpp.nats-* facets into one facet with five archetypes

Merge the five ores.cpp.nats-* facet nodes in the physical-space graph (projects/ores.codegen/library/templates/ores.cpp.nats-*.org) into one ores.cpp.nats facet with five archetypes (handler, sub-registrar, eventing, event-registrar, event-cache), updating every template/doc reference to the old five facet IDs.

• One ores.cpp.nats facet node exists with five archetypes; the five old facet .org files are retired; every reference to the old facet IDs (entity_meta_model_cpp_nats.org, applied_masd.org's facet catalogue table, any others found via grep) is updated to the new facet/archetype addresses; zero-diff regeneration verified against at least one entity using NATS (e.g. book).

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Raised while authoring Codegen entity meta-model — C++ NATS, which documents the five facets together as one conceptual flow (command pipeline: handler + sub-registrar; event pipeline: eventing + event-registrar + event-cache) precisely because the physical-space graph doesn't. All five currently belong to the C++ Technical Space with no intermediate grouping — there is no MASD concept of a "facet group" between technical space and facet; five separate facet nodes is simply five separate facet nodes today.

Manual QA scenarios (scaffolded via compass add test_scenario, run through the QA Validation Runner panel) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.