bvandeusen/FabledScribe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 50 Wiki Activity

MCP _INSTRUCTIONS: multi-user sharing ACL guard #58

Merged
bvandeusen merged 1 commits from dev into main 2026-06-03 14:18:01 -04:00
Conversation 0 Commits 1 Files Changed 1
+7
bvandeusen commented 2026-06-03 14:17:56 -04:00
Owner
Copy Link
Copy Source
  • d4666be feat(mcp): add the multi-user sharing ACL guard to _INSTRUCTIONS — every read/mutation of user data must scope by owner + shares via services/access.py. Correctly scoped to FabledScribe and always-loaded.

CI green on dev head d4666be (run #349). This merge triggers a main build (:<sha>). Shipping it to prod (release + deploy) unblocks scribe task #595 (retire the now-redundant rulebook copy).

🤖 Generated with Claude Code

- **d4666be** `feat(mcp)`: add the multi-user sharing ACL guard to `_INSTRUCTIONS` — every read/mutation of user data must scope by owner + shares via `services/access.py`. Correctly scoped to FabledScribe and always-loaded. CI green on dev head `d4666be` (run #349). This merge triggers a `main` build (`:<sha>`). Shipping it to prod (release + deploy) unblocks scribe task #595 (retire the now-redundant rulebook copy). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
bvandeusen added 1 commit 2026-06-03 14:17:57 -04:00
feat(mcp): add multi-user sharing ACL guard to _INSTRUCTIONS
CI & Build / Python lint (push) Successful in 3s
Details
CI & Build / TypeScript typecheck (push) Successful in 32s
Details
CI & Build / Python tests (push) Successful in 44s
Details
CI & Build / Build & push image (push) Successful in 1m15s
Details
d4666bea7f 
The ACL constraint (scope every read/mutation by owner + shares via
services/access.py) is a security-correctness invariant that should
always be loaded, and it's FabledScribe-specific — so it belongs in
Scribe's own contained _INSTRUCTIONS, not the cross-project FabledSword
rulebook. The redundant rulebook rule will be retired once this ships
to prod.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bvandeusen merged commit 301352f628 into main 2026-06-03 14:18:01 -04:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bvandeusen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#58
Delete Branch "dev"

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?