FE-836: Tile + wire up the network graph component into hash-frontend

[alex-e-leon]

🌟 What is the purpose of this PR?

Wires up the NetworkGraph component defined in ds-components to the new atlas service. Handles parsing the atlas wire format, tile geometry, caching + prefetching + introduces a few changes to the filter bar to support the new graph view.

Pre-Merge Checklist 🚀

🚢 Has this modified a publishable library?

This PR:

• does not modify any publishable blocks or libraries, or modifications do not need publishing

📜 Does this require a change to the docs?

The changes in this PR:

• are internal and do not require a docs change

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Ready	Preview	Aug 27, 2026 3:28pm

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
hashdotdesign-tokens	Ignored	Preview	Aug 27, 2026 3:28pm
petrinaut	Skipped		Aug 27, 2026 3:28pm
petrinaut-docs	Skipped		Aug 27, 2026 3:28pm

[cursor]

PR Summary

Medium Risk
New binary wire parsing on untrusted Atlas responses must stay aligned with the server contract; mistakes would break or mis-render the graph, though strict validation and fixture tests mitigate this.

Overview
Introduces a client-side SALTILE / Atlas wire stack under tiled-network-graph/atlas-decode: strict CBOR subset parsing, envelope/slot layout validation, and per-kind decoders for tile, edges, and locate responses (zero-copy typed-array views, request echo checks, trailers/intern tables). Adds manifest/current JSON parsers for session bootstrap and a golden fixture conformance suite against checked-in .saltile bytes.

Adds LocatedEntityPopover, a ds-components/Panda card anchored to selected nodes/edges (types, properties, link endpoints, truncation cues, optional “Go to entity”). Panda include now scans tiled-network-graph/**/* so those styles codegen with the app.

^{Reviewed by Cursor Bugbot for commit a01be13. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Type chips use colliding React keys

Low Severity

Type chips are keyed only by chip.label. An entity with two types that share a title (different versions, or distinct types with the same name) gets duplicate keys, so React can reuse the wrong chip and show a stale colour or icon when the selection updates.

 

^{Reviewed by Cursor Bugbot for commit 0221332. Configure here.}