chore(deps): record why typescript 7 and @types/node 26 are held back

[kkdev92]

Dependabot opened both of these, I checked them, and both were closed rather than
merged. Without an ignore rule they return weekly and the reasoning gets
rediscovered every time — so it goes in the config, next to the decision.

typescript majors

typescript-eslint declares typescript >=4.8.4 <6.1.0. Type-aware linting is
what lint runs, so 7.x takes the lane down rather than degrading gracefully —
the closed PR's own lint job failed, which is the evidence rather than a
prediction. vscode-ext-kit has carried this same rule for the same reason.

@types/node majors

These types decide what Node API the code may compile against, so they must not
exceed the runtime. VS Code 1.132's extension host runs Node 24.18.0
(Electron 42.7.1) — measured by running the cached build under
ELECTRON_RUN_AS_NODE, not looked up — and engines.vscode: ^1.125.0 puts the
floor lower still.

Worth stating plainly: the bump passed every CI job. Nothing in the tree
reaches for a newer API yet, which is precisely why CI cannot be the thing that
catches this. It would surface at runtime, in a real extension host, the first
time someone used a Node 26 API. Same rule as @types/vscode, where the types
floor is also the ceiling.

Both comments say when to remove the rule

When typescript-eslint widens its peer range, and when the extension host
itself moves to a newer Node. An ignore with no exit condition is how a project
gets stuck.

Config-only change — no code, no version bump.

🤖 Generated with Claude Code