SetupWizard
Corex\Kit\SetupWizard · class · Add-ons layer
The pure planning core behind the setup wizard: it turns the registered blueprints into a choosable list, and a chosen blueprint into an activation plan (which modules to activate + which feature flags to enable). No WordPress — the admin screen runs the plan (activate plugins, set options) behind a nonce + capability check.
Public API
Section titled “Public API”__construct(BlueprintRegistry $registry)
Section titled “__construct(BlueprintRegistry $registry)”kits(): array
Section titled “kits(): array”The kits a user can choose from, with what each needs.
plan(string $name, string $level): array
Section titled “plan(string $name, string $level): array”The activation plan for a kit by name: the modules to activate (required + recommended, de-duped, order preserved) and the feature flags to enable. Returns an empty plan for an unknown kit.
demoLevels(): array
Section titled “demoLevels(): array”The demo-content levels the wizard offers (FR-137). Each drives a real, differentiated page set via {@see \Corex\Kit\Company\CompanyBlueprint::pages()} — never a cosmetic toggle.
conflictChoices(): array
Section titled “conflictChoices(): array”The choices offered for a page that already holds user content (FR-139). Each maps to a real {@see \Corex\Kit\Setup\ConflictResolver} outcome; the default is always Keep Mine (FR-143).
brandFields(): array
Section titled “brandFields(): array”The brand fields the wizard’s brand step captures (FR-135). Each key is a REAL Config dot-key registered in the Settings brand section, so saving persists to the prefixed option the framework reads — these are never placeholder inputs.