feat(external-message): Hash normalization and message lookup (copypasted from TonConnect docs)

[Shvandre]

Closes #44

[github-actions]

Verdict: NEEDS_CHANGES

Thanks for the solid docs update. This PR adds useful pages, examples, and nav entries. It needs a few correctness, safety, and style fixes before merge.

Overall Verdict: NEEDS_CHANGES

• [BLOCKER] Bag of Cells page — ton/cells/BagOfCells.mdx is empty in nav — Remove from nav or add a short stub (purpose, when to use, link to BoC reference) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L28

• [BLOCKER] Library cells public flag — Incorrect public flag behavior — Replace with: “This flag controls visibility; when false, the library cell is private (only the hosting account can use it), even if hosted in the MasterChain.” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L36

• [HIGH] Safety warning — ecosystem/rpc/external-normalisation.mdx lacks a clear Warning callout — Add a Warning at the top with risk, scope, rollback steps, and Testnet/Mainnet label — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L44

• [HIGH] Safer defaults (endpoints) — Examples use mainnet by default — Default to testnet RPC endpoints and note how to switch to mainnet — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L52

• [HIGH] US spelling — Title and prose use “normalisation” — Change to “normalization” in title and prose (do not change code) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L60

• [HIGH] Headings structure and case — Multiple in‑page # and Title Case — Keep a single H1 (from frontmatter), demote in‑page # to ##, use sentence case, remove emojis — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L68

• [MEDIUM] Snippet labeling — Partial code shown without context — Label as “Not runnable” or provide full runnable context (e.g., getNormalizedExtMessageHash, retry, getTransactionByInMessage, waitForTransaction, “Using @ton/core”) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L76

• [MEDIUM] Placeholders — Implicit values in examples — Use explicit placeholders like <EXTERNAL_IN_BOC>, <RPC_URL>, and define on first use — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L84

• [MEDIUM] Imperative headings — Non‑imperative or gerund headings — Use imperative, sentence case: “Use @ton/core”, “Publish …”, “Test in Blueprint”, “Retrieve …” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L92

• [MEDIUM] Chain terminology — Mixed casing for chains — Use canonical “MasterChain” and “BaseChain” in prose across pages — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L100

• [MEDIUM] Library intro clarity — Vague first sentence — Clarify to: “Libraries extend the on‑chain deduplication mechanism …” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L108

• [MEDIUM] Environment term — Inconsistent phrasing — Use “smart contract library environment” (generic, no hyphen) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L116

• [MEDIUM] Code identifiers in prose — Fields and types not in code font — Wrap identifiers in code font: external-in, src, importFee, init, StateInit, body — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L124

• [MEDIUM] Abbreviation naming — Mixed BoC naming in prose vs code — Use “external‑in message BoC” in prose; keep code variables (e.g., boc) as‑is — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L132

• [MEDIUM] TL‑B reference — First mention lacks link — Link the first “TL‑B” mention to the canonical reference and keep later mentions unlinked — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L140

• [LOW] Descriptive link text — “here”/“See also” links are vague or long — Use descriptive link text and trim “See also” to 1–3 key links — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L148

• [LOW] Oxford comma — Missing comma in lists — Use the Oxford comma, e.g., “init, src, and importFee” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L156

• [LOW] API capitalization — “api failures” in prose — Use “API failures” (uppercase) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L164

• [LOW] Generic terms casing — Over‑capitalized common nouns — Use lowercase for generic terms (e.g., “jetton wallet”) — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L172

• [LOW] Opcode formatting — Opcodes not code‑formatted — Wrap opcodes like XLOAD, XCTOS in code font consistently — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L180

• [LOW] Ambiguous pronoun — Unclear reference in library cells — Use explicit subject: “Library cells always have level 0.” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L188

• [LOW] Throat‑clearing opener — Wordy opener in usage guide — Tighten to: “Read Library cells first.” — Style guide: https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L196

If you want, I can draft the exact text changes for each file.

[anton-trunov]

We need a few adjustements here:

• rename the article to better explain its contents, it's not really about normalization;
• clearly explain we are talking about looking for external messages from TON Connect to use for the purposes of UI, not payment processing;
• move to TON Connect section;
• make it clear TEP-467 is not a real TEP, but a TEP proposal that became a standard de-facto.