[Parked pending adopter demand] Repository knowledge-graph visualizer

Context

A generated repository knowledge bundle becomes much easier to review if humans can see its structure: modules, entrypoints, workflows, architecture notes, tests, invariants, risks, and agent instructions.

Google's OKF material points toward graph-style visualization as a useful way to inspect knowledge bundles. For contextweaver, the equivalent value is a lightweight visual/debug surface for agent-visible repository knowledge before it enters context selection.

Related work:

• #736 — Add OKF bundle loader as a context source
• #737 — Export compiled context packs as OKF bundles
• #763 — Ingest generated repository knowledge bundles as context sources
• #764 — Add validation and drift checks for OKF/repository knowledge bundles
• dgenio/weaver-spec#181 — Define an OKF profile for generated repository knowledge bundles

Goal

Prototype a static repository knowledge graph visualizer for OKF-compatible bundles, focused on reviewability and debugging rather than runtime execution.

Scope

Build a minimal visualizer that can show:

• concept nodes grouped by type
• links between concepts from OKF frontmatter and Markdown references
• source file paths for each node
• stale/missing/broken references from validation output when available
• high-level bundle metadata from index.md
• bundle history from log.md when present
• optional filtering by type, tag, or source path

Possible output formats:

• static HTML file
• Mermaid graph export
• JSON graph export for downstream tools

Design constraints

• No network dependency for local visualization.
• Do not require an LLM to build the graph.
• Keep output deterministic so it can be regenerated and reviewed in PRs.
• The visualizer should not imply that all nodes should be loaded into a prompt.

Acceptance criteria

• A sample OKF/repo-knowledge bundle can be converted into a graph representation.
• The graph includes nodes, links, source paths, and concept types.
• A static review artifact can be generated locally.
• Broken or missing references can be surfaced if validation data is available.
• Docs explain how the visualizer helps review generated repo knowledge before context selection.
• Tests cover graph extraction from a small fixture bundle.

Suggested labels / milestone

enhancement, visualization, documentation, interop, OKF

Suggested milestone: OKF interoperability if/when available.

Start with the OKF-compatible bundle shape described in the issue, including index.md, log.md, frontmatter, Markdown references, and available validation output. Compare the related work in #736, #737, #763, and #764, then define a small fixture bundle for graph extraction tests; done means a deterministic local review artifact with nodes, links, source paths, types, and documented usage.