# Driver-working-time Esper contract refactoring

This patch removes tachograph-prefixed Esper contract names from the active source-neutral driver-working-time pipeline without changing processing behavior.

## New canonical Esper contracts

- `DriverWorkingTimeActivityPointInputEvent`
- `DriverWorkingTimeVehicleUsagePointInputEvent`
- `DriverWorkingTimeActivityIntervalInputEvent`
- `DriverWorkingTimeVehicleUsageIntervalInputEvent`
- `DriverWorkingTimeSupportEvidenceInputEvent`
- `DriverWorkingTimeProjectionFinalizeEvent`
- `DriverWorkingTimeVehicleUsageIntervalInputWindow`

`DriverWorkingTimeEsperContractNames` centralizes these names for Java-side registration, event sending, cleanup, and future common modules.

## Updated active common components

- `DriverWorkingTimeReusableProjectionBuilder`
- `driver-working-time-derived-projections.epl`
- `runtime-driver-event-interval-preprocessor.epl`
- runtime cleanup query for the vehicle-usage input window
- contract and cleanup regression tests
- runtime-processing documentation

## Compatibility

The tachograph-specific legacy resources and file-session compatibility code are intentionally not renamed. They remain isolated compatibility artifacts. No public request/response DTO, module key, plan key, or business rule is changed.

## Validation

- Verified that active common Java/EPL files contain no legacy tachograph input-contract names.
- Verified that all public named windows still have cleanup coverage.
- Compiled the new contract-name class with `javac`.
- Maven tests were not run because Maven and a Maven wrapper are unavailable in the environment.