[roomote-roomote]

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

Related issue

Normal maintainer-requested release preparation; no separate issue.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

Prepare Roomote 1.19.7 → 1.20.0 using the explicitly selected minor bump. The inbound MCP changeset was deliberately downgraded from major to minor for this release; its compatibility warning remains prominent. The highest final input is minor.

What changed

Generate the root version and changelog with pnpm run version, consume both existing changesets plus one locally authored connection-test note, and polish the in-app summary and four highlights. Workspace versions are unchanged.

The complete published-v1.19.7 release inventory through develop 518d29bd71985e9db62a2d3597abfbf523e150e7 is #3658, #3655, #3657, #3649 and #3625. The already-merged dependency updates include follow-redirects 1.16.2 and @hono/node-server 2.1.3; they ship without separate dependency-only changelog bullets. No further dependency PR was merged by this preparation.

Minor changes

• Test a saved remote MCP server's connection on demand from Manage tools in shared or personal integration settings. Each test retrieves a fresh tool catalog using the saved authentication, reports success or failure even for an empty catalog, and leaves tool approval choices and server enablement unchanged. Local stdio servers still need to be checked inside a task sandbox.
• Manage and revoke inbound MCP client authorizations from personal settings or, for admins, by user in users settings, including revoking all clients for a user. Revocation blocks already-issued OAuth access tokens on subsequent requests. Upgrade compatibility: legacy MCP access tokens without client/grant identity receive 401 after API enforcement is deployed. Deploy the updated web authorization server and drain all old issuer instances before upgrading the API. Live legacy refresh sessions are backfilled without extending their original expiry; clients without a usable refresh session, or unable to refresh after a 401, must reconnect and repeat browser consent. In-progress legacy authorization codes also require consent again. Redis outages refuse OAuth access, and lost authorization data requires reconnecting. Rolling back the API removes prompt revocation enforcement; rolling back the authorization server may require reconnecting migrated clients.

Patch changes

• Stop repeated identical tool-call loops and bound subagent passes. Enforce a durable task-wide inference request ceiling before dispatch, retain partial work, and save a visible safety notice without requiring another model response.

Public documentation coverage

• Inbound MCP management, permissions, refresh/reconnect and staged upgrade/rollback: Roomote MCP and upgrade guidance are already current.
• Fresh remote connection tests, private/shared placement and stdio limits: Custom MCP servers is already current.
• Safety stops, durable limits and continuation: Tasks and Cost analytics are already current.
• No new provider or logo, navigation entry, or release-blocking public docs change is needed. Roomote MCP retains its source-backed Roomote mark.

Squash-merging this PR cuts the release and automatically opens the frozen Promote v1.20.0 to production PR against main. That candidate requires independent current-head CI and review; this PR does not authorize promotion or publication. If develop advances before merge, re-audit and regenerate the release artifacts.

How it was tested

• Canonical pnpm run version produced 1.20.0 from three inputs (two minor, one patch).
• Release artifact assertions passed: all pending notes consumed; .changeset/README.md retained; previous changelog history unchanged; root package delta is version-only; no workspace versions changed; final paths are root package.json, CHANGELOG.md and two consumed changeset deletions. Legacy 401/reconnect and web-before-API warnings verified.
• git diff --check passed. Pre-commit formatting and Judgement passed (8 judgments).
• Ordinary push hook ran once and passed: oxlint, both residual ESLint tasks, all 27 fast typecheck tasks, and Knip. Existing circular-package warnings and one non-failing Knip configuration hint remain.
• Full release-script/docs/test/static suites were left to the PR workflows per the release skill. Browser proof is not applicable to this release-artifact-only diff.
• Preparation CI and required reviews must pass before merge. The earlier dependency PR checks do not clear this new release head.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description — uses the release skill's required Release Roomote 1.20.0 title.
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally — ordinary pre-push fast equivalents passed; full formatting-inclusive commands are left to CI per release guidance.
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset — authored/updated equivalent changeset inputs and consumed them with canonical pnpm run version.

[roomote-community]

No code issues found. See session

Reviewed all four changed files, release tooling and release-note consumers. The root-only version bump, consumed changesets, preserved changelog history, and MCP upgrade/refresh/reconnect/rollback guidance are consistent with the release scope. The minor bump is explicitly selected in the PR context.

Current-head lint, typecheck, Knip, deployment and upgrade-compatibility checks passed. Tests, the app image build, and JavaScript/TypeScript CodeQL analysis were still running at the last check. Repository validation remains with CI.

_{Reviewed 3bc827e}