2 Commits

Author	SHA1	Message	Date
ahmido	440e63edff	feat: implement tenant action taxonomy lifecycle visibility (#174) ... ## Summary Implements Spec 145 for tenant action taxonomy and lifecycle-safe visibility. This PR: - adds a central tenant action policy surface and supporting value objects - aligns tenant list, detail, edit, onboarding, and widget surfaces around lifecycle-safe actions - standardizes operator-facing lifecycle wording around View, Resume onboarding, Archive, Restore, and Complete onboarding - tightens onboarding and tenant lifecycle authorization semantics, including honest 404 vs 403 behavior - updates related regression coverage and spec artifacts for Spec 145 - fixes follow-on full-suite regressions uncovered during validation, including onboarding browser flows, provider consent fixtures, workspace redirect DI expectations, and critical table/action/UI expectation drift ## Validation Executed and passed: - vendor/bin/sail bin pint --dirty --format agent - vendor/bin/sail artisan test --compact Result: - 2581 passed - 8 skipped - 13534 assertions ## Notes - Base branch: dev - Feature branch commit: a33a41b - Filament v5 / Livewire v4 compliance preserved - No panel provider registration changes; Laravel 12 provider registration remains in bootstrap/providers.php - No new globally searchable resource behavior added in this slice - Destructive lifecycle actions remain confirmation-gated and authorization-protected Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #174	2026-03-16 00:57:17 +00:00
ahmido	b0a724acef	feat: harden canonical run viewer and onboarding draft state (#173) ... ## Summary - harden the canonical operation run viewer so mismatched, missing, archived, onboarding, and selector-excluded tenant context no longer invalidates authorized canonical run viewing - extend canonical route, header-context, deep-link, and presentation coverage for Spec 144 and add the full spec artifact set under `specs/144-canonical-operation-viewer-context-decoupling/` - harden onboarding draft provider-connection resume logic so stale persisted provider connections fall back to the connect-provider step instead of resuming invalid state - add architecture-audit follow-up candidate material and prompt assets for the next governance hardening wave ## Testing - `vendor/bin/sail bin pint --dirty --format agent` - `vendor/bin/sail artisan test --compact tests/Feature/144/CanonicalOperationViewerContextMismatchTest.php tests/Feature/144/CanonicalOperationViewerDeepLinkTrustTest.php tests/Feature/Operations/TenantlessOperationRunViewerTest.php tests/Feature/OpsUx/OperateHubShellTest.php tests/Feature/Monitoring/OperationsTenantScopeTest.php tests/Feature/RunAuthorizationTenantIsolationTest.php tests/Feature/Filament/OperationRunEnterpriseDetailPageTest.php tests/Feature/Monitoring/HeaderContextBarTest.php tests/Feature/Monitoring/OperationRunResolvedReferencePresentationTest.php tests/Feature/Monitoring/OperationsCanonicalUrlsTest.php` - `vendor/bin/sail artisan test --compact tests/Feature/ManagedTenantOnboardingWizardTest.php tests/Unit/Onboarding/OnboardingDraftStageResolverTest.php tests/Unit/Onboarding/OnboardingLifecycleServiceTest.php` ## Notes - branch: `144-canonical-operation-viewer-context-decoupling` - base: `dev` Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #173	2026-03-15 18:32:04 +00:00