[Fix] manage_environments tool receives empty arguments on some models

[roomote-roomote-v1]

Opened on behalf of Matt Rubens. Follow up by mentioning @openmote, in the web UI, or in Slack.

What changed

The manage_environments MCP tool's definition field used z.union([z.string(), z.record(z.unknown())]) — the only such union in the Roomote MCP server. That schema serializes to a JSON Schema anyOf plus an empty additionalProperties: {} object, which some model/provider tool-call paths drop entirely, sending an empty {} arguments object to the server. The MCP SDK then reports action and definition as undefined and the handler never runs, blocking the environment-setup skill from persisting any environment.

This changes definition to a plain z.string(). The handler in create-environment.ts already accepts YAML/JSON strings and auto-detects format, so no logic change was needed — only the wire schema. The field description now says "YAML or JSON string" instead of "YAML/JSON string or object." A regression test asserts definition is a z.ZodString, not a z.ZodUnion, so the union cannot sneak back in.

Why this change was made

manage_environments was the only Roomote MCP tool that broke on certain model/provider paths, while simple-schema tools (manage_tasks, etc.) worked in the same session. The union schema's anyOf serialization was the differentiator. Removing the union from the wire schema makes the tool arguments survive the tool-call layer reliably regardless of provider.

Impact

Agents calling manage_environments now consistently deliver their action and definition arguments to the server across all models/providers. Object definitions are no longer accepted over the wire (agents pass a YAML or JSON string, which the environment-setup skill already does), while the handler's internal object-handling path remains as a harmless fallback for direct/test callers. No user-visible behavior change beyond the tool working reliably.

[github-actions]

Thank you for your contribution! Before we can merge this pull request, we need you to sign our Contributor License Agreement. You can sign it by posting the comment below.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[roomote-roomote-v1]

No code issues found. Reviewed the wire-schema change and its regression test. See task