chore(web)(deps): bump framer-motion from 13.4.6 to 14.0.0 in /web

[dependabot]

Bumps framer-motion from 13.4.6 to 14.0.0.

Changelog

Sourced from framer-motion's changelog.

[14.0.0] 2026-10-02

Changed

• Removed internal APIs restored in 13.5.1 for compatibility with framer-motion 13.0–13.4. Future removed internal APIs won't cause cross-compatibility issues since pinning internal framer-motion, motion-dom and motion-utils dependencies.

[13.5.1] 2026-10-02

Changed

• <motion>: Fall back to the attribute in readSVGValue when computed style is empty.
• <motion>: Internal changes to animateChanges for size reductions.

Fixed

• scroll: Temporarily reverted removal of internal observeTimeline API to fix compatibility with previous 13.x APIs. Moving to pinned dependencies before removing in 14.x.
• styleEffect: Cleaning up an earlier value no longer removes a value that was bound to the same key after it.
• svgEffect: No longer writes transforms and origins as attributes.
• <motion>: inherit={false} now correctly not inheriting parent animations.
• <motion>: Fix sortNodePosition throwing when a sibling hasn't mounted

[13.5.0] 2026-10-01

Added

• spring: Now accepts negative bounce (0--1) to define overdamped springs.

Changed

• <m>: 20% smaller.
• useSpring: 10% smaller.
• scroll/useScroll: Use main thread for all offset animations.

Fixed

• Ensure warning and error messages are cleaned from production build.
• Ensure values are never rendered before they've been resolved.

[13.4.7] 2026-09-30

Changed

• scroll/useScroll: More offsets are now hardware accelerated via ViewTimeline.

Fixed

• animate: Reduced size of Motion Studio introspection call.
• useTransform: Accelerated values now correctly clamp.
• scroll/useScroll: Ensure offsets work the same across the JS main thread and ViewTimeline.
• scroll/useScroll: Remove ScrollTimeline/ViewTimeline observer in favour of main-thread scroll tracking.

Commits

• f5838ce v14.0.0
• 351f7d0 Updating changelog
• 5da7dcd Merge pull request #3889 from motiondivision/cursor/v14-remove-shims-4e79
• 0897128 Remove 13.5.1 compatibility shims for framer-motion 13.0–13.4
• d4638ea v13.5.1
• 43cd77e Updating changelog
• 7005965 Merge pull request #3888 from motiondivision/cursor/restore-observe-timeline-...
• 7bf77e9 Merge pull request #3884 from motiondivision/cursor/sort-node-position-unmoun...
• c0495b0 Merge pull request #3887 from motiondivision/cursor/exact-internal-deps-4e79
• 9a16751 Honour deprecated rangeStart/rangeEnd in attachTimeline
• Additional commits viewable in compare view

[engrams-agent]

Major bump review — framer-motion 13.4.6 → 14.0.0

What upstream changed: framer-motion 14.0.0 removes the internal/private APIs that 13.5.1 had temporarily re-introduced for cross-version compatibility with 13.0–13.4, and pins its internal motion-dom / motion-utils dependencies so future removals of private APIs cannot break mixed installs. There are no changes to the public component/hook surface in this release.

What was migrated: Nothing. The web app consumes only the public API — motion, useReducedMotion, and layoutId — in web/src/components/Glyph.tsx, web/src/components/ui/tabs.tsx, and web/src/pages/reviews/ReviewGlyph.tsx. No internal/private framer-motion symbols are referenced anywhere in web/.

What I verified: the change is version-only (web/package.json + web/pnpm-lock.yaml), and the web (pnpm) lane (typecheck + lint + build) passes on this PR. Since the removed surface is exclusively private/internal and un-referenced here, the major bump is compatible with our usage.