Skip to content

Add outcome visualization and fix interaction bugs #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lucbrinkman merged 5 commits into from
Nov 21, 2025
Merged

Add outcome visualization and fix interaction bugs #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8f7dd0c
Add outcome distribution visualization with interactive detail modal
lucbrinkman Nov 21, 2025
e90bc3e
Fix pre-commit hooks and apply code formatting
lucbrinkman Nov 21, 2025
22b933e
Fix font family and weight in outcome visualization components
lucbrinkman Nov 21, 2025
298da8e
Fix node dragging bug when scrolling during drag
lucbrinkman Nov 21, 2025
62b087e
Fix pin button hover flickering when node layout shifts
lucbrinkman Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file modified .husky/pre-commit
100644 → 100755
View file
Open in desktop
Empty file.
14 changes: 13 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,21 @@ Next.js application called "Map of AI Futures" - an interactive probability flow
- `npm run build` - Build for production
- `npm run lint` - Run ESLint

**Port Management:**

- **IMPORTANT:** Each worktree MUST use its designated port:
- **WorkTree1** (`ai-world-model-worktree-1`): Port **3000**
- **WorkTree2** (`ai-world-model-worktree-2`): Port **3001**
- **NEVER** start a dev server on a different port without explicit user permission
- **Before starting a dev server:**
1. Check which worktree you're in (from working directory)
2. Determine the correct port (3000 for WorkTree1, 3001 for WorkTree2)
3. Kill any process on that port: `fuser -k <port>/tcp`
4. Start dev server with: `npm run dev -- -p <port>` (e.g., `npm run dev -- -p 3001`)

**Process Management:**

- **To stop a dev server cleanly:** `fuser -k <port>/tcp` (e.g., `fuser -k 3000/tcp`)
- **To stop a dev server cleanly:** `fuser -k <port>/tcp` (e.g., `fuser -k 3000/tcp` or `fuser -k 3001/tcp`)
- This kills all processes using that port, including orphaned child processes
- More reliable than KillShell which can leave next-server processes running
- Prevents accumulation of zombie processes that consume CPU/memory
Expand Down
Loading