A code task whose title/description hit a board keyword (launch, release,
architecture, security) was classified to 'board' — so a cell dev code task
got 'reviewed' by the Product Owner + Head of Marketing — and a high-complexity
cell code task was escalated to 'main_pm', which is how a PM ended up owning
(and deadlocking) a dev code task. A code task that belongs to a cell
(backend/frontend/ux_ui) is implementation work: route it WITHIN the cell
(cell_pm for high/pm-keyword, else dev), never to board/main_pm. The strategic
board/cross-cell heuristics now apply only to team-less top-level tasks.
