fix(provenance): report where the guard tripped on a refusal too

The registry retained the first guard's location, but the refusal
reporter copies named fields out of the diagnostics and never picked it
up — so the line an operator actually reads when a projection is refused
still named only the reason.

Nested rather than spread flat: the guard's `inputPath` names where it
tripped and the refusal's names where the refusal happened, which differ
whenever a latch travels, so flattening would overwrite one with the
other.

Author: icecrasher321

apps/sim/executor/utils/resolved-secret-projection-refusal.test.ts

@@ -79,6 +79,34 @@ describe('refuseResolvedSecretProjection', () => {
     )
   })
 
+  /**
+   * The reason says what tripped; without the location a reader still has to go hunting for which
+   * block. Nested rather than flattened because the guard's own `inputPath` and the refusal's name
+   * different places once a latch has travelled.
+   */
+  it('reports where the first guard tripped, not only what it was', () => {
+    const registry = new ResolvedSecretTraceRegistry([], scope)
+    registry.markIncomplete('structural-input-root-unprojected', {
+      detail: { blockType: 'table', tool: 'table_insert_row', inputPath: 'data' },
+    })
+
+    expect(() =>
+      refuseResolvedSecretProjection({
+        site: 'agent.toolCallCrossing',
+        message: 'Tool call could not be safely projected',
+        registry,
+        inputPath: 'messages',
+      })
+    ).toThrow()
+
+    expect(refusalRecords()[0][1]).toEqual(
+      expect.objectContaining({
+        inputPath: 'messages',
+        detail: { blockType: 'table', tool: 'table_insert_row', inputPath: 'data' },
+      })
+    )
+  })
+
   it('names a by-design origin that was silenced when it was marked', () => {
     const registry = createIncompleteResolvedSecretTraceRegistry(scope)
     expect(mockLogger.error).not.toHaveBeenCalled()

apps/sim/executor/utils/resolved-secret-projection-refusal.ts

@@ -71,6 +71,16 @@ function reportRefusal({ site, registry, inputPath }: ResolvedSecretProjectionRe
           ...(diagnostics.scopeWorkspaceId
             ? { scopeWorkspaceId: diagnostics.scopeWorkspaceId }
             : {}),
+          /**
+           * Where the first guard tripped — the block, tool and input path that cost the run its
+           * completeness, which is what a reader needs to go and fix.
+           *
+           * Nested rather than spread flat: its `inputPath` names where the guard tripped, while
+           * this line's own `inputPath` names where the refusal happened. Those are different
+           * places whenever a latch travels, and flattening would silently overwrite one with the
+           * other.
+           */
+          ...(diagnostics.detail ? { detail: diagnostics.detail } : {}),
         }
       : {}),
   })