[Chore] Release Roomote 1.4.0

[roomote-roomote]

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

What changed

Prepare the confirmed minor 1.3.2 -> 1.4.0 release from develop d95a5fd045ff82f81d458256a6a871ec9cda611a. Regenerated from the published 1.3.2 baseline using pnpm run version, not merged generated output. Branch history and ready-for-review state are preserved without force-push.

The release contains 26 notes: 5 minor and 21 patch. All 25 previous topics remain, with three expanded notes and one added note. All prior documentation remains, with bounded-monitoring guidance added. Workspace package versions are unchanged; the final diff against develop contains only release metadata, seven documentation files, and three consumed tracked changeset deletions.

Latest audit

• [Improve] Offer bounded monitoring for ongoing processes #2291: expand reminders with opt-in bounded monitoring; document acceptance, finite bounds, early stopping and missing evidence.
• [Fix] Slack working indicator disappears during active session turns #2293: expand Slack activity coverage to Session turn ownership, retry waits and stale cleanup.
• [Improve] Show filenames and file counts in edit activity #2294: expand native edit receipts with filenames/file counts while keeping grouped edit-call counts accurate.
• [Fix] Telegram automation form says chat replies cannot resume Sessions #2287: add corrected Telegram automation continuation guidance.
• [Fix] Fast turns fail with integration tool schema errors #2295: already shipped via hotfix [Fix] Release Roomote 1.3.2 for Fast integration schema failures #2296 in 1.3.2; do not duplicate its integration-schema note.
• [Chore] Sync published Roomote 1.3.2 metadata to develop #2297: retain published release metadata; no new product note.
• [Refactor] Centralize artifact path lookup and version selection #2298: internal artifact persistence refactor; existing artifact-availability note retained.
• No eligible external contributor or linked issue-reporter acknowledgements found.

Minor changes

• GPT-6 Astra through Vercel AI Gateway, GitHub Copilot and OpenCode Zen.
• Inspectable Session tool exchanges and task report receipts.
• Depth-two subagent assistance with existing permissions preserved.
• Session-owned custom automations and same-thread suggestions.
• Session reminders, recurring checks and opt-in bounded monitoring.

Patch changes

• Dark-mode automation avatars.
• Default Azure idle suspension with explicit-zero opt-out.
• Cleaner web runtime navigation.
• Completed artifacts survive interrupted replacements.
• Accurate completed-proof lifecycle status.
• Cost separators and Task Info refresh.
• Device authorization recovery.
• Discord thread replies and contextual task links.
• Automation Fast model/reasoning overrides distinct from coding defaults.
• Retained Fast follow-ups and parked turns.
• Signed merge-announcement screenshots.
• Mobile cards, composer hints and automation spacing.
• PR feedback preparation retries.
• Structured provider tool-call qualification.
• Review-handoff user context.
• Explicit Sentry triage scope.
• New Session default-model reset.
• Slack working status follows active turn ownership and retry waits.
• UTF-8 streamed output.
• Native activity labels and edit filenames/file counts.
• Accurate Telegram automation continuation copy.

Complete generated wording and in-app highlights: CHANGELOG.md.

Automation upgrade notes

Configured environments are delegation preferences, not guaranteed sandbox launches. Set an explicit destination for chat reports; otherwise results remain in the web Session without an owner-DM fallback. Runs use creator-scoped credentials; only creatorless automations require admin re-save. Run now returns queued rather than launched/taskId or completion. Automation model overrides govern Fast; coding tasks use explicit selections or deployment coding defaults.

Feature-to-docs coverage

• Automations: execution, upgrade guidance, suggestions and Telegram continuity.
• Fast Sessions: receipts, reminders, capability-checked monitoring offers, acceptance, finite bounds and honest stop conditions.
• Models: Astra routes and bounded nested delegation.
• Vercel, Copilot, OpenCode Zen: access and shared source-backed provider marks.
• Sentry: ad hoc scope versus configured automation behavior.
• Already current: Azure, Discord, model separation and Fast recovery. Activity-label fixes require no new setup guide.

Squash-merging this PR makes CI open the frozen Promote v1.4.0 to production PR against main. CI and Docs must pass before separately approved merge. No merge, promotion, tagging, publication or deployment is part of this preparation.

How it was tested

• pnpm run version: generated 1.4.0 from 1.3.2 and consumed all 26 inputs.
• Integrity assertions passed: five minor/21 patch notes, three intentional expansions, all prior topics retained, published 1.3.2 and older changelog byte-for-byte preserved, scoped diff and unchanged workspace versions.
• git diff --check, source/docs audit and focused completion review passed.
• Normal pre-commit hook passed. First push hook found a missing local ajv/dist/2020.js dependency after incorporating develop; pnpm install --frozen-lockfile refreshed workspace links without tracked changes. Retried ordinary push hook passed oxlint, residual lint, all 27 fast type-check tasks and Knip. Existing non-failing mint configuration hint only; no hooks bypassed.
• Full tests, lint/typecheck and docs validation are delegated to PR CI under the release skill rather than duplicated locally. Refreshed-head CI/Docs/review results must be checked before merge.
• Browser proof not applicable to release metadata/docs; no screenshots claimed.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally (full commands delegated to CI; ordinary push gates passed)
• 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 (prescribed inputs reconstructed and consumed via pnpm run version, not interactive CLI)

[roomote-community]

No new code issues found. See task

_{Reviewed db5a065}