Skip to content

Show seeded daily tasks in Operations Home today queue #73

Description

@alexeygrigorev

Show seeded daily tasks in Operations Home today queue

Status: in progress
Tags: bug, portal, frontend, work-engine, P0
Depends on: #70, #72
Blocks: #71 final V1 cutover acceptance

Scope

Fix the deployed Operations Home so production-safe seeded daily tasks appear in the operator's Today queue under portal auth.

Current production state after deploy run 28331121553:

  • /work/api/tasks?status=todo returns two tasks dated 2026-06-28 assigned to the seeded operator user Grace.
  • /work/api/notifications returns two recurring-due notifications for those tasks.
  • The browser-rendered /work page after portal login shows 0 today and No live tasks assigned to you or unassigned due today.
  • The same tasks appear only as Process Quality blockers because they lack process instructions.

The V1 Operations Home must help the operations manager see what needs action today. A task may also have a process-quality warning, but that warning must not hide the task from daily work surfaces.

Acceptance Criteria

  • After portal login, /work shows seeded due todo tasks in the Today section even when the browser actor is the synthetic portal-admin and the tasks are assigned to a real seeded operator user.
  • The Operations Home summary count includes those tasks as today work.
  • Tasks with missing process instructions can still be listed as process-quality blockers, but they remain visible and actionable in the Today queue.
  • The fix preserves real-user filtering when a real operator user is selected or available; it must not broadly hide assigned work in portal mode.
  • Production smoke after deploy records /work/api/tasks?status=todo count, /work/api/notifications count, and browser evidence that the two seeded daily tasks are visible in Operations Home.

Test Scenarios

Scenario: Synthetic portal actor opens daily work

Given: /work/api/me returns portal-admin, /work/api/users returns seeded real operators, and /work/api/tasks?status=todo returns tasks assigned to Grace due today.
When: the operator opens /work after portal login.
Then: the Today section and summary count include those tasks instead of showing 0 today.

Scenario: Missing process instructions do not hide work

Given: a due todo task has no instructionDocId and no instructionsUrl.
When: Operations Home renders.
Then: the task appears in Today and may also appear under Process Quality as a blocker.

Scenario: Real user scoping remains valid

Given: the UI has a real selected operator user.
When: Operations Home filters assigned work.
Then: it still includes tasks assigned to that operator and unassigned shared work, and does not show unrelated real-user work as assigned-to-me work.

Required Verification

  • Focused unit/static tests for the affected frontend/work-engine surface.
  • npm --prefix work-engine run typecheck if work-engine TypeScript is touched.
  • Relevant frontend/docs tests if frontend/ or Python portal behavior is touched.
  • Browser evidence for /work showing the seeded daily tasks after portal login.
  • After push, On-Call verifies Deploy DataOps V1 Lambda is green and production browser/API smoke passes.

Out of Scope

  • Changing the recurring seed task definitions unless needed for today visibility.
  • Removing process-quality blockers.
  • Running real Trello import, Telegram assistant smoke, or other Coordinate V1 production cutover and human-gate closeout #71 human gates.
  • Treating portal-admin as a permanent real operator identity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0Must havebugSomething is brokenfrontendFrontend UIportalShared portal shell and UXtestingTests and QAwork-engineDataTasks task execution engine

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions