26-Jun-2026 — resolve type errors from express 4 types and PDFParse buffer

build 721 — commit 19419c7

Express types pinned to v4

@types/express was resolving transitively (via @types/multer and @types/passport*) to v5, which dragged in @types/express-serve-static-core v5. The v5 types model Express 5 wildcard routes and so type req.params values as string | string[], producing 63 type errors across route and controller handlers even though the runtime is express 4.18.2.

Pin the express types back to v4 with an overrides block so they match the runtime. No application code changes; clears all 63 string | string[] errors plus a related string[]-as-index error.

PDFParse buffer

Node 24 types Buffer as Uint8Array<ArrayBufferLike>, which is not assignable to the pdf-parse data field's TypedArray union, causing two type errors. Pass a plain Uint8Array view over the buffer (honouring its pooled byteOffset/byteLength) so there is no data copy and the types match.