fix(external-hash): follow-up review by Anton Trunov

[Shvandre]

Closes #382

[github-actions]

Verdict: NEEDS_CHANGES

Summary
The new page is useful, but it needs structural, safety, and style fixes. One empty doc must be removed or completed. Title/H1 and doc type need alignment. Examples need safer defaults and clearer placeholders. Headings, tone, punctuation, and casing should follow the style guide.

Findings

• [BLOCKER] Empty doc page — ton/cells/bag-of-cells.mdx is empty — Remove it, or add valid frontmatter and a matching H1 with a short purpose/outcome — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L20
• [BLOCKER] Title/H1 structure — ecosystem/rpc/external-normalization.mdx title and H1 are not aligned — Set title: "External message normalization" (US spelling), add a single # External message normalization as the first content after imports, and place any Aside below H1 — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L60
• [HIGH] Doc type and intro — Page mixes concept and how‑to without clear framing — Add doc_type: "How‑to guide" to frontmatter; start with brief “Goal” and “Prerequisites”; keep short “Background” below — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L40
• [HIGH] Safety callout completeness — Warning/danger Aside is incomplete — Include Risk, Scope, Mitigation/Rollback, and Environment; default to testnet where it applies — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L120
• [MEDIUM] Code snippets and placeholders — Snippets use '...your-base64-message...' and unlabeled partials — Replace with <BASE64_BOC> and define it on first use; label partial snippets “Not runnable” or make them runnable by adding imports/setup; example: const tx = await getTransactionByInMessage('<BASE64_BOC>', client); — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L150
• [MEDIUM] Headings/procedures — Some headings are gerunds and not unique — Use imperative headings and unique examples, e.g., “Retry API calls”, “Wait for transaction confirmation”, “Example: getTransactionByInMessage”, “Example: waitForTransaction” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L80
• [MEDIUM] Spelling consistency — Mixed “normalisation/normalization” forms — Use US spelling “normalization” throughout; set frontmatter title: "External message normalization" — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L30
• [LOW] Link stability — Uses a PR link for TEP — Replace PR link with the canonical TEP‑467 document URL — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L160
• [LOW] List punctuation — Missing Oxford comma — Use the Oxford comma in series: “init, src, and importFee” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L170
• [LOW] Tone — Some sentences hedge or are indirect — Use clear, direct, imperative phrasing (e.g., “Do not use external message tracking for payment processing. See payment processing.”) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L90
• [LOW] Abbreviation casing — “Base64 boc” casing is inconsistent — Use “Base64 BoC” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L100
• [LOW] Safer defaults — Examples assume mainnet implicitly — Use a testnet endpoint in examples, or add a note to switch to mainnet explicitly when ready — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L130

Overall Verdict
NEEDS_CHANGES