## Why

The manager-facing overtime list (`GET /api/v1/employee/overtime_requests`) says nothing about who a request covers. A manager scanning the month sees titles, dates and statuses, and has to open each request to find out whose overtime it is. The administrator's equivalent at least reports how many employees a request holds; the manager's reports neither the count nor the employees.

The client wants to show a row's employees as a row of small round avatars, each naming its employee on hover — the shape used elsewhere for "who is in this". For that it needs the employees themselves, not just a number.

## What Changes

- The manager's overtime list reports, for each request, a short preview of the employees it covers and the total number of them. The preview is capped at ten; the count is the real total, so a request covering more reads as ten faces and a remainder.
- Each previewed employee carries what the avatar needs and nothing else: the employee's name, their avatar, and their employee code for the hover label.
- **The preview covers only the manager's own employees.** A manager reaches a request when it holds at least one of their employees, and such a request may hold others; those others are neither previewed nor counted. A whole-roster reading was tried first and reversed by `fix-overtime-manager-scope`; see design.
- No new filters. The two the client asked for are already served by this endpoint: `q` matches an employee's name or code (and the request title), and `from`/`to` select by the date the overtime falls on. Both are documented here so the client knows what to send.

No breaking changes: two fields are added to each row of one listing, and nothing existing is altered.

## Capabilities

### New Capabilities
- `overtime-request-employee-preview`: what the manager's overtime list reports about the employees a request covers — the capped preview, the total, whose employees are included, and which filters already narrow the list.

### Modified Capabilities

None. The only specified overtime capability, `overtime-request-workday-input`, belongs to a change that has not been archived; the scope correction this change prompts is being made there rather than here.

## Impact

**Controllers**
- `app/Http/Controllers/Api/V1/Employee/OvertimeRequestController.php` — `index()` gains the preview and the count, and its OpenAPI annotation gains the filters it already honours.

**Models**
- `app/Models/OvertimeRequest.php` — a light relation or loader for the preview. The existing `accounts()` relation eager-loads `simple_employee_detail`, which carries positions, departments and companies, and is far more than a row of avatars needs.

**Depends on**
- `add-overtime-workday-input` task 7.11, which drops the employee restriction from the manager's two summary figures. Without it the tile would count a subset of the employees this list shows.

**Not in scope**
- The administrator's screens. They already report `accounts_count`; adding the preview there is its own task.
- Changing who a request counts as covering. Employees who have left keep counting, as they do everywhere today — they are marked `quit_job`, not deleted, and the record is historical. See Decision 6 of design.md.
- Any new filter parameter. Both filters asked for already exist.
