eb1fd50add
The plant-view rollout left two legacy ir.actions.client data records still claiming tag='fp_shopfloor_landing': - action_fp_plant_overview (Plant Overview) - action_fp_shopfloor_tablet (Shop Floor — Tablet Station) The landing-action resolver dispatched the new view correctly when the user clicked the Plating root menu, but bookmarks / breadcrumbs / QR-scan landings / direct URLs still routed through these legacy actions and loaded the per-step kanban (OWL component is still registered for back-compat). Flipping their tag to fp_plant_kanban means every entry point now opens the new view. The legacy fp_shopfloor_landing OWL component stays registered (no code removed) but no XMLID points at it anymore — safe to delete in a future cleanup. Also documented this as a durable convention in CLAUDE.md under 'Legacy-action redirect (general rule for OWL component swaps)'. Verified on entech: - action 1129 (Shop Floor) tag: fp_shopfloor_landing → fp_plant_kanban - action 1133 (Plant Overview) tag: fp_shopfloor_landing → fp_plant_kanban - 3 stale asset bundles cleared - Module re-upgraded clean, registry rebuilt in 15.7s Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>