WIP: test(routing): recipient checks have exactly the recipient's access #47

Draft
KofTwentyTwo wants to merge 1 commits from test/recipient-full-access into develop
pull from: test/recipient-full-access
KofTwentyTwo commented 2026-10-16 19:31:00 +00:00 (Migrated from github.com)

This PR is test only, for the owner decision of 2026-10-16 (qqq#1265, DelegatedAccess.USER). It checks that a per-recipient check made through the alerts principal has exactly the recipient's permissions and record-lock keys, even though the principal itself holds none.

Draft: it needs the QQQ RC that contains qqq#1265; bump qqq.snapshot.version when it's cut.

  • Against a local build of #1265, the test passes (2/2).
  • Against RC.19, it fails. RC.19 intersects with the principal's grants, so this test is what pins the new behaviour.

🤖 Generated with Claude Code

This PR is test only, for the owner decision of 2026-10-16 (qqq#1265, `DelegatedAccess.USER`). It checks that a per-recipient check made through the `alerts` principal has exactly the recipient's permissions and record-lock keys, even though the principal itself holds none. **Draft:** it needs the QQQ RC that contains qqq#1265; bump `qqq.snapshot.version` when it's cut. - Against a local build of #1265, the test passes (2/2). - Against RC.19, it fails. RC.19 intersects with the principal's grants, so this test is what pins the new behaviour. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Checking for merge conflicts…
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin test/recipient-full-access:test/recipient-full-access
git checkout test/recipient-full-access
Sign in to join this conversation.