ahmido 1debe40ced feat: implement provider capability registry (#342) ... ## Summary - implement the provider capability registry and derived capability evaluation flow - update provider connections, onboarding, required-permissions diagnostics, and provider blocker translation to use capability-first summaries - add bounded unit, feature, and browser test coverage plus the prepared Spec 283 artifacts ## Notes - branch: `283-provider-capability-registry` - commit: `74e75c3e` - no additional validation commands were run in this git/PR flow step Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #342		2026-05-08 21:17:05 +00:00
..
Boundary	feat: harden provider boundaries (#273)	2026-04-24 21:05:37 +00:00
Capabilities	feat: implement provider capability registry (#342)	2026-05-08 21:17:05 +00:00
TargetScope	feat: implement provider capability registry (#342)	2026-05-08 21:17:05 +00:00
ProviderConnectionType.php	Spec 182: relocate Laravel platform to apps/platform (#213)	2026-04-08 08:40:47 +00:00
ProviderConsentStatus.php	Spec 182: relocate Laravel platform to apps/platform (#213)	2026-04-08 08:40:47 +00:00
ProviderCredentialKind.php	Spec 182: relocate Laravel platform to apps/platform (#213)	2026-04-08 08:40:47 +00:00
ProviderCredentialSource.php	Spec 182: relocate Laravel platform to apps/platform (#213)	2026-04-08 08:40:47 +00:00
ProviderNextStepsRegistry.php	feat: cut over tenant core to managed environments (#335)	2026-05-07 06:38:14 +00:00
ProviderReasonCodes.php	feat: harden provider boundaries (#273)	2026-04-24 21:05:37 +00:00
ProviderReasonTranslator.php	feat: implement provider capability registry (#342)	2026-05-08 21:17:05 +00:00
ProviderVerificationStatus.php	Spec 182: relocate Laravel platform to apps/platform (#213)	2026-04-08 08:40:47 +00:00