Task: The NATS wire carries oresmd URIs

Make the NATS wire oresmd-native. Tick subjects and the ir_curve_tick payload carry URIs, not ORE-shaped keys. Every subscriber updates.

• Tick subjects are oresmd-native: no ore_key component in the subject.
• The ir_curve_tick payload carries the oresmd URI, point included; series_type, metric, and qualifier fields are gone.
• Every subscriber of marketdata.v1.tick.* and synthetic.v1.* updates.
• Feed controllers resolve series and check collisions on URIs.
• Forward projections stay available at the ORE-format edge (file and CSV export).

(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.)

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.