Comments Test Doc

A throwaway, non-confidential document used to verify the section-level commenting system end to end. No client or cost data appears anywhere on this page.

Introduction

This section exists so a reader can leave a comment anchored to it. The comment dot appears on hover at the end of the heading, and clicking it opens the panel pre-anchored to this section.

The commenting system is built on a Cloudflare Worker backed by D1. Readers comment without logging in; Bob pulls the comments back as structured JSON, edits the source, redeploys, and resolves.

Onboarding flow

A second section to test multiple anchors. Reordering this section relative to others should NOT orphan comments, because heading IDs are now hash-stable rather than positional.

A nested subsection

An h3 under Onboarding flow, to confirm h3 headings also get comment dots and anchors.

Architecture

The Worker exposes a small REST surface. Readers use a per-doc HMAC token; Bob uses a separate bearer token with read + resolve powers across all docs.

Duplicate Heading

This heading text is intentionally repeated below to test stable-ID disambiguation.

Duplicate Heading

The second occurrence of the same heading text must get a distinct, text-hash-based ID — not a positional -2 that shifts when sections move.

Conclusion

If you can comment on each section above, see the count badges update, edit a comment, and the document still reads perfectly with the backend offline, Phase 1 works.