chore: standardize on npm, remove yarn.lock

CI and local dev used yarn (yarn.lock) while the Dockerfile used
npm ci (package-lock.json). The two lock files had 57 version
mismatches. Standardize on npm everywhere:

- Remove yarn.lock
- Regenerate package-lock.json from clean npm install
- CI: yarn install -> npm ci, yarn build -> npm run build
- docker-compose: ["yarn", "process"] -> ["npm", "run", "process"]
- Docs and scripts: yarn -> npm run

Fixes: #220

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: sameh-farouk

.github/workflows/CI.yml

@@ -14,9 +14,8 @@ jobs:
         uses: actions/setup-node@v3
         with:
           node-version: 20
-          cache: "yarn"
-          cache-dependency-path: "**/yarn.lock"
+          cache: "npm"
       - name: Install dependencies
-        run: yarn install
+        run: npm ci
       - name: Build
-        run: yarn build
+        run: npm run build

README.md

@@ -39,7 +39,7 @@ See [docs](./docs/readme.md)
     - [development.md](./docs/development.md) - Local development setup
     - [production.md](./docs/production.md) - Production deployment
     - [release_process.md](./docs/release_process.md) - Release workflow
-- `schema.graphql` - GraphQL schema — changes here regenerate `src/model/` via `yarn codegen`
+- `schema.graphql` - GraphQL schema — changes here regenerate `src/model/` via `npm run codegen`
 - `Makefile` - Common tasks: `typegen`, `typegen-add`, `typegen-seed`, `version-bump`
 - `processor-chart/` - Helm chart for processor + query node deployment
 - `indexer/chart/` - Helm chart for indexer stack deployment

docker-compose.yml

@@ -32,7 +32,7 @@ services:
       - TYPEORM_LOGGING=error
     ports:
       - 44233:44233
-    command: ["yarn", "process"]
+    command: ["npm", "run", "process"]
 
   query-node:
     image: ghcr.io/threefoldtech/tfchain_graphql_query-node:latest

docs/development.md

@@ -3,8 +3,8 @@
 ## Install
 
 ```bash
-yarn
-yarn build
+npm install
+npm run build
 ```
 
 ## Local Network
@@ -55,9 +55,9 @@ INDEXER_ENDPOINT_URL=http://localhost:8888/graphql
 Start the local PostgreSQL container and run the processor:
 
 ```bash
-yarn build
-yarn db:up
-yarn process
+npm run build
+npm run db:up
+npm run process
 ```
 
 You should see TFChain blocks being processed by the processor:
@@ -79,7 +79,7 @@ At this step, running `docker ps` should show the indexer containers running:
 Start the query node:
 
 ```bash
-yarn api
+npm run api
 ```
 
 Now you can use the GraphQL playground at http://localhost:4000/graphql
@@ -93,7 +93,7 @@ When TFChain has a new spec version with type changes, see [typeChanges.md](./ty
 make typegen-add
 
 # Check what changed in src/types/, add handler branches if needed
-yarn build
+npm run build
 ```
 
 ## Modifying the GraphQL Schema
@@ -103,17 +103,17 @@ If you need to add new entities or fields to the GraphQL API:
 1. Edit `schema.graphql`
 2. Regenerate models and create a migration:
    ```bash
-   yarn codegen
-   yarn build
-   yarn db:create-migration
+   npm run codegen
+   npm run build
+   npm run db:create-migration
    ```
 3. Add or update event handlers in `src/mappings/`
 4. Register new events in `src/processor.ts` if needed
 5. Test locally:
    ```bash
-   yarn db:up
-   yarn db:migrate
-   yarn process
+   npm run db:up
+   npm run db:migrate
+   npm run process
    ```
 
 ## Resetting the Processor Database
@@ -137,7 +137,7 @@ docker compose up -d
 
 ```bash
 ./scripts/reset-db.sh
-yarn process
+npm run process
 ```
 
 ## Debugging