f4346f95d4
The agent had no way to infer the mcp:// prefix needed to read MCP server resources. Attempting <server>://<resource> directly fails. All other internal URL schemes (skill, rule, memory, agent, etc.) are already listed in the Internal URLs section of the system prompt. Added mcp://<resource-uri>. URI resolution: exact resource listings first, then RFC 6570 URI templates advertised by connected servers.