Validate and update links (STF-557)

[oschwald]

Validated every link in the repo with the lychee link checker, fixed stale/redirecting links, and added a lychee config plus a Links CI workflow so future link rot is caught automatically.

CI setup

• lychee.toml with max_redirects = 0, fragment checking, MaxMind live/auth and XML-namespace excludes, and CHANGELOG.md / target / test fixtures excluded from scanning.
• .github/workflows/links.yml runs on push, PR, weekly cron, and manual dispatch.
• .lycheecache added to .gitignore.

Links updated (old -> new)

• https://dev.maxmind.com/geoip?lang=en -> https://dev.maxmind.com/geoip/?lang=en (pom.xml)
• https://www.maxmind.com/ -> https://www.maxmind.com/en/home (pom.xml)
• https://dev.maxmind.com/geoip/docs/web-services -> .../web-services/ (CLAUDE.md)
• https://dev.maxmind.com/geoip/docs/web-services?lang=en -> .../web-services/?lang=en (README.md, CityResponse.java, CountryResponse.java, InsightsResponse.java, WebServiceClient.java)
• https://dev.maxmind.com/geoip/docs/databases?lang=en -> .../databases/?lang=en (README.md)
• https://www.maxmind.com/en/correction -> https://www.maxmind.com/en/geoip-data-correction-request (README.md)
• https://www.maxmind.com/en/support -> https://support.maxmind.com/knowledge-base (README.md)

Each replacement was resolved with curl and confirmed to be a clean 200 with no further redirect.

Historical CHANGELOG.md entries are intentionally left unchanged (and excluded from scanning).

lychee ends green: 🔍 44 Total ✅ 37 OK 🚫 0 Errors 👻 7 Excluded.

Part of STF-557.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request configures the Lychee link checker by adding a lychee.toml configuration file and updating .gitignore to ignore .lycheecache. It also updates various documentation, POM, and Javadoc URLs to their canonical forms (such as adding trailing slashes or updating redirected paths). The review feedback recommends removing the 500..=599 HTTP status code range from the Lychee configuration's accepted list to prevent masking server-side failures and broken links.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Accepting HTTP status codes in the 500..=599 range (Server Errors) can mask actual broken links or server misconfigurations. While transient server errors can occasionally occur, permanently broken links returning 500 errors will be ignored, defeating the purpose of automated link checking. It is recommended to remove 500..=599 from the accept list so that server-side failures are surfaced.

Suggested change

	accept = ["100..=103", "200..=299", "403", "429", "500..=599", "999"]
	accept = ["100..=103", "200..=299", "403", "429", "999"]

[oschwald]

Keeping 500..=599 in accept, matching the dev-site and blog-site configs — transient upstream 5xx shouldn't fail link-checking CI.

— Claude (posted on Greg's behalf)