docs: keep maintainers' private workflow out of the agent instructions

.claude/commands/implement-pattern.md

@@ -23,7 +23,7 @@ Read `packages/eslint-effect/EFFECT_PATTERNS_TODO.md` and select the next unchec
 
 **CRITICAL:** Before implementing, verify your understanding of the pattern:
 
-1. **Check Effect source code** at `~/Development/effect/` to understand:
+1. **Check Effect source code** in the [Effect repository](https://github.com/Effect-TS/effect) to understand:
    - How the simplified function works
    - Its type signature and behavior
    - Edge cases and constraints

CLAUDE.md

@@ -20,51 +20,23 @@ eventsourcing is a set of event sourcing libraries for TypeScript, built on Effe
 
 An agent may decline an ask that falls outside this remit, and should say which owner above the ask belongs to.
 
-# 🚨 CRITICAL GIT WORKTREE WORKFLOW - DO THIS FIRST! 🚨
+## Setup
 
-**BEFORE ANY CODE CHANGES - USE WORKTREES:**
+Tool versions are pinned in the mise config. Run `mise install`, then `bun install`. Use Bun, not node or npm.
 
-1. Run `git fetch origin main` to get latest from remote
-2. Create worktree for new feature: `git worktree add worktrees/descriptive-name -b feat/descriptive-name`
-3. Change to the new worktree: `cd worktrees/descriptive-name`
-4. Run `mise trust && mise install` to make tools available
-5. Run `bun install` to set up dependencies
-6. ONLY THEN start making changes in the isolated worktree
+## Building and testing
 
-- Always use turbo to run tasks.
-- Always use Bun instead of node or npm.
-- PR titles must follow conventional commits
+Run every task through turbo:
 
-## Worktree Structure
+- `turbo all` runs the build, lint, tests and repository checks that CI runs. It must pass before a change is ready.
+- `turbo test --filter=<package>` runs one package's tests.
+- The PostgreSQL store's tests need the database from `docker-compose up -d`. The `TEST_PG_*` variables in `.mise.toml` point at it.
 
-```
-eventsourcing/            <- Repo root (main branch checkout)
-├── .git/                <- Git directory
-├── worktrees/           <- All feature worktrees go here
-│   ├── feature-name-1/  <- Feature worktree
-│   └── feature-name-2/  <- Another feature worktree
-├── packages/            <- Source code
-└── ...
-```
+The `eslint-effect` lint rules and the Effect language service enforce the Effect conventions a change must follow. `bun install` patches the language service into TypeScript. Fix what they report rather than disabling them.
 
-## Worktree Benefits
+## Contributing
 
-- Each feature branch gets its own isolated working directory
-- Never risk contaminating main branch with uncommitted changes
-- Can work on multiple features simultaneously in parallel worktrees
-- Clean separation between repo root and feature development
-
-## Before Starting Work
-
-- ALWAYS use `/start` command to create proper worktree setup
-- Choose a short worktree name based on the work description (worktrees live in worktrees/ subdirectory)
-- NEVER work directly in repo root for feature development - always use a worktree
-- Verify you're in correct worktree with `pwd` and `git branch`
-- Each worktree is a complete working copy with its own node_modules and mise config
-
-## Releasing
-
-- Start each new piece of work in a new branch from the latest origin/main. Changes are always submitted via a PR.
-- With each commit, review and update pending changesets accordingly.
-- Changesets must be written with the package consumer in mind, telling them what they need to know about changes, not just what changed.
-- Packages are released manually via GitHub UI, not automatically.
+- Branch from the latest `main` and submit every change as a pull request.
+- Write the pull request title as a conventional commit.
+- Add or update a changeset in `.changeset/` for any change to a published package. Write it for the package's consumer: say what they need to know, not just what changed.
+- Packages are released by hand from the GitHub UI, not automatically.

docs/plans/2025-10-25-effect-language-service-integration-design.md

@@ -2,11 +2,10 @@
 
 **Date:** 2025-10-25
 **Status:** Approved
-**Related Issue:** hp-1
 
 ## Overview
 
-This design integrates the Effect Language Service CLI into the brownsauce monorepo to provide compile-time diagnostics for Effect-specific issues. The integration enables TypeScript's compiler to catch Effect problems (floating Effects, incorrect yield usage, missing service dependencies) during normal type-checking, with hard enforcement that fails builds on violations.
+This design integrates the Effect Language Service CLI into this monorepo to provide compile-time diagnostics for Effect-specific issues. The integration enables TypeScript's compiler to catch Effect problems (floating Effects, incorrect yield usage, missing service dependencies) during normal type-checking, with hard enforcement that fails builds on violations.
 
 ## Goals
 
@@ -187,4 +186,3 @@ High-level steps:
 
 - Effect Language Service: https://effect.website/docs/other/language-service
 - Current devDependency version: `@effect/language-service@0.47.1`
-- Related Beads issue: hp-1