Allow users to pan the desktop and tablet board from noninteractive task-card surfaces without disrupting controls or mobile scrolling.
- Start horizontal panning from eligible task-card bodies and text while preserving native controls and editing behavior.
- Wire board pan state and cursor styling across live board roots while keeping mobile snap and touch scrolling unchanged.
- Add regression coverage, documentation updates, and a patch changeset.
Files changed:
.changeset/fn-109-board-card-pan.md | 7 ++
docs/dashboard-guide.md | 5 +-
docs/task-management.md | 4 +-
packages/dashboard/app/components/Board.css | 7 +-
packages/dashboard/app/components/Board.tsx | 8 +-
.../app/components/__tests__/Board.test.tsx | 98 ++++++++++++++++------
.../app/hooks/__tests__/useBoardMousePan.test.tsx | 47 ++++++++++-
packages/dashboard/app/hooks/useBoardMousePan.ts | 12 +--
8 files changed, 146 insertions(+), 42 deletions(-)
Fusion-Task-Id: FN-109
Fusion-Task-Lineage: 456bd9d3-9767-4b82-9f99-f191abc44b18
Co-authored-by: Fusion <noreply@runfusion.ai>
Each changeset file in this directory describes one user-facing change for release notes.
Required body format
---
"@runfusion/fusion": minor
---
summary: Add a Command Center productivity control for LOC backfills.
category: feature
dev: Uses the new `fn_backfill_loc` tool; settings key `commandCenter.locBackfill`.
Fields
Field
Required
Description
summary
Yes
One line, user-facing, max 120 chars. Describe what changed for the operator.
category
Yes
One of: feature, fix, breaking, security, performance, internal.
dev
No
Developer or migration detail. Preserved in per-package CHANGELOGs but excluded from distilled release notes.
Audience
The summary is the only content that appears in end-user release notes by default. Write for Fusion operators — describe behavior, fixes, and what changed. Avoid internal class names, file paths, and implementation detail.
Bump types
patch — bug fixes, internal changes
minor — new features, CLI additions, tools
major — breaking changes
Validation
Run pnpm check:changesets to validate. The linter runs in the PR-check gate and test:gate. Legacy freeform changesets pass with a warning during the transition period.