Story-3132 · functions lane

WhatsApp answers that read at a glance

Long Vani answers now split into readable WhatsApp bubbles at 600 characters. The independent 4096-character Meta API guard remains in the sender, so readability and provider acceptance keep separate limits.

What counsel receives

• 14 Mar 2024: Agreement signed
• 22 Aug 2025: Quality report received

`M-013 · 1/3`

Every split-answer chunk carries its position in the matter signature; single-message answers keep the bare code without a noisy 1/1. The longest N/N suffix is reserved inside the 600-character limit, so the counter cannot create a new “Read more” bubble. Matter title, firm name, brackets, and dashes are deliberately absent.

Deterministic presentation

Markdown bullets become visible Unicode bullets; Markdown bold and strikethrough become WhatsApp syntax; heading markers become bold text; quote markers become a visible quote bar; unsupported underline tags are removed without removing their text. Paragraph, line, sentence, and word break preference remains unchanged.

Rail boundary

The signature is added only by the WhatsApp converse-answer dispatch. ACP answers bypass this formatter and remain unsigned. No model call, new network dependency, compatibility path, or quiet-hours hold was added.

Review checks

• A 1400-character answer becomes multiple messages of at most 600 characters.
• Every split message ends with `M-013 · n/N` after one blank line.
• No Markdown list asterisk survives as a bullet marker.
• The ACP answer contains no WhatsApp signature.