Document storage tuning, thread debugging, MQTT durable sessions, analytics config

[kriszyp]

Summary

Fills in documentation gaps identified by reviewing harper-pro/core against the reference docs. Adds two new reference pages and expands four existing sections so user-facing capabilities that previously lived only in config-root.schema.json or release notes are now properly documented.

What changed

New pages

• reference/database/storage-tuning.md — deep dive on storage.* for production tuning: writeAsync durability tradeoffs, compression dictionary/threshold, multi-path blobPaths, prefetchWrites/noReadAhead/pageSize/caching, maxTransactionQueueTime, and the full storage.reclamation.* reference (threshold, interval, evictionFactor) plus workload recipes.
• reference/configuration/debugging.md — threads.debug.* (port, startingPort, host, waitForDebugger), Chrome DevTools + VS Code attach instructions, SSH-tunneled remote debugging, and an expanded threads.heapSnapshotNearLimit section.

Expanded sections

• reference/mqtt/overview.md — new Durable Sessions section (cleanStart/sessionExpiryInterval, hdb_durable_session storage, audit-log catch-up, per-node scope) and a note on hdb_session_will for Last Will durability. Also fixes a duplicate ### Last Will heading.
• reference/analytics/overview.md — full analytics.* config reference, including the previously undocumented storageInterval, plus replicate, logging, and aggregatePeriod.
• reference/configuration/options.md — annotated threads.heapSnapshotNearLimit and threads.debug, expanded storage.reclamation.* with per-property defaults, added analytics.storageInterval and analytics.logging, linked the storage section to the new Storage Tuning page.
• reference/configuration/overview.md and reference/database/overview.md — cross-links to the new pages.
• sidebarsReference.ts — registered both new pages.

Why

A review of public-facing surfaces in harper-pro/core against the docs surfaced several config keys, behaviors, and APIs that were either schema-only (storage.reclamation.*, analytics.storageInterval, threads.debug.* sub-options) or present in code but missing user-facing guidance (MQTT durable sessions, blob-path strategies, write durability tradeoffs). The features are user-visible and operationally important, so documenting them reduces the gap between schema knowledge and what an operator can reasonably do without reading source.

Test plan

• npm run build succeeds locally — only pre-existing broken-anchor warning unrelated to this change
• Spot-check rendered pages on preview: Database → Storage Tuning, Configuration → Worker Thread Debugging, MQTT → Durable Sessions section, Analytics → Configuration section
• Verify sidebar entries appear under Database and Configuration categories

🤖 Generated with Claude Code

[github-actions]

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-489

This preview will update automatically when you push new commits.

[Ethan-Arrowood]

Generally lgtm with a minor nit.

Also don't forget to format!

[Ethan-Arrowood]

Suggested change

	Type: `number` (seconds)  •  Default: `60`
	Type: `number` (seconds) - Default: `60`

Not going to block on this, but this whole double space and special dot character (at least its not on my keyboard) seems extra. Most of the docs use regular characters like - here.

[Ethan-Arrowood]

Is `duration string` accurate here? It should it be `string` (duration)