50a94714ec
The central DB (~/.fusion/fusion-central.db) is opened concurrently by every fusion process on a host. In WAL mode those connections coordinate through a memory-mapped `-shm` wal-index; on macOS/APFS a reader takes a SIGBUS (walIndexReadHdr / `cluster_pagein past EOF`) when another process resizes it mid-checkpoint, killing the node process with no JS stack or log. Observed 3x in 3 days. Switch the central DB to journal_mode=DELETE, which uses no `-shm` mmap and coordinates cross-process access via POSIX byte-range locks instead; busy_timeout absorbs the added writer serialization. Per-project DBs keep WAL. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Changeset Format Guide
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 changesminor— new features, CLI additions, toolsmajor— 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.