CLAUDE: add details and adjust directions for dev workflow

- Linting takes a while, so stop recommending it before every commit.
- Add information on optimizer and schemachanger packages.
- Mention bazel file generation.

Release note: None

Author: rafiss

CLAUDE.md

@@ -29,7 +29,7 @@ CockroachDB is a distributed SQL database written in Go, built with Bazel and ma
 ./dev test pkg/sql --stress          # Run repeatedly until failure
 ./dev testlogic                      # Run all SQL logic tests
 ./dev testlogic ccl                  # Run enterprise logic tests
-./dev testlogic --files='prepare|fk' # Run specific test files
+./dev testlogic base --config=local --files='prepare|fk' # Run specific test files under a specific configuration
 ```
 
 Note that when filtering tests via `-f` to include the `-v` flag which
@@ -40,8 +40,10 @@ for `testing: warning: no tests to run` in the output.
 ```bash
 ./dev generate            # Generate all code (protobuf, parsers, etc.)
 ./dev generate go         # Generate Go code only
-./dev lint                # Run all linters
-./dev lint --short        # Run fast subset of linters
+./dev generate bazel      # Update BUILD.bazel files when dependencies change
+./dev generate protobuf   # Generate files based on protocol buffer definitions
+./dev lint                # Run all linters (only run this when requested)
+./dev lint --short        # Run fast subset of linters (only run this when requested)
 ```
 
 ### Architecture Overview
@@ -67,20 +69,21 @@ SQL Layer (pkg/sql/) → Distributed KV (pkg/kv/) → Storage (pkg/storage/)
 
 ### Development Workflow
 
-1. **Environment Setup**: Run `./dev doctor` to ensure all dependencies are installed
-2. **Building**: Use `./dev build short` for iterative development, `./dev build cockroach` for full builds
-3. **Testing**: Run package-specific tests with `./dev test pkg/[package]` 
-4. **Code Generation**: After schema/proto changes, run `./dev generate go`
-5. **Quality Checks**: Run `./dev lint` before committing
+1. **Environment Setup**: Run `./dev doctor` to ensure all dependencies are installed.
+2. **Building**: Use `./dev build short` for iterative development, `./dev build cockroach` for full builds.
+3. **Testing**: Run package-specific tests with `./dev test pkg/[package]`.
+4. **Code Generation**: After schema/proto changes, run `./dev generate go`.
+5. **Linting**: Run with `./dev lint` or `./dev lint --short`. This takes a while, so no need to run it regularly.
 
 ### Testing Strategy
 
 CockroachDB has comprehensive testing infrastructure:
-- **Unit Tests**: Standard Go tests throughout `/pkg/` packages
-- **Logic Tests**: SQL correctness tests using `./dev testlogic`
-- **Roachtests**: Distributed system integration tests
-- **Acceptance Tests**: End-to-end testing in `/pkg/acceptance/`
-- **Stress Testing**: Continuous testing with `--stress` flag
+- **Unit Tests**: Standard Go tests throughout `/pkg/` packages.
+- **Logic Tests**: SQL correctness tests using `./dev testlogic`.
+- **Roachtests**: Distributed system integration tests.
+- **Acceptance Tests**: End-to-end testing in `/pkg/acceptance/`.
+- **Stress Testing**: Continuous testing with `--stress` flag.
+
 
 ### Build System
 
@@ -93,6 +96,8 @@ CockroachDB has comprehensive testing infrastructure:
 
 **Package Structure:**
 - `/pkg/sql/` - SQL layer (parser, optimizer, executor)
+- `/pkg/sql/opt` - Query optimizer and planner
+- `/pkg/sql/schemachanger` - Declarative schema changer
 - `/pkg/kv/` - Key-value layer and transaction management
 - `/pkg/storage/` - Storage engine interface
 - `/pkg/server/` - Node and cluster management