fix(entries): preserve merged timeline pagination

[arapov]

Summary

• preserve upstream Link rel=next when list_party_entries includeLinkedPersons returns an exactly-full merged page
• fetch enough entries per party to cover the requested merged window, up to Capsule's per-party 100 cap
• align the new timeline probe/docs with the v1.7.0 minor-release line and refresh the test count

Review notes

• No security blockers found in the changed HTTP landing page, explicit MCP annotations, or linked-person timeline path.
• npm outdated reports only @biomejs/biome 2.4.15 -> 2.4.16; left out of this scoped fix as a non-blocking dev-tool patch.
• package.json/serverInfo still report 1.6.5; bump to 1.7.0 during the release cut.

Verification

• npm test -- tests/entries.test.ts tests/tool-annotations.test.ts tests/http-app.test.ts tests/mcp-integration.test.ts
• npm test
• npm run typecheck
• npm run lint
• npm run format:check
• npm run build
• npm audit --audit-level=low
• npm outdated --json
• npm install --package-lock-only --ignore-scripts
• npm view capsulemcp dist-tags version versions --json --cache /private/tmp/capsulemcp-npm-cache
• npm pack --dry-run --json --cache /private/tmp/capsulemcp-npm-cache
• npm publish --dry-run --tag latest --cache /private/tmp/capsulemcp-npm-cache
• git diff --check HEAD

[arapov]

Cherry-picked the substantive pagination fix (entries.ts + tests) into #64, which targets current master. Dropped this PR's v1.6.6→v1.7.0 doc rewrites and the wire-trace-v166.ts→v170.ts rename: the probe scripts are iteration markers (v163–v167), not release versions, and renaming only v166 would break the sequence + the NOTES §32 references. Your semver point (next release is a minor bump for the new tools) is correct and noted for the release cut. Thanks for catching the page>1 under-fetch + the exactly-full-page-1 nextPage bug — both were real. Closing in favour of #64.