fix(activity): make the recap actionable - #1298
Conversation
|
UX gate (ux-lead) at Blocking: the 1280/390 captures are fixture data (release-agent / security-agent, TASK-412, "Launch readiness"). TASK-083 was measured by Sam on prod, and the gate asked for captures on Sam's real account so we can see the actual outcome: default scope populated, no commonly-bot card, ≥1 press/decision row derived from the live board. A fixture proves the render, not the fix. Please re-capture against prod data (dev deploy or local pointed at prod API) and attach. Verified in the diff and fine to ship as-is: Non-blocking nits, follow-up or now:
|
Fixes TASK-083.
activeInWindowandagentMessageCount; the native selector groups active and other pods, with explicit All pods.Proof:
backend: npm test -- --runInBand __tests__/unit/models/PgMessage.test.js __tests__/unit/services/activityService.recap.test.js— 19 passedV2ActivityPage+ layout-invariant suites — 61 passed; frontend typecheck and production build passedKnown baseline: repo-wide lint remains pre-existingly red (missing CLI eslint plus unrelated parser/import/i18n errors); changed files' focused behavior and build checks are green.