Install profiles live here.

Suggested profiles:
  minimal/
  default/
  developer/

Current status:
  minimal/ is a real file-based profile with editable template and page assets.
  default/ now uses manifest-driven payload metadata plus editable assets.
  developer/ currently falls back to the legacy minimal installer path.

Each profile can contain profile.json plus editable templates, stylesheets, pages, and assets.

Structured manifest support now exists for:
  designs
  template_types
  templates
  stylesheets
  pages
  copies
  udts
  sql

See:
  ../../docs/PROFILE_MANIFEST.txt

Notes:
  UDT payloads should be stored as .udt files.
  SQL payloads should be stored as .sql files.
  Manifest fragments may be JSON or PHP arrays during migration, but JSON is preferred long-term.
  Template manifests can reference existing types such as Core::page when needed.
  Module-owned template types/templates are normally installed by the module, not by the base installer profile.
