refactoring for canon conformity

docs/discovery-queries.md

@@ -90,6 +90,11 @@ The JSON export has two top-level arrays:
 - `edges`: graph relationships such as `provides`, `exposes`,
   `available_via`, `consumes`, `binds:<status>`, and `uses_interface`
 
+Canon-aligned exports also carry mapping metadata beside the existing Fabric
+terms: nodes include `canon_category`, `canon_anchor`, `mapping_fit`, and
+`evidence_state`; edges include `canonical_type`, `display_only`,
+`mapping_fit`, and `evidence_state`.
+
 The graph explorer payload wraps those nodes and edges as Cytoscape-compatible
 elements with stable keys, layers, display state, visual facets, source
 references, and deep links. The registry service exposes the same projection at