Tiger_Module_Discovery

@api

Tiger_Module_Discovery — find the modules present on disk (active or not).

The activation gate strips inactive modules from the runtime controller-directory map, so the Modules admin can't enumerate from there — it scans the module DIRECTORIES instead (app + first-party core), reading each module.json manifest when present. The (future) installer reuses this to know what's installed. Pure filesystem read — no DB, no state.

Methods

all()

all()

All modules on disk, keyed by slug: {slug, area, name, version, description, author, license, homepage, pricing, has_manifest}.

Returns array<string,array> — module metadata rows keyed by slug (sorted)