Load shipped categories before binding, panic on an index that misses a read, and name the index entry and unloaded category plainly

docs/decisions.md

@@ -116,17 +116,17 @@ still lives in `data/` as JSON; `--data-path` layers over it.
 
 `todo.md` item 77 revises it: a library imports the shipped data as Go modules.
 
-## The shipped set alone loads a category on the first call reaching it; beside a `--data-path` it loads whole
+## The shipped set alone loads a category on the first call reaching it; beside a `--data-path` every category loads in `New`
 
 2026-10-03, approved by the maintainer as the restructure of `todo.md` item 76. Goal 12: a
 `New` pays nothing for the categories a run never reaches, which matters once the shipped
 set grows to hundreds of MB. A category loads with every category it references and its
 whole table family, and is bound as a whole load binds, so it renders as it would from
 `New`. `List` reads `shippedindex.go`, generated from `data/` with `REPIN=1`, and
-`TestShippedIndexIsCurrent` fails while it is stale. CI loads the whole shipped set, so a
-shipped category never fails at first reach. Goal 6: beside a `--data-path` or a
+`TestShippedIndexIsCurrent` fails while it is stale. CI loads the whole shipped set, and
+loads each shipped category alone into a fresh `New`, so none fails at first reach. Goal 6: beside a `--data-path` or a
 `WithDataFS`, every category loads in `New`, so each mistake in a source the user wrote is
-`New`'s error. Valid while the shipped set is proven whole in CI.
+`New`'s error. Valid while CI proves the shipped set whole and each category alone.
 
 ## A bare reference draws each time; a reference path is held