refactor: clarify WorkspaceScope vs BelongsToWorkspace architecture #5
Labels
No labels
P1
P2
P3
PHP
agent-ready
bug
clotho
discovery
docs
epic
refactor
review
security
testing
athena
athena-gemini
audit
clotho
clotho-gemini
codex
darbs-claude
security
wiki
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: core/php-tenant#5
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem
The
WorkspaceScopeclass exists inScopes/WorkspaceScope.phpbut is not applied as a global scope viaBelongsToWorkspacetrait. The relationship between these two mechanisms is unclear.Impact
Developers consuming this package are unsure when to use
WorkspaceScope(global scope) vsBelongsToWorkspace(trait-based auto-assignment). This can lead to workspace isolation bugs.Acceptance Criteria
WorkspaceScopevsBelongsToWorkspaceshould be usedWorkspaceScopeas a proper Eloquent global scopeCLAUDE.mdwith guidance for contributorsdocs/architecture.mdDiscovered during automated scan (issue #3)