[adibhanna]

Adopts core 2.69.1 (core-2.69.1-core.h3b2f026d7dfd6c7d, built by CI from ZenNotes/zennotes 86e98b49, the v2.69.1 release commit).

Not a release: no version bump, and it waits for the next Android release. The core release is still a draft on ZenNotes/zennotes; it is published once the phones ship on it.

What it brings

Convert to database offers the heading right above the table as the database's name in a long note too. It read the editor's syntax tree, which spans the whole note even while the parse has not reached the table, so in a note opened a moment ago it could offer an earlier heading; it now parses up to the table before choosing (ZenNotes/zennotes ba74c54f). The name could be edited before saving, so nothing was saved under it unseen.

The rest of 2.69.1 needs a desktop: renames on Windows, the MCP server's task lines, and What's New. No new bridge method, palette command or long-press entry.

Checks

• npm run core:adopt -- core-2.69.1-core.h3b2f026d7dfd6c7d --source 86e98b49d6a0be5e9c52e4e9b1c414977cbfbd29: SHA-256, SHA-512, packed versions and clean-source provenance verified. The vendored headingAbove calls ensureSyntaxTree(state, pos, 50).
• npm run upstream (boundary check and typecheck), npm test (278 pass), npm run sync.
• No emulator pass: the change is core logic, and the three archives are byte for byte the ones the iPhone shell adopted (fix(mobile): adopt core 2.69.1, a converted table is named after the heading above it zennotesios#60, same SHA-256), where the table cell's menu offered "Roadmap" under # Roadmap in a long note and converted the table.

How to test locally

1. Build and install a debug build on an emulator (npm run build && npx cap sync android && (cd android && ./gradlew assembleDebug), then adb install).
2. Make a note with # Early at the top, about fifty paragraphs, then # Roadmap with a table under it.
3. Open the note, open a table cell's menu and choose Convert to database…. The name offered is "Roadmap".