chore: in-range dependency refresh + lint fix after eslint update

npm update within existing semver ranges (no range changes):
- @modelcontextprotocol/sdk 1.26.0 -> 1.32.1
- @typescript-eslint/* 8.38.0 -> 8.71.2
- @types/node 24.0.3 -> 24.19.2
- dotenv 16.5.0 -> 16.6.1
- graphql 16.11.0 -> 16.14.2
- graphql-request 7.2.0 -> 7.4.0
- graphql-tag 2.12.6 -> 2.12.7
- typescript 5.8.3 -> 5.9.3
- zod 3.25.67 -> 3.25.76
- ts-jest 29.4.0 -> 29.4.15
- @graphql-codegen/typescript-graphql-request 6.3.0 -> 6.4.0

All majors left untouched (12):
- eslint 8 -> 10 (+ @typescript-eslint, flat-config cascade)
- typescript 5.9 -> 7 (gated by the eslint chain)
- jest 29 -> 30 and @types/jest 29 -> 30 (coupled)
- @graphql-codegen/* 5/4 -> 7/6 (codegen.yml schema churn)
- zod 3 -> 4 (MCP tool schema APIs)
- graphql 16 -> 17 (deprecated APIs removed)
- dotenv 16 -> 18 (prod dep)
- @types/node 24 -> 26 (types only, Node-coupled)

@modelcontextprotocol/sdk already latest within ^1.12.3.
lint + build + tests green.

src/wikijs/index.ts

@@ -147,7 +147,7 @@ export class WikiJSClient {
     // Fetch existing page to avoid clobbering fields the caller did not supply.
     let existing: Record<string, unknown> | null = null;
     try {
-      existing = (await this.getPageById(params.id)) as Record<string, unknown> | null;
+      existing = await this.getPageById(params.id);
     } catch {
       existing = null;
     }