Fix leaked Google Docs comment markers on the clusters page#826
Merged
Conversation
Six cluster/sub-cluster descriptions on the live clusters page showed literal bracket artifacts like "process:[ag][ah]" and "feedback[ai][aj], have received". Root cause: parse_clusters_to_sheet.py fetches the source Google Doc via its plain-text export (docs.google.com/.../export?format=txt), and Google Docs' plain-text export represents unresolved inline comments as bracketed reference codes (a, b, ... aa, ab, ...) inserted directly into the body text at the comment's anchor point. The script already had an extract_annotations() helper for exactly this pattern (built for citation/publication text and sub-cluster ToC names), but the code paths that build cluster- and sub-cluster-level *description* text appended the raw, uncleaned line instead - five call sites across parse_cluster_toc(), parse_subclusters_standard(), and parse_cluster_11(). Fixed all five so future re-syncs from the Google Doc won't reintroduce this even if comments are left open. Also directly cleaned the six leaked instances already baked into the committed data/clusters_v4.json (a minimal, scoped find/replace on just the affected fields - not a full re-sync from the live doc, to avoid pulling in unrelated content drift). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
👍 All image files/references (if any) are in webp format, in line with our policy. |
Contributor
✅ Spell Check PassedNo spelling issues found when checking 2 changed file(s)! 🎉 |
Contributor
Author
|
✅ Staging Deployment Status This PR has been successfully deployed to staging as part of an aggregated deployment. Deployed at: 2026-07-02 12:54:12 UTC The staging site shows the combined state of all compatible open PRs. |
richarddushime
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/clusters/page showed literal bracket artifacts likeprocess:[ag][ah]andfeedback[ai][aj], have receivedinstead of clean prose.scripts/parse_clusters_to_sheet.pyfetches the source Google Doc via its plain-text export (export?format=txt). Google Docs' plain-text export represents unresolved inline comments as bracketed reference codes (a,b, ...aa,ab, ...) inserted directly into the body text at the comment's anchor point.extract_annotations()helper built for exactly this pattern (used for citation text and sub-cluster ToC names), but the code paths that build cluster- and sub-cluster-level description text appended the raw, uncleaned line instead — 5 call sites acrossparse_cluster_toc(),parse_subclusters_standard(), andparse_cluster_11().Changes
data/clusters_v4.jsonwith a minimal, scoped fix targeting only the affected fields — not a full re-sync from the live doc, to avoid pulling in unrelated content drift.Test plan
/clusters/page🤖 Generated with Claude Code