Make driver routes descriptor-backed

[shiny-code-bot]

Current Status

State: Waiting. Audit found descriptors document driver capabilities while service.py still hardcodes many driver envelopes and handlers. This is important, but should follow contract and provider seam cleanup.

Next action: Design a small descriptor-dispatch spike with a fake driver and parity tests before moving real routes.

Blocked by: No native issue blocker.
Waiting for: Typed evidence and provider adapter seams to reduce churn.

Acceptance Criteria

• Adding a stub third product driver requires a descriptor and driver module, not edits in multiple unrelated service.py route tables.
• Startup or tests fail closed if a descriptor action lacks a route, envelope, authz action, or handler.
• Driver route envelopes/handlers move into cohesive driver modules.
• Existing Odoo/generic-web/VeriReel routes remain compatible or have explicit retirement steps.
• Docs explain how a new driver declares actions and where code lives.

Target Areas

• control_plane/service.py
• control_plane/drivers/registry.py
• control_plane/contracts/driver_descriptor.py
• product workflow modules and service tests

Finish Line

Driver route metadata, authz, envelopes, and dispatch have one source of truth or tested parity so adding a product driver does not require central service surgery.