zeekayandHanzo Dev 4593f61024 An unresolvable prefix refuses, as the rule above it says ...

routerPrefix promises that an unresolvable router "is an error naming the
call, never an assumed empty prefix", and then returned the empty prefix for
a group. So a group handed to another function filed its ops at the path
after the prefix — an address nothing serves — in the document and the MCP
tool alike, which is the silent drop the resolution exists to end.

The one shape this hits is a group reached through a parameter: the prefix
belongs to the call that made the group, and the call is in another
function. The error says so now, rather than leaving the reader to infer it
from a path that looks plausible.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-17 22:09:49 -07:00

..

x.go

An unresolvable prefix refuses, as the rule above it says

2026-09-17 22:09:49 -07:00