Should Vyasa continue relying on framework inheritance for presentation-heavy surfaces, or should critical surfaces always pin color and font explicitly?
Options: keep inheritance for flexibility, or standardize explicit tokens for headings, nav, sidebars, and controls.
Blocker: explicit pinning reduces surprises but also reduces theme composability.
Should hash navigation become a first-class lifecycle with a single "layout settled" hook instead of repeated retries in scripts.js?
Options: keep retries, or define a post-layout event that Mermaid/D2/HTMX all feed into.
Blocker: Vyasa currently has multiple independent async layout producers, not one central renderer.