# v4928.1.5.62 — Task Schema Hotfix

This release fixes a production regression introduced by the v1.5.61 task fiscal inheritance change.

## Root cause

Production schema stores the fiscal customer link on opportunities as `local_customer_id`. The task detail query tried to read `o.fiscal_customer_id`, which does not exist in the production database, causing HTTP 500 on task detail pages.

## Changes

- `app/task_service.py`
  - joins customers through `o.local_customer_id` only;
  - exposes `opportunity_fiscal_customer_id` as an alias of `local_customer_id` for compatibility with UI code.
- `app/opportunity_next_action_service.py`
  - maps `local_customer_id` to the workflow engine's internal `fiscal_customer_id` alias;
  - uses production customer columns (`street_name`, `postal_zone`, `city_name`) with normalized aliases for the engine.
- Adds static regression tests to prevent reintroducing non-existing `opportunities.fiscal_customer_id` SQL.

## Validation

`346 passed`