ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

test: add post-scope contract browser verification gate (340) #411

Merged
ahmido merged 1 commits from 340-post-scope-contract-browser-verification-gate into platform-dev 2026-05-31 14:37:31 +00:00
Conversation 0 Commits 1 Files Changed 10 +1172
ahmido commented 2026-05-31 14:22:58 +00:00
Owner
Copy Link

Summary

  • add the Spec 340 browser verification gate package for the post-338/339 workspace and environment scope contract
  • add a bounded Pest browser smoke that verifies clean workspace origin, environment origin, explicit environment_id hub filtering, remembered-environment non-authority, and Provider Connections create/view/edit authority signals
  • record the verification inventory, matrix, findings, checklist, and audit report under specs/340-post-scope-contract-browser-verification-gate/
  • document a GO recommendation with no confirmed P1/P2 drift and one backlog wording follow-up
  • keep the change verification-only with no runtime behavior, schema, or route-family changes

Validation

  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec340PostScopeContractVerificationSmokeTest.php
  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/ProviderConnections --filter=ScopeHardening
  • cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent
  • git diff --check --no-index /dev/null apps/platform/tests/Browser/Spec340PostScopeContractVerificationSmokeTest.php
  • git diff --check

Notes

  • Livewire v4 compliance unchanged
  • Filament provider registration remains in apps/platform/bootstrap/providers.php
  • no globally searchable resource behavior changed
  • no destructive action behavior changed or executed in this verification gate
  • no new Filament assets; deploy filament:assets posture is unchanged
## Summary - add the Spec 340 browser verification gate package for the post-338/339 workspace and environment scope contract - add a bounded Pest browser smoke that verifies clean workspace origin, environment origin, explicit `environment_id` hub filtering, remembered-environment non-authority, and Provider Connections create/view/edit authority signals - record the verification inventory, matrix, findings, checklist, and audit report under `specs/340-post-scope-contract-browser-verification-gate/` - document a `GO` recommendation with no confirmed P1/P2 drift and one backlog wording follow-up - keep the change verification-only with no runtime behavior, schema, or route-family changes ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec340PostScopeContractVerificationSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/ProviderConnections --filter=ScopeHardening` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - `git diff --check --no-index /dev/null apps/platform/tests/Browser/Spec340PostScopeContractVerificationSmokeTest.php` - `git diff --check` ## Notes - Livewire v4 compliance unchanged - Filament provider registration remains in `apps/platform/bootstrap/providers.php` - no globally searchable resource behavior changed - no destructive action behavior changed or executed in this verification gate - no new Filament assets; deploy `filament:assets` posture is unchanged
ahmido added 1 commit 2026-05-31 14:22:59 +00:00
test: add post-scope contract browser verification gate (340)
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 59s
Details
196271ac01
ahmido merged commit a3b21c48d8 into platform-dev 2026-05-31 14:37:31 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#411
No description provided.
Delete Branch "340-post-scope-contract-browser-verification-gate"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?