robots.txt is tiny and high-stakes: one mis-ordered Allow leaks an admin path to a single bot group, and no one notices until it's indexed. Hand-editing the file (or hand-rolling a form) has no guardrail for that class of mistake.

RobotsEditor is a controlled rule builder — per-group User-agent / Allow / Disallow / Crawl-delay plus sitemap URLs — with the protect() safety rail: protected paths are pinned Disallow for EVERY group, rendered as red chips, stripped from Allow lists, and flagged by validateRobots if they ever sneak back.

Hold the RobotsModel in state, render the editor beside <XFilePreview kind="robots">, and persist the model to your backend (particle-academy/fancy-x-files renders the identical file server-side). List private paths in protectedPaths and the rail does the rest.