[roomote-roomote]

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

Related issue

Normal patch release preparation; includes #3567. No linked closing 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 1.19.1 → 1.19.2 from the published v1.19.1 tag at 4d533527b7dc101fd942d768d98db7920df9eca7 and audited develop 2466dc81da914b82804ca45f39c43c5db66fb122. The complete first-parent release range contains only #3567. Both main and develop were at 1.19.1; no pending changesets, higher-bump conflict, open preparation/Promote PR, or other running release preparation conflicted.

What changed

Generated the root patch version and changelog with pnpm run version, consumed the single locally authored patch note, and polished the in-app summary/highlight. Workspace package versions and historical release entries are unchanged.

Highlights

• Resume saved tasks after an upgrade instead of encountering a worker installation failure caused by an older snapshot image.

Patch changes

• Follow-ups can now resume tasks saved before a Roomote upgrade instead of failing during worker installation because the task snapshot was created with an older release. Worker startup warns about the older snapshot image and continues while still requiring the installed worker to match the application release.

Public documentation coverage

• Saved task snapshot resume after an upgrade ([Fix] Resume tasks whose snapshot baked an older worker release #3567): updated Worker runtime and saved snapshots to distinguish environment fresh starts from saved-task resumes, explain file preservation and worker/application compatibility, and retain tool/certificate maintenance requirements.
• No new capability, provider, integration, configuration, navigation entry, or icon is introduced; no other release-blocking docs gap was found.
• Contributor/reporter audit: [Fix] Resume tasks whose snapshot baked an older worker release #3567 is authored by directly listed CODEOWNER @mrubens and has no closing issue references. No eligible external acknowledgement is missing.

Squash-merging this PR cuts the release preparation and automatically opens the frozen Promote v1.19.2 to production PR against main. Promotion is separate and requires fresh CI and review evidence on its exact head.

How it was tested

• pnpm run version: generated 1.19.1 → 1.19.2 from one patch changeset.
• Release-invariant assertions: exact patch version; no remaining pending notes; README retained; historical changelog unchanged. Reviewed the three-file release-only diff; no workspace version changed. git diff --check passed.
• Ordinary push hook ran exactly once and passed oxlint, both residual lint tasks, all 27 fast typecheck tasks and Knip. Knip emitted a non-failing existing Mint ignore-binary hint.
• Pre-commit formatting passed. Local Judgement evidence/judgment collection was incomplete for criteria 7 and 8 across all three files; commit was allowed, but the full PR Judgement check remains required before merge.
• Rendered the real local Mintlify operations page and visually inspected the complete added paragraph. Screenshot proves documentation rendering, not runtime snapshot resume. Independent visual review found the stated docs claim supported; a byte comparison confirmed no source drift after capture.
• Per release guidance, full release-script tests, docs validation/link checks, repository formatting/lint/type suites and Knip were not separately rerun; the ordinary push hook provides the local static gate, and PR CI and Docs must succeed before merge.
• Re-audit and regenerate from latest develop if it advances before preparation merges. No merge, auto-merge, promotion, tag, publish, deployment or release workflow dispatch is part of this PR preparation.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description — release-specific skill requires Release Roomote 1.19.2 instead.
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally — full manual reruns deferred to PR CI per release skill; ordinary push static 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 — authored the prescribed patch input locally and consumed it with pnpm run version.

Screenshots

Genuine local docs preview, with no simulated state. Shows readable upgrade guidance; does not prove backend or sandbox resume behavior.

[roomote-community]

No code issues found. See session

Reviewed the patch version bump, release notes, and saved-snapshot operations guidance against the installer compatibility logic and regression coverage. Docs, lint, typecheck, deployment artifacts, upgrade compatibility, and Judgement checks passed; tests and the app image build were still running when inspected. Repository validation suites were left to CI.

_{Reviewed bb47134}