Rooster Performance

"What Rooster has done for ME" -- the desk's own panel (Frederick, 2026-08-09, drawing the line against the department-wide read on Analytics): "On the desk, Rooster should be talking about what he's done for you. On analytics, Rooster should be talking about what he's done for the entire customer service department. Two different data points." See supervisor_service.PersonRoosterStat's own docstring for exactly what is counted and, as importantly, what was deliberately left out as not honestly computable.

NO GRANT GATE, same reasoning as GET /needs-you (2026-08-09, folding that endpoint's own fix in here too): tickets assigned to this caller by id count regardless of any grant or role (the Keith Bowdle shape). A caller with no queue membership and nothing Rooster has touched for them gets honest zeros, never a 403.

pool_kinds IS QUEUE MEMBERSHIP, NOT VERTICAL VISIBILITY -- same same-day correction as GET /needs-you above, and the same underlying conflation: _allowed_kinds (holds tickets:b2c/tickets:b2g) used to scope the shared-pool half of this count too, which would have counted every b2c ticket ever as "your pool" for anyone merely holding tickets:b2c visibility -- a fulfillment technician (both verticals by default since migration 0137) included, not just a Sales Manager. See registry.QUEUE_MEMBERSHIP_ROLES's own docstring for the full argument; the owner (admin:people:read) is the same deliberate ADDITION-not- replacement GET /needs-you uses -- registry.owner_bypass_ticket_kinds, never a kind the caller does not separately hold tickets:b2c/tickets:b2g for (2026-08-11 fix, Cindy Palma: see GET /needs-you's own docstring for the full incident).