## Why

An overtime request is always entered as a time range: an admin or manager supplies `from` and `to`, and the system derives the overtime duration from them, then converts that duration into overtime workday by applying the company's overtime ratio for that date.

Customers have asked for a second way in. On a day when a team works late with ragged timings — some arriving early, some leaving late, nobody with clean clock data to justify a range — a manager wants to credit each person a fixed amount of overtime workday and be done with it. The two things that make the current flow unusable in that situation are that it forces start and end times nobody can state honestly, and that whatever is entered is then multiplied by a ratio, so the manager cannot say what the result will be.

What the customer asks for is to state the final figure: *this person gets 5 hours of overtime workday for that day, regardless of the ratio and regardless of when they came or left*.

## What Changes

- Overtime requests gain an input mode. The existing mode, now named `time_range`, is unchanged and remains the default. The new mode, `workday`, takes a date and an amount of overtime workday instead of a time range, and like the existing mode accepts several entries in one submission.
- **An overtime request entered in `workday` mode deliberately bypasses the overtime ratio.** The amount entered is the amount credited, whether the date is an ordinary day, a day off or a public holiday. This is the point of the feature, and it is a departure from how every other overtime record behaves.
- The amount is entered in the `HH:MM` form already used for every other duration field in the system, and means hours *of overtime workday*, not hours worked. Five hours entered is five hours of overtime workday — on an ordinary day the same credit a time-range request of about 3h20m would produce at a ratio of 1.5.
- Both modes contribute to the same day's timesheet and are summed. A day may hold any mix of the two.
- Overlap checking stays exactly as it is, but applies only between `time_range` requests. A `workday` request is never checked against anything and never blocks anything: it has no time range to overlap with, and the customer wants to be free to add several on one day.
- The minimum-duration guard (`min_minutes_recognized`) still applies. For a `workday` request the entered amount is converted back to an overtime duration at validation time, using the ratios in force at that moment, and the request is refused if that duration falls below the configured minimum. Nothing derived at validation time is stored.
- The timesheet continues to report an overtime duration in hours for display, reporting and the overtime-to-annual-leave conversion. For the `workday` portion that figure is derived during timesheet calculation from the ratios then in force, so it never goes stale, and it is never persisted on the request.
- The monthly summary on the overtime request screens reports the `workday` total as its own figure alongside the existing duration total, rather than folding one into the other.

No breaking changes. Every existing overtime request is a `time_range` request and behaves exactly as before.

## Capabilities

### New Capabilities
- `overtime-request-workday-input`: the two input modes of an overtime request, what each one stores, how overlap checking and the minimum-duration guard apply to each, how both modes combine into a day's overtime workday and overtime duration, and how the monthly summary reports them.

### Modified Capabilities

None. No capability currently specified under `openspec/specs/` covers overtime requests or timesheet overtime calculation.

## Impact

**Database**
- `overtime_requests.input_mode` — enum-style string, default `time_range`. Existing rows become `time_range`.
- `overtime_requests.total_workday` — decimal, minutes-of-workday, the same unit `timesheets.overtime_workday` already uses. Null or zero for `time_range` requests.
- `overtime_requests.to` is already nullable; no change needed. `from` carries the date for both modes and remains required, because `OvertimeRequest::filterByDate()` anchors a request to a timesheet with `whereDate('from', ...)`.

**Models**
- `app/Models/OvertimeRequest.php` — fillable, accessor/mutator pair for `total_workday` mirroring the existing `total_time` pair, mode-scoped query helpers, and a second aggregate alongside `getTotalOvertimeByAccount()`.

**Timesheet calculation**
- `app/Classes/TimesheetCalculator.php` — `handleOvertime()` adds the `workday` total directly to `overtime_workday` without applying the ratio, and derives the matching duration for `overtime`. This is the only place the conversion between the two units happens.

**Controllers**
- `app/Http/Controllers/Api/V1/Admin/OvertimeRequestController.php` — `store()` accepts the new mode; `getSummary()` reports the new total.
- `app/Http/Controllers/Api/V1/Employee/OvertimeRequestController.php` — same, for the manager-facing endpoints.
- Overlap checks at all three call sites must be narrowed to `time_range` requests.

**Notifications**
- `app/Mail/OvertimeRequestApproved.php`, `OvertimeRequestCancelled.php` and the two matching listeners build a `"HH:MM - HH:MM, <day> <date>"` string from `from`/`to`. A `workday` request has no range, so these need a variant that states the date and the amount.

**Language files**
- `resources/lang/*/overtime.php` — messages for the new validation failures.

**Not in scope**
- The ratio settings themselves (`overtime_ratio`, `overtime_day_off_ratio`, `overtime_holiday_ratio`) are untouched. They continue to govern `time_range` requests.
- `PUT /admin/timesheets/{id}/adjust-overtime` is left alone. It writes an overtime figure straight onto a timesheet, is already hidden in the UI, and is wiped by the next recalculation. Removing it is tracked separately.
- No change to how timesheet rows come into existence. An overtime request of either mode only reaches payroll once a timesheet row exists for that account and date; this is existing behaviour and is recorded as a known limitation in design.md.
- No cap on how much overtime workday may be entered for one person on one day. The customer wants to sum whatever is entered and validate it themselves.
