Changelog

prepublishOnly gates were red. Fixed: image-picker deps.env string → typed object (UNSPLASH_ACCESS_KEY, scope server, optional); slice-schema gains optional deps.sharedFiles (notion-database / notion-shell already used it); version/title parity synced for resend-newsletter (0.1.3), ai-chat (0.2.0), landing-sections (0.2.0), markdown title; deleted stale template-base/frontend/slices/notion port-staging copy (R1 dual-home); AiChatFab refactored props-driven — convex/react import replaced with injected `chat` prop (R3).

md-reader renamed to `markdown` and maximised. <MarkdownPage> adds optional surfaces: Read (rich text), Write (raw source editor with snippet toolbar + live preview), Review (block-anchored comments with add/resolve — controlled callbacks or internal fallback). Fenced ```mermaid blocks render as SVG diagrams (dynamic-imported mermaid) and ```chart blocks as recharts bar/line/area/pie from a JSON spec. Notion sync grammar unchanged.

New read-only surface that renders a markdown string as a clean document (headings, lists, todo, callouts, fenced code, KaTeX, tables, images, toggles, inline marks). Sync with the notion block editor is by shared grammar: a new notion bridge (blocksToMarkdown / markdownToBlocks) serialises blocks ↔ the exact markdown this reader parses — so anything readable as a notion page is readable here, and back. Self-contained (own parser + inline renderer, no notion runtime dep). 21 tests.

Reverting to the shadcn Calendar broke picking again (it's the unreliable part here); the self-contained DateCalendar grid is what works. Restored it and added Notion-style range picking: with End date on, click 1 = start, click 2 = end (the earlier of the two is always kept as start, so clicking before the start swaps them); clicking once a full range exists starts a fresh range.

Root cause: the repo pinned react-day-picker ^10.0.0, but this shadcn Calendar component is generated for rdp v9; v10's breaking changes silently stopped the controlled mode/selected/onSelect path from registering day clicks (same bug in notion-page-clone). Fix: pin react-day-picker to ^9.14.0 (what the shadcn Calendar targets) and restore the canonical Popover + Calendar date picker (mode=single / mode=range).

Dates couldn't be picked (same in notion-page-clone) — the controlled mode/selected/onSelect path broke under react-day-picker v10. The calendar now handles clicks via onDayClick and drives the selected-day + range highlight purely from `modifiers`, both fed by our own value, so it no longer relies on rdp's internal selection state machine.

Ported the recursive nested-block tree behind the adapter seam: NestedBlock (self-registering dispatcher) + NestedContent (by-type renderer — database via adapter.database, page nav via adapter.page, page icon via a built-in PageIcon, code via SimpleCodeBlock) + ToggleBlock + ColumnBlockEditor (split into column/panes) + SyncedBlock (split into synced/views + ChildrenList, cross-page source via pages/workspaceId) + NestedBlockControls. Completes M2b — chrome + nested rendering done. Next: M2c BlockEditor/page shell.

react-day-picker range mode wasn't registering clicks. Switched the calendar to single mode (the proven path) for both modes: range now uses an active-field model (two fields, click to choose which the calendar edits — matching Notion's blue active field) with the start→end span shaded via modifiers. Picking works again.

Fixed: dates couldn't be picked in range mode (an empty cell passed a {from:undefined} range that broke react-day-picker's first click — now passes undefined). The cell's End-date toggle now patches prop.dateRange, the same switch the column header's edit-property panel toggles, so the two stay in sync.

Ported the per-block toolbar (BlockControls hub + MenuHierarchy action menu + QuickButtons/GripButton) against the frozen seam: data CRUD + selection via useEditorData/useSelection, comments via useComments (popover + count), AI panel via optional useAi. The nested-rendering subtree (toggle/columns/synced) is the next slice (M2b.2b).