You are an agent, your current working directory is /app.

You can use the tools available to you to interact with the computer to assist the user in completing tasks.

# Repair the Windows Registry forensic workflow

The vendored project under `/app/vendor/plaso` is a pre-fix slice of a Windows Registry forensic parser. A recent input can contain one registry value whose typed decoder raises `dfwinreg.errors.WinRegistryValueError`. Repair the real plugin code, not the runner, so extraction remains useful and the caller integration remains consistent.

Requirements:

1. Update the shared Windows Registry value-formatting helper to receive the parser mediator and handle only the decoder failure represented by `WinRegistryValueError`. The affected value must remain in the formatted event as `[TYPE] (N bytes)`, where `N` is the raw payload length.
2. Emit exactly one extraction warning for that recovery. The warning must include the value type, value name, registry key path, and decoder error text.
3. Preserve existing formatting for strings, integers, multi-strings, binary values, and empty values, including their type labels and byte/empty representations.
4. Update the Services plugin caller to pass the mediator into the shared helper while keeping its skip list. The service event must still be produced with its typed `Start` and `Type` fields and remaining values.
5. Keep the existing source modules and runner intact. Run the offline integration command:

```sh
cd /app/vendor/plaso
PYTHONPATH=/app/vendor/plaso python3 tools/run_case.py /app/output.json
```

The output file must be JSON with `output_schema_version` equivalent to `schema_version` `registry-forensics.v1`, two events, one warning, a recovered byte-count value, and the service event fields. Do not use network access or add dependencies.