Surface batch-apply consequences in the action UI

[ndisidore]

Stacked on #241. Phase-1 frontend stopgap for the batch applyActionsThrough semantics — RPC signatures are unchanged (approveAction(id) / rejectAction(id); the frontier semantics live behind approveAction), which is what keeps Phase 2's batch-review UI a UI-only change.

• "+N earlier" hint on Approve buttons (Activity review pane, chat action cards, header notifications popover): approving an action now also applies every earlier pending action from the same gatekeeper connection, so the button says so. Count comes from the already-subscribed local action list (countEarlierPending).
• failure: when a batch pass stops at an action, its pending card shows the gatekeeper's display-safe reason (Activity review card, chat inline row and blocking callout). The existing useResolveAction failure toast is unchanged.
• cascadedFrom: rejected entries invalidated by another action's veto show "Invalidated by rejection of '{title}'" (title from the local list, generic fallback) in the Activity history details and the chat card's expanded view.

Optimistic resolve state is untouched — batch-decided sibling records arrive via the subscribeToActions subscription.

Tested with pnpm build, pnpm test, pnpm lint:check.

[ask-bonk]

github run

[ask-bonk]

@ndisidore Bonk workflow failed. Check the logs for details.

View workflow run · To retry, trigger Bonk again.

[ask-bonk]

github run