Merge branch 'main' into claude/fix-mcpc-timeout-YImuH

Author: jancurn

.github/workflows/ci.yml

@@ -35,14 +35,14 @@ jobs:
       - name: Unit tests
         run: npm run test:unit
 
-  e2e:
-    name: E2E tests
+  e2e-node:
+    name: E2E tests (Node.js)
     runs-on: ubuntu-latest
 
     steps:
       - uses: actions/checkout@v6
 
-      - name: Set up Node.js 22
+      - name: Set up Node.js 24
         uses: actions/setup-node@v6
         with:
           node-version: 24
@@ -54,13 +54,35 @@ jobs:
       - name: Build
         run: npm run build
 
-      - name: Install Bun
-        uses: oven-sh/setup-bun@v2
-
       - name: E2E tests
         # Run without gnome-keyring: @napi-rs/keyring fails fast when no D-Bus secret
         # service is available, and keychain.ts automatically falls back to encrypted
         # file storage (~/.mcpc/credentials.json, mode 0600).  The keychain code paths
         # are covered by unit tests; e2e tests only need credentials to work, not a
         # specific storage backend.
         run: ./test/e2e/run.sh --no-build --parallel 4
+
+  e2e-bun:
+    name: E2E tests (Bun)
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Set up Node.js 24
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          cache: npm
+
+      - name: Install Bun
+        uses: oven-sh/setup-bun@v2
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build
+
+      - name: E2E tests
+        run: ./test/e2e/run.sh --no-build --runtime bun --parallel 4

CLAUDE.md

@@ -517,6 +517,11 @@ Example: `mcpc @apify logging-set-level debug`
 
 ## Common Implementation Patterns
 
+After making any code changes, always run `npm run lint` and fix all errors before finishing. The lint command checks both ESLint rules and
+Prettier formatting; run `npx prettier --write` on any files flagged for formatting issues or `npm run lint` to fix the entire repo.
+
+For any non-trivial change (new feature, bug fix, behaviour change, or notable refactor), add an entry to the `[Unreleased]` section of `CHANGELOG.md` before finishing. Use the appropriate category (`Added`, `Changed`, `Fixed`, `Removed`). Skip purely internal changes such as test-only edits or code style fixes.
+
 When implementing features:
 
 1. **Keep core runtime-agnostic** - Use native APIs, avoid runtime-specific dependencies