chore: sync upstream cella v0.10.2 (55af2fac)

[flipvh]

Syncs upstream cellajs/cella to 55af2fa (v0.10.2).

7 upstream commits since last sync (compare):

• 45923f2 fix(sync): act on app sync feedback: marker-aware vocabulary gate, route tree script, portable mention fixture (fix(sync): act on app sync feedback: marker-aware vocabulary gate, route tree script, portable mention fixture cella#1150)
• 8870467 fix(attachments): description edits survive stale clocks, emptied documents and sheet dismissal; keywords derived on update (fix(attachments): description edits survive stale clocks, emptied documents and sheet dismissal; keywords derived on update cella#1152)
• 4e83dfe feat: attachment and yjs refactoring (feat(seed): attachment rows point at published seed assets in the public bucket cella#1146)
• a826b1f fix(attachment): dialog image fits between the chrome, one zoom clamp for wheel, pinch and buttons (fix(attachment): dialog image fits between the chrome, one zoom clamp for wheel, pinch and buttons cella#1153)
• 17d7838 chore: update dependencies (chore: update dependencies cella#1154)
• b682f78 fix(test): exclude the storybook browser project from root vitest runs (fix(test): exclude the storybook browser project from root vitest runs cella#1155)
• 55af2fa chore(main): release 0.10.2 (chore(main): release 0.10.2 cella#1151)

Conflicts

One: backend/tests/attachment-notifications.test.ts. Upstream #1150 adopted raak's most-privileged-role fixture, so ours = theirs + fork marker. Took theirs, marker retired. No fork markers remain in cella-owned code except the new bench seed below.

Migrations marked (3)

• 20260907T0619-route-tree-generation-script: gen:routes / generate:routes scripts and @tanstack/router-generator arrived through package sync; vite.config.ts now uses vite/router-options.ts. Verified: pnpm generate:routes leaves routeTree.gen.ts unchanged.
• 20260907T0711-description-seed-preview-hooks: 15-tasks.seed.ts builds paragraphs with paragraphBlock/text from description-document.ts (checklist loop kept, explicit props in BlockNote key order); use-task-description-update.ts composes patchCollaborativeDescription + persistStandaloneDescription (derived props computed once, triggerTaskGlow kept after the collaborative patch). The task editor already renders a faded static preview as waitingFallback. 20-attachment.seed.ts still goes through the pinned placement seam.
• 20260909T0740-yjs-update-log: pnpm generate emitted 20260909171506_calm_scarlet_witch (yjs_updates table, RLS enabled, last_edited_by dropped) + 20260909171507_side_effects (RLS set now 5 tables). No fork code imports the yjs storage API. y-websocket dev dep installed.

Pinned files

Upstream touched two pinned files with comment/copy-only deltas: routes-config.tsx (notificationSearch doc comment, hand-adopted) and locales/en/about.json (sync_diagram.part_3.text, key not present in raak's about.json, nothing to adopt).

Tests

pnpm check clean. pnpm test (full, docker test db): 2721 passed, two failures triaged:

• bench/src/tests/all-scenarios.test.ts: pre-existing since 2026-09-02, not sync damage (fails identically on main). Two causes, both fixed here: raak's attachments.project_id FK (Feat/cella drift convergence #131) while the bench attachment seed never assigned a project, and tasks.mentions (v0.9.8 sync) not declared as a native pg array. Fix: fork-marked projectId + order: 115 in bench/src/seeds/attachment.bench.ts, 'mentions' added to pgArrayColumns in fork-owned task.bench.ts. Passes now.
• yjs/src/tests/integration/concurrency.test.ts "burst of keystrokes" e2e: upstream flake, ~1 in 5 runs on an idle machine, readLog(...).length === 3 never met within 3 s. raak's yjs/ is byte-identical to upstream. Likely the relay's server-side Step1 pull racing the burst (a 4th log row, or compaction consuming the log before the poll sees 3). To report upstream.

Drift (pnpm cella analyze)

before: diverged 1, pinned 2, drifted 0, behind 107 → after: diverged 0, pinned 0, drifted 1, behind 5.

• drifted 1: bench/src/seeds/attachment.bench.ts, fork-marked (project-homed attachment axis). Candidate extension point: a bench placement hook next to the backend attachment-placement.ts seam would let the fork drop the marker.
• behind 5: cella #1156 (infra VM IAM reconcile) landed on upstream main during this sync; next sync picks it up.