claude: Update instructions for linting (use clippy)

Author: lutter

CLAUDE.md

@@ -24,6 +24,7 @@ Use unit tests for regular development and only run integration tests when:
 Unit tests are inlined with source code.
 
 **Prerequisites:**
+
 1. PostgreSQL running on localhost:5432 (with initialised `graph-test` database)
 2. IPFS running on localhost:5001
 3. PNPM
@@ -33,6 +34,7 @@ Unit tests are inlined with source code.
 The environment dependencies and environment setup are operated by the human.
 
 **Running Unit Tests:**
+
 ```bash
 # Run unit tests
 just test-unit
@@ -47,13 +49,15 @@ When filtering for specific tests, ensure the intended test name(s) appear in th
 ### Runner Tests (Integration Tests)
 
 **Prerequisites:**
+
 1. PostgreSQL running on localhost:5432 (with initialised `graph-test` database)
 2. IPFS running on localhost:5001
 3. PNPM
 4. Foundry (for smart contract compilation)
 5. Environment variable `THEGRAPH_STORE_POSTGRES_DIESEL_URL` set to `postgresql://graph:graph@127.0.0.1:5432/graph-test`
 
 **Running Runner Tests:**
+
 ```bash
 # Run runner tests.
 just test-runner
@@ -66,13 +70,15 @@ just test-runner block_handlers
 When filtering for specific tests, ensure the intended test name(s) appear in the output.
 
 **Important Notes:**
+
 - Runner tests take moderate time (10-20 seconds)
 - Tests automatically reset the database between runs
-- Some tests can pass without IPFS, but tests involving file data sources or substreams require it
+- Some tests can pass without IPFS, but tests involving file data sources require it
 
 ### Integration Tests
 
 **Prerequisites:**
+
 1. PostgreSQL running on localhost:3011 (with initialised `graph-node` database)
 2. IPFS running on localhost:3001
 3. Anvil running on localhost:3021
@@ -83,6 +89,7 @@ When filtering for specific tests, ensure the intended test name(s) appear in th
 The environment dependencies and environment setup are operated by the human.
 
 **Running Integration Tests:**
+
 ```bash
 # REQUIRED: Build graph-node binary before running integration tests
 just build
@@ -95,30 +102,34 @@ TEST_CASE=grafted just test-integration
 ```
 
 **⚠️ Test Verification Requirements:**
+
 - **ALWAYS verify tests actually ran** - Check the output for "test result: ok. X passed" where X > 0
 - **If output shows "0 passed" or "0 tests run"**, the TEST_CASE variable or filter was wrong - fix and re-run
 - **Never trust exit code 0 alone** - Cargo can exit successfully even when no tests matched your filter
 
 **Important Notes:**
+
 - Integration tests take significant time (several minutes)
 - Tests automatically reset the database between runs
 - Logs are written to `tests/integration-tests/graph-node.log`
 
 ### Code Quality
+
 ```bash
 # 🚨 MANDATORY: Format all code IMMEDIATELY after any .rs file edit
 just format
 
 # 🚨 MANDATORY: Check code for warnings and errors - MUST have zero warnings
