docs(handbook): rename the v2001.0.0 tree to v2001.0.1

[nerdalytics]

Description

Release 2001.0.1 shipped from #178. The handbook keeps one documentation tree per minor version and names it after the latest patch. Commit 50c213a set that rule when it removed the intermediate patch trees. The tree for the 2001.0 minor still had the name v2001.0.0, and the landing badges still pointed at the 2001.0.0 package. This PR renames the tree to v2001.0.1 and repoints every reference. No page content changes.

Changes Made

• git mv moves handbook/src/routes/v2001.0.0 to handbook/src/routes/v2001.0.1. Git records 17 of the page files as pure renames.
• versions.ts and navigation.ts name v2001.0.1 as latestSource, as the version entry and as the nav prefix.
• The /latest page glob and the /latest landing import point at the new directory, so /latest keeps serving the current tree without a copy.
• The root landing page and the version landing page show the 2001.0.1 npm and Socket badges. pkgVersion was the only value the landing badges read.
• The llms page examples use v2001.0.1 URLs so they resolve on the built site.
• handbook/AGENTS.md and HOOKS_TODO.md reference the new directory.
• Two strings keep 2001.0.0 on purpose. The hooks catalog keeps its ^2001.0.0 install range, and the migration page keeps its sentence about the bump to 2001.0.0, which describes the past.

Performance Impact

None. The change touches the documentation site only.

Test Coverage

• npm run check in handbook/: svelte-check reported 374 files, 0 errors and 0 warnings, and the service-worker tsc pass completed.
• BASE_PATH=/beacon npm run build in handbook/ wrote the site with a build/v2001.0.1/ directory and no v2001.0.0 directory.
• Root npm run check passed with no fixes.
• To verify after deploy, open /latest/state and /v2001.0.1/state on the site and confirm the version selector lists v2001.0.1. URLs under /v2001.0.0/ return the static 404 page, as the removed older patch trees do.

Related Issues

Follows #178.

Checklist

• Tests added/updated for changes
• Documentation updated
• All tests passing
• Code formatting checked
• Performance implications considered
• Breaking changes documented (if applicable)