KitProvisioner
Corex\Provisioning\KitProvisioner · interface · Core layer
The seam between the kit framework (which knows blueprints) and the consumers that drive activation — the Add-ons screen prompt and the dashboard card (spec 042). Defined in corex-core so corex-config depends only on this interface, never on a kit add-on (Principle IX): corex-config resolves it optionally from the container and degrades gracefully when no kit framework is active. The kit framework binds a concrete implementation.
Public API
Section titled “Public API”applicableKits(): array
Section titled “applicableKits(): array”Kits that declare applicable starter content (pages/flags/modules).
isApplicable(string $kit): bool
Section titled “isApplicable(string $kit): bool”Whether $kit is a known applicable kit.
kitForModule(string $addonSlug): ?string
Section titled “kitForModule(string $addonSlug): ?string”The kit name an add-on slug provisions (e.g. corex-kit-company → company), or null when the add-on is not a kit. Lets a consumer map an enabled add-on to its kit without knowing the kit framework’s internals.
preview(string $kit): ApplyPreview
Section titled “preview(string $kit): ApplyPreview”Read-only: what applying $kit would do. Performs no writes.
apply(string $kit): ApplyOutcome
Section titled “apply(string $kit): ApplyOutcome”Apply $kit through the single shared apply path; returns the outcome.