Release v0.9.0

.changelog/NEXT.md

@@ -0,0 +1,9 @@
+# Unreleased Changes
+
+## Added
+
+## Changed
+
+## Fixed
+
+## Removed

.changelog/README.md

@@ -1,128 +1,104 @@
 # Release Changelogs
 
-This directory contains **all** release notes for SparseTree. Unlike traditional projects that maintain a root `CHANGELOG.md` file, we use version-specific files that evolve with development and automatically archive on release.
+This directory contains detailed release notes for each version of SparseTree. These files are used by the GitHub Actions release workflow to create rich, user-friendly release descriptions.
 
 **No root CHANGELOG.md needed** - all changelog content lives in this directory.
 
 ## Structure
 
-Each minor version series has its own markdown file following the naming convention:
+### NEXT.md — Unreleased Changes Accumulator
+
+During development, all changelog entries are appended to `NEXT.md`. This file accumulates changes across multiple commits until a release is created.
+
+- `/cam` (commit all my work) automatically adds entries to `NEXT.md`
+- `/release` renames `NEXT.md` to `v{version}.md` and finalizes it with the version number and release date
+- Do NOT create versioned changelog files manually — `/release` handles that
+
+### Versioned Files
+
+Each release has its own markdown file:
 
 ```
-v{major}.{minor}.x.md
+v{major}.{minor}.{patch}.md
 ```
 
-The "x" is a literal character, not a placeholder - it represents the entire minor version series (e.g., all 0.2.x releases share `v0.2.x.md`).
-
-Examples:
-- `v0.1.x.md` - Used for releases 0.1.1, 0.1.2, 0.1.3, etc.
-- `v0.2.x.md` - Used for releases 0.2.1, 0.2.2, 0.2.3, etc.
-- `v1.0.x.md` - Used for releases 1.0.1, 1.0.2, 1.0.3, etc.
+These are created automatically by `/release` from `NEXT.md`.
 
 ## Format
 
 Each changelog file should follow this structure:
 
 ```markdown
-# Release v{major}.{minor}.x - {Descriptive Title}
+# Release v{version}
 
 Released: YYYY-MM-DD
 
 ## Overview
 
-A brief summary of the release, highlighting the main theme or most important changes.
+A brief summary of the release.
 
-## 🎉 New Features
+## Added
 
-### Feature Category 1
-- Feature description with technical details
-- Another feature in this category
+- Feature descriptions
 
-## 🐛 Bug Fixes
+## Changed
 
-### Fix Category
-- Description of what was fixed
-- Impact and technical details
+- What was changed
 
-## 🔧 Improvements
+## Fixed
 
-### Improvement Category
-- What was improved
-- Why it matters
+- Description of what was fixed
 
-## 🗑️ Removed
+## Removed
 
-### Deprecated Features
 - What was removed
-- Why it was removed
-
-## 📦 Installation
 
-\`\`\`bash
-git clone https://github.com/atomantic/SparseTree.git
-cd SparseTree
-npm run install:all
-pm2 start ecosystem.config.cjs
-\`\`\`
+## Full Changelog
 
-## 🔗 Full Changelog
-
-**Full Diff**: https://github.com/atomantic/SparseTree/compare/v{prev}...v{major}.{minor}.x
+**Full Diff**: https://github.com/atomantic/SparseTree/compare/v{prev}...v{current}
 ```
 
-## Workflow
-
-### During Development
+## Workflow Integration
 
-Update `.changelog/v0.2.x.md` **every time** you add features and fixes:
-- Add entries under appropriate emoji sections (🎉 Features, 🐛 Fixes, 🔧 Improvements)
-- Keep the version in the file as `v0.2.x` (literal x)
-- Don't worry about the final patch number - it will be substituted automatically
+The GitHub Actions release workflow (`.github/workflows/release.yml`) automatically:
 
-### Before Releasing
+1. Checks for a changelog file matching the version in `package.json`
+2. If found, uses it as the GitHub release description
+3. If not found, falls back to generating a simple changelog from git commits
 
-Final review before pushing to `release`:
-- Ensure all changes are documented
-- Add release date (update "YYYY-MM-DD" to actual date)
-- Review and polish the content
-- Commit the changelog file
-- Bump version in `package.json`
+## Development Workflow
 
-### Triggering a Release
+1. **During Development**: Each `/cam` commit appends entries to `NEXT.md` under the appropriate section (Added, Changed, Fixed, Removed)
 
