v0.2.4: Non-existent-iD handling, start cap, and a resource leak fix

Non-existent-iD handling, start cap, and a resource leak fix

Three handler fixes for ORCID edge cases, plus dev-dependency bumps.

Fixed:

• orcid_get_research_resources throws profile_not_found for non-existent iDs — the /research-resources endpoint returns HTTP 200 {"group":[]} (not 404), so the empty path now verifies existence via getPerson. (#11)
• orcid_search_researchers caps start at 10,000, so Zod rejects out-of-range values before the ORCID Public API returns its HTTP 400. (#12)
• orcid://researcher/{orcid_id}/profile no longer leaks the upstream ORCID URL or raw 404 error body — the resource handler catches the upstream NotFound and rethrows a clean error. (#13)

Changed:

• @types/node ^25.9.3 → ^25.9.4
• vitest ^4.1.8 → ^4.1.9

234 tests pass; bun run devcheck clean.