Generalize the existing /machines command channel from "jump piece-name" into a free-text prompt that runs through the device's prompt.mjs execute() exactly as if you were typing locally. Anything the local prompt accepts (piece names, kidlisp expressions, link/wifi/theme builtins, $code aliases) now works from the web dashboard. - session-server: forward msg.args.text alongside target on cmd:"prompt". - machines.c/.h: widen cmd_target to 2048 for prompt payloads, add an escape-aware json extractor so quoted strings survive transit, and add machines_send_response() that ships {type:"command-response", data:{ok,output}}. - ac-native: new ACRuntime fields (pending_prompt_text/_id) staged when a prompt cmd arrives, then route the runtime through the prompt piece. - js-bindings: system.consumePromptCmd() and system.machinesResponse(id, output, ok). - native prompt.mjs: boot consumes the staged cmd, calls execute(), captures whatever message landed, and ships it back through machinesResponse(). - web machines.mjs: rebrand [Jump] → [Prompt] free-text input, send cmd:"prompt" with {text}, mirror submitted text + device reply as colored log entries.