## Summary - normalize provider-neutral target-scope and identity contracts across provider connection resolution, operation-start gating, verification reporting, and boundary configuration - align provider connection resource, onboarding, tenant summaries, and operation follow-up on the same shared scope contract while keeping Microsoft-specific profile details in provider-owned metadata - add Spec 281 artifacts and focused feature/browser coverage for the new provider-scope contract - move the tenant dashboard context-chip rail into Filament header widgets so the metadata row renders directly under the page subtitle ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Providers/ProviderConnectionTargetScopeNeutralityTest.php tests/Feature/Providers/ProviderIdentityResolutionNeutralityTest.php tests/Feature/Providers/ProviderOperationStartGateTargetScopeContextTest.php tests/Feature/Filament/ProviderConnectionResourceScopeSummaryTest.php tests/Feature/Onboarding/ManagedTenantOnboardingProviderConnectionScopeTest.php tests/Feature/Guards/ProviderConnectionMicrosoftScopeLeakGuardTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec281ProviderConnectionScopeSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Dashboard/TenantDashboardProductizationSummaryTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Dashboard/TenantDashboardProductizationSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` ## Notes - Filament remains on v5 with Livewire v4-compatible surfaces only. - Provider registration location is unchanged; Laravel 11+ providers stay in `apps/platform/bootstrap/providers.php`. - `ProviderConnectionResource` remains non-globally-searchable and still exposes View/Edit pages. - No new asset registration was added; deploy-time `filament:assets` expectations are unchanged. - No new destructive action path was introduced; existing server authorization and confirmation handling remain in place where applicable. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #339
58 lines
2.9 KiB
PHP
58 lines
2.9 KiB
PHP
<?php
|
|
|
|
use App\Support\Providers\Boundary\ProviderBoundaryCatalog;
|
|
use App\Support\Providers\Boundary\ProviderBoundaryOwner;
|
|
use App\Support\Providers\Boundary\ProviderBoundarySeam;
|
|
|
|
it('classifies the authoritative first-slice provider seams', function (): void {
|
|
$catalog = app(ProviderBoundaryCatalog::class);
|
|
|
|
expect(array_keys($catalog->all()))->toBe([
|
|
'provider.connection_resolution',
|
|
'provider.gateway_runtime',
|
|
'provider.identity_resolution',
|
|
'provider.operation_registry',
|
|
'provider.operation_start_gate',
|
|
]);
|
|
|
|
expect($catalog->get('provider.gateway_runtime')->owner)->toBe(ProviderBoundaryOwner::ProviderOwned);
|
|
expect($catalog->get('provider.identity_resolution')->owner)->toBe(ProviderBoundaryOwner::PlatformCore);
|
|
expect($catalog->get('provider.connection_resolution')->owner)->toBe(ProviderBoundaryOwner::PlatformCore);
|
|
expect($catalog->get('provider.operation_registry')->owner)->toBe(ProviderBoundaryOwner::PlatformCore);
|
|
expect($catalog->get('provider.operation_start_gate')->owner)->toBe(ProviderBoundaryOwner::PlatformCore);
|
|
});
|
|
|
|
it('records implementation paths and bounded exception metadata for platform-core seams', function (): void {
|
|
$catalog = app(ProviderBoundaryCatalog::class);
|
|
|
|
$identity = $catalog->get('provider.identity_resolution');
|
|
|
|
expect($identity->coversPath('app/Services/Providers/ProviderIdentityResolution.php'))->toBeTrue()
|
|
->and($identity->neutralTerms)->toContain('target scope')
|
|
->and($identity->retainedProviderSemantics)->toContain('provider_context.microsoft_tenant_id')
|
|
->and($identity->retainedProviderSemantics)->not->toContain('Microsoft Graph option keys')
|
|
->and($identity->followUpAction)->toBe(ProviderBoundarySeam::FOLLOW_UP_DOCUMENT_IN_FEATURE);
|
|
|
|
$registry = $catalog->get('provider.operation_registry');
|
|
|
|
expect($registry->neutralTerms)->toContain('provider binding')
|
|
->and($registry->retainedProviderSemantics)->toContain('active provider binding')
|
|
->and($registry->followUpAction)->toBe(ProviderBoundarySeam::FOLLOW_UP_DOCUMENT_IN_FEATURE);
|
|
});
|
|
|
|
it('aligns the catalog shape with the logical boundary contract', function (): void {
|
|
$seam = app(ProviderBoundaryCatalog::class)->get('provider.operation_start_gate');
|
|
|
|
expect($seam->key)->toBe('provider.operation_start_gate')
|
|
->and($seam->owner->value)->toBeIn(ProviderBoundaryOwner::values())
|
|
->and($seam->description)->not->toBeEmpty()
|
|
->and($seam->implementationPaths)->not->toBeEmpty()
|
|
->and($seam->neutralTerms)->not->toBeEmpty()
|
|
->and($seam->retainedProviderSemantics)->toContain('provider_context.microsoft_tenant_id')
|
|
->and($seam->followUpAction)->toBeIn([
|
|
ProviderBoundarySeam::FOLLOW_UP_NONE,
|
|
ProviderBoundarySeam::FOLLOW_UP_DOCUMENT_IN_FEATURE,
|
|
ProviderBoundarySeam::FOLLOW_UP_SPEC,
|
|
]);
|
|
});
|