-just check
+just lint
 
 # 🚨 MANDATORY: Check in release mode to catch linking/optimization issues that cargo check misses
 just check --release
 ```
 
 🚨 **CRITICAL REQUIREMENTS for ANY implementation**:
+
 - **🚨 MANDATORY**: `cargo fmt --all` MUST be run before any commit
-- **🚨 MANDATORY**: `cargo check` MUST show zero warnings before any commit
+- **🚨 MANDATORY**: `just lint` MUST show zero warnings before any commit
 - **🚨 MANDATORY**: `cargo check --release` MUST complete successfully before any commit
 - **🚨 MANDATORY**: The unit test suite MUST pass before any commit
 
@@ -127,6 +138,7 @@ Forgetting any of these means you failed to follow instructions. Before any comm
 ## High-Level Architecture
 
 ### Core Components
+
 - **`graph/`**: Core abstractions, traits, and shared types
 - **`node/`**: Main executable and CLI (graphman)
 - **`chain/`**: Blockchain-specific adapters (ethereum, near, substreams)
@@ -136,6 +148,7 @@ Forgetting any of these means you failed to follow instructions. Before any comm
 - **`server/`**: HTTP/WebSocket APIs
 
 ### Data Flow
+
 ```
 Blockchain → Chain Adapter → Block Stream → Trigger Processing → Runtime → Store → GraphQL API
 ```
@@ -148,13 +161,15 @@ Blockchain → Chain Adapter → Block Stream → Trigger Processing → Runtime
 6. **GraphQL** processes queries and returns results
 
 ### Key Abstractions
+
 - **`Blockchain`** trait: Core blockchain interface
 - **`Store`** trait: Storage abstraction with read/write variants
 - **`RuntimeHost`**: WASM execution environment
 - **`TriggerData`**: Standardized blockchain events
 - **`EventConsumer`/`EventProducer`**: Component communication
 
 ### Architecture Patterns
+
 - **Event-driven**: Components communicate through async streams and channels
 - **Trait-based**: Extensive use of traits for abstraction and modularity
 - **Async/await**: Tokio-based async runtime throughout
@@ -164,35 +179,42 @@ Blockchain → Chain Adapter → Block Stream → Trigger Processing → Runtime
 ## Development Guidelines
 
 ### Commit Convention
+
 Use format: `{crate-name}: {description}`
+
 - Single crate: `store: Support 'Or' filters`
 - Multiple crates: `core, graphql: Add event source to store`
 - All crates: `all: {description}`
 
 ### Git Workflow
+
 - Rebase on master (don't merge master into feature branch)
 - Keep commits logical and atomic
 - Squash commits to clean up history before merging
 
 ## Crate Structure
 
 ### Core Crates
+
 - **`graph`**: Shared types, traits, and utilities
 - **`node`**: Main binary and component wiring
 - **`core`**: Business logic and subgraph management
 
 ### Blockchain Integration
+
 - **`chain/ethereum`**: Ethereum chain support
 - **`chain/near`**: NEAR protocol support
 - **`chain/substreams`**: Substreams data source support
 
 ### Infrastructure
+
 - **`store/postgres`**: PostgreSQL storage implementation
 - **`runtime/wasm`**: WebAssembly runtime and host functions
 - **`graphql`**: Query processing and execution
 - **`server/`**: HTTP/WebSocket servers
 
 ### Key Dependencies
+
 - **`diesel`**: PostgreSQL ORM
 - **`tokio`**: Async runtime
 - **`tonic`**: gRPC framework
@@ -208,6 +230,7 @@ The repository includes a process-compose-flake setup that provides native, decl
 Currently, the human is required to operate the service dependencies as illustrated below.
 
 **Unit Tests:**
+
 ```bash
 # Human: Start PostgreSQL + IPFS for unit tests in a separate terminal
 # PostgreSQL: localhost:5432, IPFS: localhost:5001
@@ -218,6 +241,7 @@ just test-unit
 ```
 
 **Runner Tests:**
+
 ```bash
 # Human: Start PostgreSQL + IPFS for runner tests in a separate terminal
 # PostgreSQL: localhost:5432, IPFS: localhost:5001
@@ -228,6 +252,7 @@ just test-runner
 ```
 
 **Integration Tests:**
+
 ```bash
 # Human: Start all services for integration tests in a separate terminal
 # PostgreSQL: localhost:3011, IPFS: localhost:3001, Anvil: localhost:3021
@@ -243,18 +268,20 @@ just test-integration
 **Services Configuration:**
 The services are configured to use the test suite default ports for unit- and integration tests respectively.
 
-| Service | Unit Tests Port | Integration Tests Port | Database/Config |
-|---------|-----------------|------------------------|-----------------|
-| PostgreSQL | 5432 | 3011 | `graph-test` / `graph-node` |
-| IPFS | 5001 | 3001 | Data in `./.data/unit` or `./.data/integration` |
-| Anvil (Ethereum) | - | 3021 | Deterministic test chain |
+| Service          | Unit Tests Port | Integration Tests Port | Database/Config                                 |
+| ---------------- | --------------- | ---------------------- | ----------------------------------------------- |
+| PostgreSQL       | 5432            | 3011                   | `graph-test` / `graph-node`                     |
+| IPFS             | 5001            | 3001                   | Data in `./.data/unit` or `./.data/integration` |
+| Anvil (Ethereum) | -               | 3021                   | Deterministic test chain                        |
 
 **Service Configuration:**
 The setup combines built-in services-flake services with custom multiService modules:
 
 **Built-in Services:**
+
 - **PostgreSQL**: Uses services-flake's postgres service with a helper function (`mkPostgresConfig`) that provides graph-specific defaults including required extensions.
 
 **Custom Services** (located in `./nix`):
+
 - `ipfs.nix`: IPFS (kubo) with automatic initialization and configurable ports
 - `anvil.nix`: Ethereum test chain with deterministic configuration