Fix: resolve relative concept links in the graph viewer detail panel

[ryanb93]

Problem

In the bundled OKF graph viewer (viz.html), clicking a concept link inside the detail panel opened the raw .md file instead of selecting that concept in the graph — but only for relative links.

rewriteInternalLinks only recognised absolute links (/tables/users.md). Relative links — users.md, ../references/metrics/dau.md — fell through to the external-link branch. This is an asymmetry with the rest of the toolchain:

• the Python edge extractor _extract_links (generator.py) already resolves relative links, so the graph edges render correctly;
• the OKF spec's own examples and the reference agent's output use relative links.

So a bundle authored with relative links draws the right graph, but its in-panel links don't navigate.

Fix

Resolve each markdown-link href to a concept id relative to the current concept's directory — handling ., .., and #anchor — then select the node if it exists (falling back to external-link behaviour otherwise). This brings the click handler to parity with the already-supported/edge-extracted relative links. Absolute links keep working unchanged.

Testing

viz.js is a browser-only static asset and the repo has no JS test harness, so no automated JS test is added (introducing one for a ~30-line fix seemed disproportionate — happy to add one if maintainers prefer). The relative-link contract is already covered on the Python side by test_viewer.py::test_cross_links_become_edges, which uses relative links. Manually verified that absolute, sibling, ..-traversing, and #anchor links all resolve to the correct concept id, and that unresolved links still render as external.

🤖 Generated with Claude Code

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.