# v4928.1.5.85 — Operator audit quality follow-ups

Incremental correction after running the operator-page consistency audit in production.

## Corrections

- Treat known Odoo logistics-only lines such as `Delivery_007` / `Standard delivery` as non-billable delivery lines.
  - These no longer raise `MEDIUM` as possible missing Jasmin invoice lines.
  - They become `LOW` informational findings by default, or can be suppressed with `--suppress-non-billable-delivery-warnings`.
  - Additional patterns can be configured with `CLIENTFLOW_NON_BILLABLE_ODOO_LINES` or repeated `--non-billable-delivery-pattern` flags.
- The audit no longer reports future-due completed tasks once the repair script has explicitly acknowledged them as completed early.
- The audit no longer reports “invoice sent task done but document status not sent” once the document payload has ClientFlow invoice-sent evidence.

## Repair script additions

`dispatch/repair_operator_page_consistency_findings.py` equivalent behavior in `scripts/repair_operator_page_consistency_findings.py` can now safely normalize low-severity noise:

- `--fix-future-done-task-notes`: adds note/metadata to tasks completed before their planned follow-up date.
- `--fix-invoice-sent-evidence`: stores ClientFlow evidence on invoice documents when a `SEND_INVOICE` task is already done.

Default mode includes these safe low-severity repairs together with the existing safe task cleanup. It still only reports, and never automatically fixes, delivered-without-payment cases.

## Tests

- Added static regression checks for non-billable delivery-line handling.
- Added static regression checks for low-severity normalization and critical-payment safety guard.
