test(plugin-security): the owner-may-edit delegator holds its set by a direct grant (#24757)

controlled-by-parent-owner-may-edit.test.ts landed on main (#26005) after this
branch's base. Its delegator reached omd_requester through a sys_user_position
row named after the set, the fold this PR retires, so the delegated-update pin
refused at the on-behalf-of check instead of the master gate. The row is now a
sys_user_permission_set grant, the same rebinding the chain-middle-master suite
received; every expectation is unchanged.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J8LYP8UCJURxbFWZqnywyD

Author: claude

packages/plugins/plugin-security/src/controlled-by-parent-owner-may-edit.test.ts

@@ -180,14 +180,14 @@ beforeAll(async () => {
     id, name: id, email: `${id}@omd.test`,
   })), SYS);
   await engine.insert('sys_organization', [{ id: ORG, name: 'OMD', slug: 'omd' }], SYS);
-  // The delegator holds the requester's set through a stored position row
+  // The delegator holds the requester's set through a stored direct grant row
   // owned by ORG, so the on-behalf-of link resolves to the same grants the
   // owner holds — and NO `sys_member` row, so no ownership floor binds the
   // delegator's pass: the only thing left to refuse a delegated update is the
   // master gate, which is the pin (see the chain-middle-master suite for why
   // the row lands straight through the driver).
-  await (engine as any).getDriver('sys_user_position').create('sys_user_position', {
-    id: 'up_delegator', user_id: DELEGATOR, position: REQUESTER_SET.name, organization_id: ORG,
+  await (engine as any).getDriver('sys_user_permission_set').create('sys_user_permission_set', {
+    id: 'ups_delegator', user_id: DELEGATOR, permission_set: REQUESTER_SET.name, organization_id: ORG,
   });
 
   let securityService: unknown;