[roomote-roomote]

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

What changed

Prepare the approved patch release 1.19.2 → 1.19.3 from audited develop d307f5fa. Generate the root product version and changelog with pnpm run version, then polish the summary and two highlights for the in-app release display. The final diff contains only root package.json and CHANGELOG.md; workspace versions and earlier release entries are unchanged.

The audit covers all three merged PRs since published v1.19.2: scheduler-offset repair #3580, memory-backfill scheduling reliability #3581, and dependency security maintenance #3571. The dependency-only update ships without a separate public changelog bullet. No open preparation/Promote PR or newer unshipped candidate was found. There were no pre-existing pending changesets; both temporary patch inputs were consumed during generation. No eligible external contributor or issue-reporter acknowledgments were identified.

Patch changes

• Memory history backfills no longer pile up overlapping collector runs that delay scheduled automations, make worker health checks go stale, and trigger repeated worker restarts. Collection runs one at a time and yields between bounded backfill passes, preserving progress for the next scheduled run.
• Scheduled heartbeat and automation checks now recover their intended cadence after an interval change instead of continuing to run late because of an outdated scheduler offset. Roomote repairs affected schedules automatically when the background worker starts.

Public documentation coverage

• Scheduler repair: existing operations health guidance and custom-automation scheduling guidance remain accurate; this restores expected behavior and introduces no setup or configuration.
• Memory backfill reliability: existing memory guidance already describes bounded background passes that preserve and resume progress; no new feature or setup requirement.
• Dependency maintenance: no new user workflow, provider, integration, or icon requirement. No release-blocking documentation updates found.

Squash-merging this preparation PR cuts the release and automatically opens the frozen Promote v1.19.3 to production PR against main. This PR does not authorize promotion; the preparation and subsequent promotion each need their own successful CI and reviews.

How it was tested

• pnpm run version: generated 1.19.3 from two patch inputs and consumed both.
• Inspected the complete diff and verified exactly two artifact paths, version 1.19.3, summary/highlights plus two patch bullets, no empty major/minor sections, no pending changesets, retained changeset README, unchanged workspace versions and unchanged earlier changelog content.
• git diff --check passed. Ordinary pre-commit formatting passed.
• Ordinary push hook ran once and passed oxlint, web/worker residual ESLint, all 27 fast typecheck tasks, and Knip. Full release-script tests, full repository tests/static checks, and docs checks were not manually duplicated, per release guidance; PR workflows remain the merge gate.
• Local commit Judgement was incomplete: evidence collection/judgment failed for the two files on prose criteria 7 and 8; the hook allowed the commit but explicitly requires a full check before merge. Hosted Judgement/reviews must clear this gap.
• Browser proof is not applicable to this artifact-only diff; no screenshots or simulated state.

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 explicit Release Roomote 1.19.3 title.
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally — ordinary fast push gates passed; full aliases intentionally left to CI.
• 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 two canonical single-package patch inputs and consumed them with pnpm run version instead.

[roomote-community]

No code issues found. See session

Reviewed the root version bump and release notes against the merged fixes, release scripts, and repository guidance. Earlier release entries and workspace versions are unchanged. Current-head CI has passed tests, lint, type checks, Knip, deployment artifacts, upgrade compatibility, and hosted Judgement; the app image build and JavaScript/TypeScript CodeQL analysis were still running when checked.

_{Reviewed 1aa9646}