Add CLI, HTTP, shell, and Wt layer generation to codegen

Add codegen profiles for the four presentation/access layers that currently have no codegen support at all:

• CLI commands (ores.cli)
• HTTP REST endpoints (ores.http.server)
• Shell REPL commands (ores.shell)
• Wt web UI (ores.wt)

Today, every entity commissioned end-to-end (SQL, domain, repository, service, protocol, NATS, Qt) ships without these layers. Per-entity placeholder captures have been filed for each missing layer — but the gap is not per-entity; it is that codegen has no profile for any of these layers at all. Once the profiles exist, every entity gets them automatically on regeneration.

This capture will be split into separate stories (one per layer) with per-component tasks when work begins. Entities known to need coverage include at least: contact_type, purpose_type, business_centre, and the three CRM topology entities (crm_topology_config, crm_driver_pair, crm_enabled_derived_pair).

Every entity commissioned since the codegen migration ships with a gap in its presentation layers. Filing per-entity captures keeps individual entities from being forgotten, but the real fix is building the codegen profiles. Until they exist, every newly-commissioned entity accumulates the same gap, and the per-entity capture list grows unboundedly.

• Entity commissioning process reference — the gap protocol that documents which layers each entity is missing.