Dependency-graph features: export as json/yaml/toml and render an interactive dep tree #296

Source: Google Chat alex-alex-me — msgs #108 (Aug 8 14:56), #156 (Aug 11 00:15), #246 (Aug 24 01:24), #184 (Aug 14 18:02)
Audit: chat-bridge sweep 2026-08-28. Parent ORESoftware/my-ai#22

Ask

zed-pkg should be able to produce dependency graphs given repos and GitHub orgs, and users should be able to download the graph as json, yaml, toml etc. Then build an outstanding visualization of the dep tree and dep graph between zed packages for a given package — navigable, clickable, with buttons that run common queries.

claritas-viz can serve HTML for us, but it is better to run it ourselves in our own mash Rust web server. Make the visualization genuinely nice, dynamic and interactive. Model users, orgs, projects, packages, licensing, package versions, pre-releases, uploads and downloads in Postgres and expose them through the HTML/htmx. It belongs on the org, project and package pages, so shared components are the right shape — Leptos islands are welcome.

Also: trace every zed-pkg package across all repos in all orgs, audit and harden their implementation with total context before changing any one repo, keep them current with the latest zed API, and test them through their respective *-test orgs. Identify 1-5 repos that would benefit from becoming a zed package.

Done when

• zed graph emits json/yaml/toml for a package, a repo or a whole org.
• The interactive graph renders from mash/htmx with Leptos islands, no React.
• A cross-org audit of .zpkg.toml files is published, with the 1-5 new-candidate repos named.

Conflicts: resolve semantically per ORESoftware/my-ai AGENTS.md, never pick a side.