Every manifest problem, or []. The manifest is plain data, so this runs
without activating anything. Checks: ids are well formed and unique; every
requires names a core service the host implements; routes, sockets, CLI
verbs, job kinds and storage entries are well formed and unique across
modules (routes by method and path shape, storage case-insensitively and not
nested in another module's path, except that two modules may declare the same
entry, one path and kind, to share it); a panel's tag follows the id and its declared route is unique.
Every manifest problem, or
[]. The manifest is plain data, so this runs without activating anything. Checks: ids are well formed and unique; everyrequiresnames a core service the host implements; routes, sockets, CLI verbs, job kinds and storage entries are well formed and unique across modules (routes by method and path shape, storage case-insensitively and not nested in another module's path, except that two modules may declare the same entry, one path and kind, to share it); a panel's tag follows the id and its declared route is unique.