test(react): pin that useActionEngine no longer harvests the retired keys

CI caught two useActionEngine tests still asserting the metadata harvest this
branch removed: getBulkActions() picking up `bulkEnabled: true` and
handleShortcut() resolving `shortcut: 'ctrl+k'`, both read off an
ActionSchema array.

Inverted deliberately rather than reverted. Neither capability has a product
consumer — `record-quick-actions` and `record-alert`, the only two callers of
this hook, use `getActionsForLocation` / `executeAction` — so removing the
harvest broke no live path; the tests were pinning the read of a key that
spec 17 retired and that no longer parses. The stale keys stay in the fixture
on purpose, so the assertions now prove they are IGNORED — the same shape as
plugin-grid's "ignores a stale bulkEnabled flag on an object action".

The engine's own bulk / shortcut mechanics keep their coverage in
ActionEngine.test.ts, where a host passes those options to registerAction
explicitly, which is still supported.

Full suite: 9277 passed / 0 failed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S9aiswZBzoVYsyLKRuGByE

Author: claude

packages/react/src/hooks/__tests__/useActionEngine.test.ts

@@ -78,14 +78,20 @@ describe('useActionEngine', () => {
   });
 
   describe('getBulkActions', () => {
-    it('returns only bulk-enabled actions', () => {
+    // Deliberately INVERTED. `sampleActions` still carries the stale
+    // `bulkEnabled: true` — spec 17 retired the key as a `retiredKey()`
+    // tombstone, so metadata like this no longer parses at all, and harvesting
+    // it here made a dead registration option look load-bearing. Same posture
+    // as plugin-grid's "ignores a stale bulkEnabled flag on an object action".
+    // The engine's bulk mechanics keep their coverage in ActionEngine.test.ts,
+    // where a HOST passes `{ bulkEnabled: true }` to `registerAction`
+    // explicitly — which is still supported.
+    it('does not harvest the retired bulkEnabled key from metadata', () => {
       const { result } = renderHook(() =>
         useActionEngine({ actions: sampleActions }),
       );
 
-      const bulkActions = result.current.getBulkActions();
-      expect(bulkActions.length).toBe(1);
-      expect(bulkActions[0].name).toBe('mark_complete');
+      expect(result.current.getBulkActions()).toEqual([]);
     });
   });
 
@@ -119,7 +125,14 @@ describe('useActionEngine', () => {
   });
 
   describe('handleShortcut', () => {
-    it('handles registered keyboard shortcut', async () => {
+    // Deliberately INVERTED, for the same reason as getBulkActions above:
+    // `sampleActions` still declares the stale `shortcut: 'ctrl+k'`, which
+    // spec 17 retired. Its tombstone is explicit that nothing ever consumed it
+    // ("no keydown listener feeds ActionEngine.getShortcuts(), and objectui's
+    // keyboard stack is hand-registered and never consults action metadata"),
+    // so harvesting it only kept a dead path looking alive. A host that wants
+    // a shortcut still passes one to `registerAction` explicitly.
+    it('does not harvest the retired shortcut key from metadata', async () => {
       const { result } = renderHook(() =>
         useActionEngine({ actions: sampleActions }),
       );
@@ -129,8 +142,7 @@ describe('useActionEngine', () => {
         shortcutResult = await result.current.handleShortcut('ctrl+k');
       });
 
-      expect(shortcutResult).not.toBeNull();
-      expect(shortcutResult.success).toBe(true);
+      expect(shortcutResult).toBeNull();
     });
 
     it('returns null for unregistered shortcut', async () => {