-Push main to the release branch:
-
-```bash
-git push origin main:release
-```
-
-### On Release
-
-The GitHub Actions workflow automatically:
-1. Reads `.changelog/v0.2.x.md`
-2. Replaces all instances of `0.2.x` with the actual version (e.g., `0.2.5`)
-3. Creates the GitHub release with the substituted changelog
-4. Renames `v0.2.x.md` → `v0.2.5.md` on `main` (preserves git history)
-5. Fast-forwards `release` to match `main`
-
-### After Release
-
-- Create a new `v0.3.x.md` for the next minor version
-- Copy the previous version as a template
+2. **During Release** (`/release`):
+   - Determines the version bump from conventional commit prefixes
+   - Bumps `package.json` version
+   - Renames `NEXT.md` → `v{new_version}.md`
+   - Adds version header, release date, and diff link
+   - Commits the version bump + finalized changelog
 
 ## Best Practices
 
 ### Do:
-- Update the changelog file **as you work** (not just before release)
-- Use clear, descriptive section headings
+- Update the changelog **as you work** via `/cam`
+- Use clear, descriptive entries
 - Group related changes together
-- Include technical details where helpful
 - Explain the "why" not just the "what"
-- Use emoji section headers for visual organization
 
 ### Don't:
-- Create a root `CHANGELOG.md` file
+- Create versioned changelog files manually (use `/release`)
+- Bump the version in `/cam` — only `/release` does that
 - Use vague descriptions like "various improvements"
-- Include internal implementation details users don't care about
 - Leave placeholder or TODO content
-- Change the version from `v0.2.x` to specific patch numbers during development
+
+## Maintenance
+
+### Updating Past Releases
+
+If you need to update a past release's changelog:
+
+1. Edit the `.changelog/v{version}.md` file
+2. Update the GitHub release manually:
+   ```bash
+   gh release edit v{version} --notes-file .changelog/v{version}.md
+   ```

.changelog/v0.9.0.md

@@ -0,0 +1,34 @@
+# Release v0.9.0
+
+Released: 2026-03-07
+
+## Added
+
+- Fan chart: progressive expansion from semi-circle to full circle as generations increase (paternal left, maternal right)
+- Fan chart: curved text along arcs (gen 1-3) and radial text (gen 4+) with auto-scaling to fit names without truncation
+- Fan chart: root person name auto-wraps into multiple lines to fit center circle
+- Fan chart: support up to 10 generations (was 6) with text at all depths visible on zoom
+- Production serving via PM2: `npm start` builds all packages then starts PM2
+- Express serves built client UI from `client/dist` with SPA catch-all routing
+- `scripts/dev-start.js` for clean PM2-based dev startup (replaces concurrently)
+- PM2 convenience scripts: `pm2:start`, `pm2:stop`, `pm2:restart`, `pm2:logs`, `pm2:status`
+- `dev:stop` script for stopping PM2 processes
+
+## Changed
+
+- `update.sh` uses local pm2 binary instead of requiring global install
+- `ecosystem.config.cjs` adds `log_date_format` and `max_memory_restart` to server app
+- pm2 added as devDependency (no longer requires global install)
+
+## Fixed
+
+- Fix memory leak in pathLongest BFS: reconstruct ancestors from parent chain instead of copying Sets per queue entry
+- Add error logging to silent `.catch()` handlers in sync.service.ts and sync.routes.ts
+- Extract magic numbers in requestTimeout.ts into named constants (LONG_TIMEOUT_MS, SHORT_TIMEOUT_MS)
+- Reconcile PLAN.md audit checklist with already-shipped fixes from PRs #39-43
+
+## Removed
+
+## Full Changelog
+
+**Full Diff**: https://github.com/atomantic/SparseTree/compare/v0.8.4...v0.9.0

.github/workflows/ci.yml

@@ -24,7 +24,7 @@ jobs:
       - uses: actions/checkout@v6
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
           cache: 'npm'
@@ -54,7 +54,7 @@ jobs:
       - uses: actions/checkout@v6
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
           cache: 'npm'
@@ -91,7 +91,7 @@ jobs:
       - uses: actions/checkout@v6
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
           cache: 'npm'
@@ -121,7 +121,7 @@ jobs:
       - uses: actions/checkout@v6
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
           cache: 'npm'

.github/workflows/release.yml

@@ -20,7 +20,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Use Node.js 20.x
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: 20.x
 

.github/workflows/validate-mocks.yml

@@ -15,7 +15,7 @@ jobs:
       - uses: actions/checkout@v6
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: '20'
           cache: 'npm'

CLAUDE.md

@@ -79,7 +79,8 @@ Layer 1: Raw Provider Cache → JSON files (data/person/*.json)
 - **release**: Push `main` to `release` to trigger GitHub Release workflow
 - **Push pattern**: `git pull --rebase --autostash && git push`
 - **Release**: `git push origin main:release`
-- **Changelog**: Update `.changelog/v{major}.{minor}.x.md` with changes
+- **Changelog**: `/cam` appends to `.changelog/NEXT.md`; `/release` finalizes it into a versioned file
+- **Versioning**: Version in `package.json` reflects the last release. Do not bump during development — `/release` handles version bumps
 - **Commit often**: After each feature or bug fix
 
 ## Code Guidelines