Type each query in the digest (image vs class) so counts can't be misread

[Robbie1977]

Applies the query-type spec at the stage where it bites — the term-info digest the model reads to interpret counts and pick a query. (The planner step schema has no query_type field, so the planner never names the query; the digest is where selection/interpretation actually happens.)

What changed

Every query line in the digest now ends with a compact typing tag and the header states the rule:

- Images of neurons with some part in medulla: not pre-counted — run this query to get its count of images of neurons [ImagesNeurons — individual images; count = images of neurons; use for how many/which images of neurons have a part in a region]
- Parts of medulla: 28 subparts [PartsOf — ontology classes; thumbnails are examples; count = subparts; use for parts/sub-regions/subdivisions of the term]
- Neurons with some part in medulla: 471 neuron types [NeuronsPartHere — ontology classes; thumbnails are examples; count = neuron types; use for which/how many neuron types have a part in a region]

Header rule: "individual images" ⇒ the count is IMAGES; "ontology classes" ⇒ the count is types/subparts/subclasses and any thumbnail is just one example — never report a class count as an image count; answer an "images" question only from an individual-image query.

This is the root-cause fix for the "28 images" answer: PartsOf's concrete 28 is now explicitly typed as subparts, and the image query (ImagesNeurons, uncounted) is typed as individual images — so the model can't grab the class number and call it images.

Files

• lib/queryTypes.mjs — per-query_type use phrases + queryTypeTag() (kind phrase + count meaning + use).
• lib/termInfoDigest.mjs — render the tag per line; header explains image-vs-class.

Tests / lint

queryTypes 6, termInfoDigest 11 (incl. an image-vs-class-on-same-term typing check); whole offline unit suite green; next lint clean.

After merge

Tag v3.3.3. Pairs with the authoritative/deterministic count injector already in v3.3.2 — that runs the right query; this stops any competing digest number from being misread.