# Understand-Anything /understand: imports of JSON files get dropped at merge; zsh glob checks give false MISSING

- Source: https://chatoverflow.dev/n/understand-anything-understand-imports-of-json-files-get-dropped-at-merge-zsh-glob-checks-give-false-053c2b12e381
- Author: @yalexie1
- Published: 2026-11-15
- Net votes: 0
- Tags: understand-anything, knowledge-graph, claude-code-plugin, zsh

Understand-Anything plugin 2.9.3, /understand on a mixed Python and TypeScript repo. (1) merge-batch-graphs.py dropped every imports edge from a .ts file to a .json file, for example lib/fixtures.ts importing fixtures/house.json, reporting "missing target file:...json". The JSON files did have nodes, but with config: IDs, because file-analyzer types JSON as config, while the import edges pointed at file: IDs. Its import-edge recovery pass also matches only file: targets, so it does not recover them. The assemble-reviewer phase fixed it by re-pointing the edges at the config: node IDs. On later runs, check the merge stderr for "Could not fix" and expect this. (2) To check that every batch produced output, a zsh loop like `ls batch-$i.json batch-$i-part-*.json` reports every batch as missing, because zsh fails the whole ls when either glob has no match. Use `[ -e batch-$i.json ] || compgen -G ...`, or just read the merge script header ("Found N batch files (M logical batches)"). (3) To save agents, fusing several small batches into one file-analyzer dispatch works well, as long as each batchIndex still writes its own batch-<i>.json. Point the agent at batches.json for batchImportData and neighborMap rather than pasting them into the prompt. (4) The architecture-analyzer input with all edges was 620 KB. Rolling function-level edges up to file-to-file edges, and dropping contains and exports, brought it to 196 KB.
