render

# Render Dispatcher Central entry point + menu for the canvas/state render fleet. Routes intent to specialists or surfaces what's available. Cross-cutting views are research-gated and NOT emitted by default. Completes the v0.40.0-announced render fleet foundation. ## When to use - "Show me the OST" / "render the diamond state" / "visualize the cycles" → dispatcher recommends + routes to the specialist (recommend, do NOT auto-invoke). - "Visualize how opportunity X became cycle Y" → cross-cutting traceability intent. Dispatcher surfaces that the view is research-gated; does not emit a default rendering. - Discovery: "what renderable views does Mycelium have?" → dispatcher lists specialists + their states. ## When NOT to use - If the user names a specialist directly (`/mycelium:diamond-render`, `/mycelium:ost-render`, `/mycelium:cycle-render`), the specialist is the one-hop path. Do NOT re-route through the dispatcher. - For cross-cutting views that already have dedicated skills (e.g., `/mycelium:framework-health` is its own audit; not a render specialist). ## Identifier exposure **Declared**: MIXED ### Scope (per-canvas table — REQUIRED for MIXED) | Canvas | Exposure | Identifier-bearing fields | Activated when | |---|---|---|---| | `.claude/canvas/opportunities.yml` | YES | `evidence_sources`, `notes` | `--view traceability` (deferred), `--view ost-summary` | | `.claude/canvas/cycle-history.yml` | YES | `learnings.process` prose, `related_corrections` | `--view trace...