Skip to content

feat(planning): measure a vendored Mermaid renderer so the owner can decide its size #5474

Description

@kyle-sexton

Problem

The page shows Mermaid source with "not available in this version" (plugins/planning/surface/index.html:1121). Rendering needs a vendored renderer. The page CSP allows no network source (test_exporters.py:416), so any renderer must be inlined into the page. The owner's decision on #4653 is to "decide Mermaid renderer size"; this issue is not the decision.

Evidence

  • index.html:1121: source shown, not rendered.
  • test_exporters.py:416: CSP with no network source.

Proposed approach

  1. Vendor a Mermaid renderer build in a scratch location (not committed) and measure it: raw bytes, gzip bytes, and the resulting size of index.html if inlined.
  2. Post the numbers on this issue, with the current index.html size for comparison.
  3. Stop. The owner decides whether that size is acceptable. Do not choose a size threshold or build the integration.

Acceptance criteria

  • Measured raw and gzip size of a vendored Mermaid renderer is posted on this issue.
  • The owner records accept or reject; only then is an integration issue filed.

Context

Refs #4653 (owner decision 2026-09-29, Option B). The size call stays with the owner, hence status: needs-decision.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions