[Bug] docs @types/node is 26 on a Node 24 toolchain — track the engines floor in every Bun-installed manifest, with the ignore rule and a guard

[pathosDev]

#1601 took /docs' @types/node from ^24.13.3 to ^26.6.1, and the Dependabot config let it through on purpose: "No @types/node rule here: TypeDoc compiles ../src with the root tsconfig, so the root's pin is the one that guards the library, and the copy in this manifest only types the site's own scripts." That reasoning is correct about the library — the root gate compiles against 24 whatever the docs install — and still lands the docs on types for a Node the docs never run on: docs-checks.yml and docs.yml set up Node 24, engines.node is >=24, and types newer than the runtime are the wrong direction for the only thing that copy types.

Maintainer's call after review: one Node story. @types/node tracks the engines floor in every Bun-installed manifest that declares it, and every such entry carries the same ignore rule, so the manifest and the rule move together when the floor is raised.

Proposed

• /docs: @types/node back to ^24.13.3, bun.lock regenerated (stamp stays 1).
• The /docs Dependabot entry gets the root's @types/node semver-major ignore, and its paragraph says why the exemption was withdrawn.
• A guard: for every Bun-installed manifest that declares @types/node, the declared major equals the engines.node floor, and the Dependabot entry for that directory ignores @types/node majors. Nothing under tests/ pinned any of this; chore(deps-dev): Bump @types/node from 24.13.3 to 26.6.1 in /docs #1601 merged green.

The two Next example frontends carry @types/node 26 as of #1611 (they were on 22 before, so they were never part of this story); npm-installed demo apps, out of scope here — a follow-up if wanted.

[pathosDev]

Scope widened on request: the two Next example frontends follow the same line — @types/node back to ^24.13.3 (both lockfiles regenerated, agreeing on 24.13.6), the npm entry carries the semver-major ignore, and TypesNodeFloor.test.ts reads the npm entry's directories: list too, so the frontends are in the same story as the root and /docs. Verified red against the previous state on both the manifests and the missing rule; npm ci + npm run build pass in both directories.