fix(google-vault): isolate stale-value-prone subblocks per operation

Cursor Bugbot: consolidating shared subblocks across operations left two
cross-contamination risks since a stale value from one operation stays in
block state until overwritten:

- accountEmails/orgUnitId are checked emails-first with silent either/or
  priority; sharing them across update_matters_holds and create_saved_query
  meant a leftover value from a different operation could silently override
  the intended scope. Gave both operations dedicated fields
  (updateHoldAccountEmails/updateHoldOrgUnitId, savedQueryAccountEmails/
  savedQueryOrgUnitId), remapped in tools.config.params.
- matterId presence alone switches google_vault_list_matters between
  list-all and single-get. Sharing it with every other operation meant a
  leftover matterId could silently turn "List Matters" into a single-matter
  fetch. Gave list_matters its own optional listMatterId field.

create_matters_holds/create_matters_export keep sharing accountEmails/
orgUnitId as before this PR (pre-existing behavior, not introduced here).

Author: waleedlatif1

apps/sim/blocks/blocks/google_vault.ts

@@ -88,7 +88,6 @@ export const GoogleVaultBlock: BlockConfig = {
           'delete_matters_holds',
           'add_held_accounts',
           'remove_held_accounts',
-          'list_matters',
           'update_matters',
           'close_matters',
           'reopen_matters',
@@ -127,6 +126,16 @@ export const GoogleVaultBlock: BlockConfig = {
         ],
       }),
     },
+    // Dedicated optional matter-id filter for list_matters — kept separate from the
+    // required matterId above so a value left over from another operation can never
+    // silently turn "List Matters" into a single-matter get.
+    {
+      id: 'listMatterId',
+      title: 'Matter ID',
+      type: 'short-input',
+      placeholder: 'Enter Matter ID (optional to fetch a specific matter)',
+      condition: { field: 'operation', value: 'list_matters' },
+    },
     // Download Export File inputs
     {
       id: 'bucketName',
@@ -228,12 +237,7 @@ Return ONLY the hold name - no explanations, no quotes, no extra text.`,
       placeholder: 'Comma-separated emails (alternative to Org Unit)',
       condition: {
         field: 'operation',
-        value: [
-          'create_matters_holds',
-          'update_matters_holds',
-          'create_matters_export',
-          'create_saved_query',
-        ],
+        value: ['create_matters_holds', 'create_matters_export'],
       },
     },
     {
@@ -243,14 +247,42 @@ Return ONLY the hold name - no explanations, no quotes, no extra text.`,
       placeholder: 'Org Unit ID (alternative to emails)',
       condition: {
         field: 'operation',
-        value: [
-          'create_matters_holds',
-          'update_matters_holds',
-          'create_matters_export',
-          'create_saved_query',
-        ],
+        value: ['create_matters_holds', 'create_matters_export'],
       },
     },
+    // Dedicated scope fields for update_matters_holds and create_saved_query — kept
+    // separate from the create_matters_holds/create_matters_export accountEmails/orgUnitId
+    // above so a stale value left over from a different operation can never silently win
+    // in the accountEmails-before-orgUnitId scope priority (each field is only ever
+    // populated by the user while its own operation is selected).
+    {
+      id: 'updateHoldAccountEmails',
+      title: 'Account Emails',
+      type: 'long-input',
+      placeholder: 'Comma-separated emails (alternative to Org Unit)',
+      condition: { field: 'operation', value: 'update_matters_holds' },
+    },
+    {
+      id: 'updateHoldOrgUnitId',
+      title: 'Org Unit ID',
+      type: 'short-input',
+      placeholder: 'Org Unit ID (alternative to emails)',
+      condition: { field: 'operation', value: 'update_matters_holds' },
+    },
+    {
+      id: 'savedQueryAccountEmails',
+      title: 'Account Emails',
+      type: 'long-input',
+      placeholder: 'Comma-separated emails (alternative to Org Unit)',
+      condition: { field: 'operation', value: 'create_saved_query' },
+    },
+    {
+      id: 'savedQueryOrgUnitId',
+      title: 'Org Unit ID',
+      type: 'short-input',
+      placeholder: 'Org Unit ID (alternative to emails)',
+      condition: { field: 'operation', value: 'create_saved_query' },
+    },
     // Date filtering for exports (works with all corpus types)
     {
       id: 'startTime',
@@ -665,6 +697,11 @@ Return ONLY the description text - no explanations, no quotes, no extra text.`,
           holdTerms,
           heldAccountEmails,
           heldAccountIds,
+          listMatterId,
+          updateHoldAccountEmails,
+          updateHoldOrgUnitId,
+          savedQueryAccountEmails,
+          savedQueryOrgUnitId,
           ...rest
         } = params
         return {
@@ -676,6 +713,13 @@ Return ONLY the description text - no explanations, no quotes, no extra text.`,
           ...(holdTerms && { terms: holdTerms }),
           ...(heldAccountEmails && { accountEmails: heldAccountEmails }),
           ...(heldAccountIds && { accountIds: heldAccountIds }),
+          // Map operation-scoped fields (kept separate in the UI so a stale value from
+          // another operation can never silently override these) to their tool parameter names
+          ...(listMatterId && { matterId: listMatterId }),
+          ...(updateHoldAccountEmails && { accountEmails: updateHoldAccountEmails }),
+          ...(updateHoldOrgUnitId && { orgUnitId: updateHoldOrgUnitId }),
+          ...(savedQueryAccountEmails && { accountEmails: savedQueryAccountEmails }),
+          ...(savedQueryOrgUnitId && { orgUnitId: savedQueryOrgUnitId }),
         }
       },
     },
@@ -745,6 +789,27 @@ Return ONLY the description text - no explanations, no quotes, no extra text.`,
     // Saved query inputs
     displayName: { type: 'string', description: 'Name for the saved query' },
     savedQueryId: { type: 'string', description: 'Specific saved query ID to fetch or delete' },
+
+    // Operation-scoped fields kept separate from their shared counterparts above so a
+    // stale value from another operation can never silently carry over
+    listMatterId: { type: 'string', description: 'Specific matter ID to fetch (list_matters)' },
+    updateHoldAccountEmails: {
+      type: 'string',
+      description: 'Comma-separated emails covered by the hold (update_matters_holds)',
+    },
+    updateHoldOrgUnitId: {
+      type: 'string',
+      description: 'Org unit ID covered by the hold (update_matters_holds, alternative to emails)',
+    },
+    savedQueryAccountEmails: {
+      type: 'string',
+      description: 'Comma-separated emails to scope the saved query (create_saved_query)',
+    },
+    savedQueryOrgUnitId: {
+      type: 'string',
+      description:
+        'Org unit ID to scope the saved query (create_saved_query, alternative to emails)',
+    },
   },
   outputs: {
     matters: {