kimi-desktop 0.1.6: a conversation quoting [agent-profile-route gets 409 even with roles off #850

Found reviewing #813 at 6e3257e (kimi-desktop 0.1.6).

adapter.mjs:472 refuses every inference whose outgoing body contains [agent-profile-route or [/agent-profile-route anywhere (RESERVED_ROUTE), with HTTP 409 agent_profile_unbound. The check runs for every connection, including one that never selected a secondary model and so has no role plugin, no routing secret and no bindings.

So a conversation that quotes the marker, in a user message or a tool result (for example asking Kimi Work about this plugin's agent-routing.mjs or README), gets 409 on that request and on every later one, because the history keeps the text. 0.1.5 had no such refusal.

Reproduced with the lifecycle fixture (no secondaryModel, never opted in): one user message What does \[agent-profile-route:v1]` in adapter.mjs do?returned 409agent_profile_unbound`, and nothing was forwarded.

A forged section outside a system/developer message can't choose a route (only authenticated sections in system text are read), so refusing it protects nothing when roles are off. With roles on, the router's own RESERVED_PROFILE check refuses the same quoted text in user and tool messages too. Suggested scope: check for leftover markers only in the text the router strips (system/developer messages), and forward user and tool content as written. Tests: a never-opted-in and an opted-in conversation whose user message quotes the marker are both forwarded unchanged, and a forged section there still selects no route.