The 128-character cap lived in four unlinked copies — the chat piece, the keyboard clamp, the MCP tool, and the server that actually enforces it. Now shared/chat-capabilities.mjs holds it once, next to the message syntax and the bare-word commands, and everything else reads from there. The server hands the object to every client in the connected packet, so the chat piece takes its limit from the handshake instead of a hardcoded default, and serves it at /chat/capabilities (plus /api/chat-capabilities on lith) for bots that want the contract before they post. The chat_send MCP tool builds its description from the same object, so an agent learns the cap and the quoting rule that makes a piece name tappable from the tool contract rather than by reading source.