Skip to content

docs(investigations): encoding corroboration on #819 mindmap HTML wrappers (read-only, 0 write) - #821

Merged
jsboige merged 1 commit into
masterfrom
docs/819-mindmap-wrapper-encoding
Jul 16, 2026
Merged

docs(investigations): encoding corroboration on #819 mindmap HTML wrappers (read-only, 0 write)#821
jsboige merged 1 commit into
masterfrom
docs/819-mindmap-wrapper-encoding

Conversation

@jsboige

@jsboige jsboige commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

What

Read-only encoding check on the 29 integrated HTML mindmap wrappers regenerated by #819 — the format served in prod and opened in-browser by Thomas & Adeline (gate (b) review vehicle). Extends the #818 encoding thread. No write, no regen, no C#/CSV touched.

Why

#819 built its wrappers from the .content.svg files that carry the #804 residual #3 (ai-01 Cycle H: they declare encoding="utf-16" but are actually UTF-8+BOM). The de-risking question: did that latent propagate into the file T&A actually open?

Result — 0 propagation

Metric Value
Wrappers checked 29
Really UTF-8 29/29
Declare charset=UTF-8 (meta) 29/29
utf-16-declared-but-utf8 mismatches 0

The latent does not reach the review vehicle. MindMapHtmlWrapper.FormatWrapper strips the <?xml?> prologue and injects the SVG into an HTML shell with its own charset=UTF-8 — the erroneous utf-16 declaration is eliminated, not inherited.

This independently corroborates ai-01's Cycle H localization certification (SHA256 #636 + script composition) on the freshest artifact (#819, post-Cycle-H).

Tracked-not-fixed observation

4/29 wrappers carry a BOM (Fallacies_{ar,es,fa,zh}.html) — harmless (meta charset + BOM precedence renders correctly) but inconsistent with the other 25. Fix = po-2013 regen lane (mindmaps), not po-2024 (Cards). Folded into po-2023's post-tag mindmap regen pass (#804 #1/#2/#3).

Out of scope

Verification

  • Script: scratchpad Python stdlib, read-only, <2s.
  • No build/test/render impact. 1 file / 54 insertions.

Refs

#819 · #804 residual #3 · #818 · #458

— po-2024 (tick 29, jsboige work-session request)

…ppers (read-only, 0 write)

Read-only check on the 29 integrated HTML mindmap wrappers regenerated by
#819 (the T&A review vehicle for gate (b)), extending the #818 encoding
thread. Answers a concrete de-risking question: did the #804 residual #3
(.content.svg declare encoding="utf-16" but are UTF-8+BOM, ai-01 Cycle H)
propagate into the file Thomas & Adeline actually open?

Result: NO. 0/29 wrappers carry the latent.
- 29/29 are really UTF-8, declare charset=UTF-8 (meta).
- 0 utf-16-declared-but-utf8 mismatches.
- Cause: MindMapHtmlWrapper.FormatWrapper strips the <?xml?> prologue and
  injects the SVG into an HTML shell with its own charset=UTF-8, so the
  erroneous utf-16 declaration is eliminated, not inherited.

Independently corroborates ai-01's Cycle H localization certification
(SHA256 #636 + script composition) on the freshest artifact (#819).

Tracked-not-fixed observation: 4/29 wrappers carry a BOM
(Fallacies_{ar,es,fa,zh}.html) — harmless (meta charset + BOM precedence)
but inconsistent. Fix = po-2023 regen lane (mindmaps), not po-2024
(Cards). Folded into po-2023's post-tag mindmap regen pass (#804 #1/#2/#3).

Out of scope: wrapper/.content.svg regen, MindMapHtmlWrapper edit, BOM
strip — all lane po-2023. No write prod this PR.

Refs: #819, #804 residu #3, #818, #458.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jsboige
jsboige merged commit fccb5b3 into master Jul 16, 2026
2 checks passed
@jsboige
jsboige deleted the docs/819-mindmap-wrapper-encoding branch July 16, 2026 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant