fix: register core before a module whose package sorts ahead of it

src/Providers/ModuleServiceProvider.php

@@ -5,6 +5,7 @@
 use Illuminate\Support\ServiceProvider;
 use Illuminate\Support\Str;
 use InterNACHI\Modular\Support\ModuleRegistry;
+use Saucebase\Core\CoreServiceProvider;
 
 abstract class ModuleServiceProvider extends ServiceProvider
 {
@@ -37,6 +38,11 @@ public function boot(): void
      */
     public function register(): void
     {
+        // Laravel registers discovered packages alphabetically, so a module named
+        // before "core" gets here first and moduleName() would find no registry.
+        // Registering an already-registered provider is a no-op.
+        $this->app->register(CoreServiceProvider::class);
+
         // Config is merged here rather than in boot() because every register() runs
         // before any boot(): a provider that reads a module's config while booting —
         // Filament resolving its panels, for one — would otherwise race the merge and

tests/Feature/ModuleBootOrderTest.php

@@ -0,0 +1,27 @@
+<?php
+
+namespace Saucebase\Core\Tests\Feature;
+
+use Saucebase\Core\Tests\Concerns\InteractsWithFixtureModules;
+use Saucebase\Core\Tests\TestCase;
+
+/**
+ * A module registers before core when its package name sorts first.
+ *
+ * Laravel registers discovered packages alphabetically, so `saucebase/auth` reaches
+ * its provider's register() before `saucebase/core` has bound the module registry.
+ */
+class ModuleBootOrderTest extends TestCase
+{
+    use InteractsWithFixtureModules;
+
+    protected function getPackageProviders($app): array
+    {
+        return [...$this->fixtureModuleProviders(), ...parent::getPackageProviders($app)];
+    }
+
+    public function test_a_module_registered_before_core_still_merges_its_config(): void
+    {
+        $this->assertSame('Module Test Fixture', config('module-test-fixture.name'));
+    }
+}