01a46e33e2
Two issues on the Process Tree client action: 1. Back to Work Order kept growing breadcrumbs (WO -> Tree -> WO -> Tree -> ...) because onBack used action.doAction() which PUSHES a new act_window onto the stack instead of popping. Fixed by trying action.restore() first (pops the Tree off the stack and returns to the parent WO/Step controller). Falls through to explicit doAction only when there's no parent in the stack (direct URL access). 2. The empty-state banner referenced productionId, a dead variable from the bridge_mrp era when the tree was tied to mrp.production. Since the component now uses jobId (fp.job context key), the "No manufacturing order selected" message ALWAYS fired regardless of whether a job was loaded. Fixed by using jobId and updating the message to "No work order selected". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>