fork-workflowlisted

# ClankerMux development workflow The repo (`d4rken/better-ccflare` on GitHub) began as a fork of `tombii/better-ccflare`, but it has diverged far enough — and intentionally removed things upstream won't take — that **ClankerMux is now its own project**. Treat it as such. ## The one lane: fork-only | Aspect | Value | |---|---| | Branch prefix | `fix/*`, `feat/*`, or `fork/*` (any is fine; they're all fork-only) | | Base branch | `origin/main` — never `upstream/main` | | PR upstream? | No. We don't contribute to `tombii/better-ccflare`. | | Merge style | `--no-ff` into `main` (the merge commit is the undo handle) | ## Making a change Branch-creating steps move HEAD, so they happen **in a worktree** — never in the live checkout. See the live-checkout section of `CLAUDE.md`. ```bash # 1. Worktree off origin/main (EnterWorktree in Claude Code, or:) git worktree add .claude/worktrees/<name> -b fix/<name> origin/main # 2. Code the fix and tests. Write tests first for new functionality. # 3. Verify — mandatory. `lint` rewrites files (biome check --write --unsafe), # so typecheck must run after it. No trailing `format`: check already formats. bun run lint && bun run typecheck # 4. Commit with a recognized prefix git add <specific files> # never `git add .` git commit -m "fix: <subject>" # 5. Bump the app version in the root package.json (see below) # 6. Merge into main. This IS allowed in the live checkout — it advances main # in place rather than switchin