list_registry_edges
Enumerate the registry's INTERNAL edges: the read counterpart to `create_registry_edge`. These edges live in `registry.edges` in the portfolio document and never touch a product graph, which is why the product-scoped readers miss them. `export_edges` enumerates the ACTIVE PRODUCT's edges and returns an empty array for registry-only types, and an empty array meaning *wrong scope* is indistinguishable from one meaning *no such edges*. Ask this tool "what points at this canonical" before planning any migration that retires or re-points registry entities, because `list_registry`'s `instance_count` counts only inbound `instance_of` edges from product graphs, not these. Returns the same `{ id, source, target, type }` shape as `export_edges`, with bare (unqualified) registry endpoint ids.
Arguments
typesarrayoptionalFilter to these catalog edge types (omit to enumerate all registry edges).
endpoint_idstringoptionalFilter to edges touching this registry node in EITHER direction (bare or registry/{id}).
source_idstringoptionalFilter to edges leaving this registry node (bare or registry/{id}).
target_idstringoptionalFilter to edges arriving at this registry node (bare or registry/{id}).
Returns
{ edges: Array<{ id, source, target, type }>, total, by_type }Returns an empty enumeration when no portfolio/registry exists yet.