Registry render orchestration.
Purpose
-------
Expose the public `render_all` orchestration entry point for registry-backed
filesystem artifacts.
Responsibilities
----------------
- Dispatch to each artifact renderer in a deterministic order.
- Apply shared `prefer_local`, `dry_run`, and artifact filtering options.
- Return an aggregate `RenderReport` for CLI and doctor consumers.
Diagnostics
-----------
Domain: OC_CHAT.MAIN
Levels:
L2 - render-all lifecycle events
L3 - artifact selection details
L4 - per-artifact dispatch tracing
Contracts
---------
- `render_all` mutates files only through artifact writers.
- Registry state is read-only during rendering.
Dependencies
------------
- oc_diagnostics (structured debug logging via _dbg)
- oc_chat.registry.api (Registry facade the artifacts are rendered from)
- oc_chat.registry.render._common (RenderReport, RenderResult and the worktree plan rows)
- oc_chat.registry.render.plan_header (plan header artifact writer)
- oc_chat.registry.render.plan_status (plan status artifact writer)