feat(schedule-actions): add confirmation modal and mutation flow

[Assem-Uber]

Summary

• Adds the schedule-actions modal shell with confirmation flow, mutation, snackbar feedback, and query invalidation.
• Mirrors the workflow-actions modal pattern: form slot, optional banner, submit/cancel, and error banner on API failure.

Changes

• schedule-actions-modal/ — modal wrapper (900px width, mounts modal content)
• schedule-actions-modal-content/ — react-hook-form + TanStack mutation, banner slot, initialFormValues support
• schedule-actions.types.ts — remove unused formData from ScheduleActionFormProps

Testing

• npm run test:unit:browser -- schedule-actions-modal-content (4 tests)
• npm run test:unit:browser -- schedule-actions-modal (2 tests)

Stack

• Depends on: feat(schedule-actions): add action types, config, and menu #1419
• Follow-up: Assem-Uber:feat/schedule-actions-mount

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Implements the schedule-actions modal and mutation flow, incorporating robust validation and dynamic feature flagging. The race condition allowing early action triggering has been resolved.

✅ 1 resolved

✅ Edge Case: Actions clickable before schedule loads, skipping runnable check

📄 src/views/schedule-actions/schedule-actions-menu/schedule-actions-menu.tsx:18-23 📄 src/views/schedule-actions/schedule-actions-menu/helpers/get-action-disabled-reason.ts:20-22
In schedule-actions-menu.tsx, getActionDisabledReason is called with actionRunnableStatus: schedule ? action.getRunnableStatus(schedule) : undefined. When the schedule is still loading (schedule undefined) but the enabled-config is 'ENABLED', getActionDisabledReason returns undefined (see get-action-disabled-reason.ts lines 20-22: if (!actionRunnableStatus) return undefined). This means the button is rendered enabled and clickable before the schedule has loaded, so the runnable-status gate (e.g. 'already paused' / 'not paused') is bypassed. A user could trigger Pause/Resume against a schedule whose real state hasn't been resolved yet. Impact is limited since the backend still validates, but consider disabling the actions (or omitting the menu) until schedule is available.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}