[Fix] Release Roomote 1.3.2 for Fast integration schema failures

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Emergency patch release 1.3.1 → 1.3.2, branched from latest main c06990c6. Includes only the complete schema fix from #2295 (b85611efe0df620a43032fcc160e1763c687ccbe) and generated release metadata. Merge this PR with a merge commit, never squash/rebase.

Fast's integration-call wrapper emits concrete non-recursive JSON value alternatives, preserving nested arguments and existing recursive server validation. Regression tests compile serialized native schemas after OpenCode normalization with Ajv2020.

Why this change was made

OpenCode 1.18.10 renames $defs to definitions without rewriting references created by z.json(), producing invalid Fast tool schemas. This hotfix avoids those references without reverting the concrete JSON argument support in #2237.

The cherry-pick required test-context resolution only: add imports required by the new regressions, but do not bring the unrelated Sentry test added later on develop. No runtime prerequisites, database changes, or unrelated develop commits are included.

Impact

Six-file net scope: native bridge, native-schema regression test, cloud-agents package manifest, lockfile, root package version, changelog. Workspace versions unchanged; the single hotfix changeset was consumed by pnpm run version. Docs audit: small behavior-restoring fix, no new configuration or release-blocking public documentation update.

Release note: Fix Fast turns failing with integration tool schema errors while preserving support for nested integration arguments.

Validation: ordinary pre-push lint, monorepo fast types and knip passed. Full PR CI must pass before merge. A repeated real OpenRouter openai/gpt-4.1-mini smoke on freshly generated hotfix tools passed discovery, safe-stub invocation, nested JSON preservation and final response. This is isolated OpenCode inference, not full Fast orchestration or a customer integration. No live customer resolution is claimed.

Release order: merge this production PR; wait for Tag Product Release and tag-triggered Publish GHCR Images, verify immutable images and GitHub Release; only then merge the companion two-file version/changelog sync to develop. Publication is not customer deployment.

Rollback: before external consumption, revert the hotfix merge only if operationally safe. After publication, redeploy immutable v1.3.1 (for Compose, roomote upgrade v1.3.1); never move/delete/reuse v1.3.2. There are no database changes, but rollback restores the Fast schema defect.

[roomote-community]

No code issues found. See task

_{Reviewed ccae4ea}

[roomote-roomote]

Companion release-metadata sync: #2297. It must remain unmerged until this PR merges with a merge commit, Tag Product Release succeeds, and immutable v1.3.2 images plus the GitHub Release are verified published. The hotfix live safe-stub inference check passed; full customer/integration deployment remains unverified.