docs(vocab): 'residue list' collides with the shared glossary's Residue; OND/CNO connection rows proposed for the type-family map #175

The estate's type-research families share a vocabulary + boundary map in nextgen-typing/docs/TYPE-CONNECTIONS.adoc (tracked by nextgen-typing#118). Two coherence items surfaced while sweeping the type-set:

1. "Residue list" collides with the shared glossary. Absolute Zero ships "a residue list of out-of-scope observables: the honest boundary between the proof and the physical metal" (README, OND pillar). TYPE-CONNECTIONS' glossary defines Residue as "information retained after a transformation" (Echo sense) and explicitly fences it from the numerical residual. This is a third meaning: an out-of-scope-observables list. The honesty practice is excellent and worth keeping — but the word will be misread against the glossary. Options: rename here (e.g. exclusion list / boundary list), or register the third sense in the map's glossary with a one-line fence ("OND residue list = out-of-scope observables; not an Echo residue, not a numerical residual"). Owner's call; the map can hold whichever way it goes.
2. OND ↔ family-map connection rows (proposal for review). OND's "observable trace is constant over the secret, relative to a declared observation model O" is conceptually adjacent to Echo (fibres over an observation function) and Residual Evidence Types (observation + evidence constraints over admissible worlds). And "The conserved quantity is state" (CNO) sits next to the cost/state split that occupancy-types is registering in the map. Suggest proposing two dashed-arrow rows (OND → Echo/Residual, CNO → Occupancy) in the map as research obligations only — the map's discipline ("a name alone does not establish a new primitive") applies. I have not added them unilaterally; this issue is the proposal.
3. FYI: januskey's pending reversibility formalisation looks like a natural CNO-adjacent consumer/sibling — noted there (its issue linked in nextgen-typing#118).

Tracked by: hyperpolymath/nextgen-typing#118