XFilesManager

fancy-x-files-ui

The compound surface — a tab per file kind wiring each editor next to its live preview over one aggregate model.

Registry JSON
Why
Six well-known files means six editors, six previews, six routes — unless something composes them. Admins want one screen: tabs, edit, see the file, save.
What
XFilesManager is the compound surface: a tab per file kind, each wiring its editor beside its live preview over ONE aggregate XFilesModel (value + onChange). Absent kinds get an Add affordance; kinds / activeKind restrict and control the tabs.
How
Hold the aggregate model, render <XFilesManager value onChange />, persist on save — the sandbox's /admin/well-known-files page is exactly this component over the fancy-x-files backend.