Switch CI and docs to Bun so the lockfile can't drift again

This PR's dependency bump updated bun.lock but not
package-lock.json, so npm ci failed on a manifest/lockfile mismatch
and CI never ran. The repo only ever used bun.lock in practice — bun
was already the working package manager, npm was vestigial and had
already drifted once. Rather than regenerate a second lockfile that
can drift the same way next time, drop it and standardize CI, README,
CONTRIBUTING, and the PR template on Bun.

Verified locally: bun install --frozen-lockfile, bun run lint,
bun run test (161 passed), and bun run build all pass. Note bun test
invokes Bun's own test runner, not Vitest, so docs use `bun run test`
to hit the actual package.json script.

Refs #13

Author: euxaristia

.github/PULL_REQUEST_TEMPLATE.md

@@ -24,8 +24,8 @@
 
 ## Checklist
 
-- [ ] `npm run lint` passes
-- [ ] `npm test` passes
-- [ ] `npm run build` passes (includes typecheck)
+- [ ] `bun run lint` passes
+- [ ] `bun run test` passes
+- [ ] `bun run build` passes (includes typecheck)
 - [ ] New logic in `src/lib/` has colocated unit tests
 - [ ] I kept the change focused on a single concern

.github/workflows/ci.yml

@@ -11,19 +11,18 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - uses: actions/setup-node@v4
+      - uses: oven-sh/setup-bun@v2
         with:
-          node-version: 22
-          cache: npm
+          bun-version: latest
 
       - name: Install dependencies
-        run: npm ci
+        run: bun install --frozen-lockfile
 
       - name: Lint
-        run: npm run lint
+        run: bun run lint
 
       - name: Test
-        run: npm test
+        run: bun run test
 
       - name: Build
-        run: npm run build
+        run: bun run build

CONTRIBUTING.md

@@ -9,11 +9,11 @@ the conventions the codebase follows, and what to expect from the review process
 2. Install dependencies and start the dev server:
 
    ```sh
-   npm install
-   npm run dev
+   bun install
+   bun run dev
    ```
 
-   Requires Node.js 20+. The dev server proxies API calls to
+   Requires [Bun](https://bun.sh) 1.1+. The dev server proxies API calls to
    `https://node.gitlawb.com` — no backend setup needed.
 
 3. Create a branch off `main` for your change:
@@ -27,12 +27,12 @@ the conventions the codebase follows, and what to expect from the review process
 Run the full check suite locally — CI runs the same three commands:
 
 ```sh
-npm run lint
-npm test
-npm run build
+bun run lint
+bun run test
+bun run build
 ```
 
-All three must pass. `npm run build` includes the TypeScript project build
+All three must pass. `bun run build` includes the TypeScript project build
 (`tsc -b`), so type errors fail there.
 
 ### Editing the security headers

README.md

@@ -23,13 +23,13 @@ push events, straight from the node's REST API.
 
 ## Quick start
 
-Requires Node.js 20+.
+Requires [Bun](https://bun.sh) 1.1+.
 
 ```sh
 git clone https://github.com/Gitlawb/node-explorer.git
 cd node-explorer
-npm install
-npm run dev
+bun install
+bun run dev
 ```
 
 The dev server proxies `/api/*` and `/node-info` to `https://node.gitlawb.com`
@@ -41,12 +41,12 @@ through a same-origin proxy. To point at a different node, change the proxy
 
 | Command | What it does |
 | --- | --- |
-| `npm run dev` | Vite dev server with API proxy |
-| `npm run build` | Typecheck (`tsc -b`) + production build |
-| `npm test` | Run the unit test suite once (Vitest) |
-| `npm run test:watch` | Vitest in watch mode |
-| `npm run lint` | ESLint |
-| `npm run preview` | Serve the production build locally |
+| `bun run dev` | Vite dev server with API proxy |
+| `bun run build` | Typecheck (`tsc -b`) + production build |
+| `bun run test` | Run the unit test suite once (Vitest) |
+| `bun run test:watch` | Vitest in watch mode |
+| `bun run lint` | ESLint |
+| `bun run preview` | Serve the production build locally |
 
 ## Data source
 
@@ -67,7 +67,7 @@ opt-in via an env flag (older nodes silently ignore unknown params, which would
 search appear to return everything):
 
 ```sh
-VITE_SERVER_SEARCH=true npm run dev
+VITE_SERVER_SEARCH=true bun run dev
 ```
 
 Until the flag is on, search and sort apply to the currently loaded page and the UI
@@ -99,8 +99,8 @@ parsing, language detection, API mapping/classification, TOC extraction) is cove
 network functions are tested against a stubbed `fetch`.
 
 ```sh
-npm test              # single run
-npm run test:watch    # watch mode
+bun run test          # single run
+bun run test:watch    # watch mode
 ```
 
 Tests live next to the modules they cover (`src/lib/foo.ts` → `src/lib/foo.test.ts`).