# X_DOC_PACKAGE_GRAPH_STALE

## Means

the dependency graph `docs/architecture/01-package-map.md` draws is not the one the manifests declare

## Typical cause

two shapes, one code: an arrow whose `from` package declares no dependency on its `to`, and a publishable package with no node at all. Eleven arrows described imports no manifest ever made — `schema→core`, `ui→render`, `render→query` and eight more — and `scraping` was absent entirely. The reverse is deliberately unchecked: the graph abridges, `cli` declares 23 and draws 4

## Fix

`bun run package-map-graph --json` — each finding names the arrow, its line and the `package.json` that would have to declare it

[CLI and verify](/error-codes#cli-and-verify)