[Chore] Release Roomote 0.45.1 hotfix for Notion database discovery

[roomote-roomote]

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

What changed

Cuts production hotfix Roomote 0.45.1 from current main / v0.45.0 with the complete merged develop fix from #1825:

• enumerate every shared Notion data source so database rows missing from search are ingested into Memory
• persist data-source enumeration across passes and restart safely when a Notion cursor expires
• let the Notion MCP fetch database objects and guide agents from databases to data sources and rows
• document database-row discovery
• bump the single product version from 0.45.0 to 0.45.1 and add the generated 0.45.1 changelog section

The patch changeset is preserved in commit a0c968b6 and consumed by the repository-owned pnpm run version flow in commit 2128ad2f; no inert pending changeset remains on the release tree.

Why this change was made

Notion database rows inherit integration access but are often absent from Notion search results. That left pages inside directly shared databases undiscoverable by both Memory ingestion and the deployment Notion MCP.

main already contains prerequisite #1726 (6409841f), which added the traversal foundation this hotfix extends. Live verification has already succeeded for database fetch, data-source row query, full row fetch, and Memory ingestion.

Merge and tag instructions

1. Merge this PR into main with a merge commit. Do not squash or rebase it; this preserves the hotfix changeset/versioning history and matches the direct-main hotfix convention from [Chore] Release Roomote 0.4.2 hotfix for saved Slack continue #302.
2. The main push starts Tag Product Release, which must create and push annotated tag v0.45.1 from the merged hotfix tree.
3. Wait for that workflow to succeed and verify the remote v0.45.1 tag exists. The tag then triggers the GHCR image publish and GitHub Release flow.
4. Only after v0.45.1 exists, squash-merge companion develop sync #1841. Do not merge [Chore] Record Roomote 0.45.1 on develop after production hotfix #1841 first.

Impact

After deployment, Memory can discover rows inside directly shared Notion databases, and agents can resolve those databases through the built-in Notion MCP. The release includes no database schema or persisted-data migration.

Validation

• final origin/main...HEAD diff contains only the original four [Fix] Discover pages inside shared Notion databases #1825 files plus root package.json and CHANGELOG.md
• the original code patch still matches squash commit d55de215db6c602fbbf1ac3f27114eb724b86098
• release-script tests: 16 passed
• Notion API MCP tests: 7 passed
• BullMQ Brain Notion collector tests: 23 passed
• API and BullMQ TypeScript checks passed
• Notion docs validation and broken-link checks passed
• repository formatting check passed
• repository pre-push gate passed: oxlint, residual ESLint, fast monorepo typechecks, and knip

Risk and rollback

Runtime risk is limited to additional bounded Notion search/query work during the existing traversal cycle. Enumeration state is backward-compatible, and expired search cursors restart rather than wedging collection.

Rollback the application by redeploying v0.45.0. If this PR has merged but v0.45.1 has not been consumed externally, the Git history can also be reverted as one merge commit. There are no schema changes or data migrations to reverse. Do not reuse or move the immutable v0.45.1 tag after publication.

Related PRs

• develop version-record companion #1841

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Aug 29, 2026, 3:00 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[roomote-community]

No code issues found. See task

_{Reviewed 2128ad2}