859a32773847049f00522c40c6f50572fc14a25d
A "Ready for X" gating step (fp.step.kind code='gating') maps to area_kind='receiving' in the taxonomy. For a MID-recipe gate (e.g. "Ready for processing" between Racking and Plating) that snapped the job's card back to the far-left Receiving column when work advanced into it — the job looked like it vanished from the board. _compute_area_kind now detects gating via the stable kind code and resolves a gating step's column to the NEXT non-gating step's area (so "Ready for processing" shows in Plating), keeping cards flowing left→right. Falls back to the last real stage for a trailing gate. Non-gating steps unchanged. Helpers: _fp_is_gating_step / _fp_raw_area_kind (no recursion) / _fp_resolve_area_kind. area_kind is a stored compute — recomputed all 537 live steps on entech. Verified: WO-30061 "Ready for processing" area receiving→plating, card now renders in the Plating column. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Description
Odoo 19 custom modules
Languages
Python
57.7%
HTML
23.9%
JavaScript
14.9%
SCSS
2.2%
CSS
0.8%
Other
0.4%