/**
 * Escape a config value for use as ONE URL path segment. Without it a value
 * containing `/`, `?` or `#` (e.g. a pasted ID with a trailing path) would
 * re-route the credentialed request within the vendor host. `:` and `@` stay
 * literal — both are legal in a path segment (RFC 3986 `pchar`) and Telegram
 * bot tokens contain `:`.
 *
 * `''`, `.` and `..` are rejected rather than escaped: the WHATWG URL parser
 * collapses dot-segments (even `%2e`), and an empty segment silently changes
 * the path.
 */
export declare function encodePathSegment(value: unknown, field: string): string;