Load the config root's tool extensions (definitions, schema, settings and name collisions with the platform's tools), its hooks (source and settings) and every page's handlers anywhere under the root (a page is wherever its entry HTML is), with the runtime's own loaders. Each entry is listed with the files it bundles; every error is printed as the agent would report it at boot.

When a tsconfig.json exists at the root and tsc is on the path, tsc --noEmit runs too.

Bookmarks (.genie/bookmarks.json) are read with the platform's own parser: an entry it would drop from the menu (no label, no path, a path that is not clean and relative to the agent dir, past the 50-entry limit) is an error, and so are a path no menu shows and a shared/ path that is a folder: bookmarks open files.

Duplicate labels and a shared/ file missing from the root are warnings.

Each kept entry says who sees it; paths outside the config plane are workspace files, resolved at runtime.

Exit status is 1 when anything fails; warnings do not fail.

mutiro agent dev check <config-root> [flags]