/**
 * Plan/35: split a mesh envelope body into a human-readable sender label and
 * the message text.
 *
 * Since the address (`from`) became a path/route — great for replies,
 * unreadable as a label — a sender MAY shape the body as `{ name, text }`:
 * `name` is a display-only nickname, `text` is the content. `from` stays the
 * reply-to route untouched, so the 5-field envelope schema is unchanged — this
 * is purely a body convention, not a new field.
 *
 * Fallbacks keep every legacy/cross-path message working:
 *   - a string body  → the text verbatim, label = `fallbackName` (the route);
 *   - any other shape → JSON-stringified, label = `fallbackName`;
 *   - `{ name }` only → label = name, text = the JSON of the body;
 *   - `{ text }` only → label = `fallbackName`, text = text.
 */
export declare function meshMessageDisplay(body: unknown, fallbackName: string): {
    name: string;
    text: string;
};