Fix daily queue table wrapping and overlap in V1 dashboard

[alexeygrigorev]

Fix daily queue table wrapping and overlap in V1 dashboard

Status: pending
Tags: bug, work-engine, frontend, design, P1
Depends on: #57
Blocks: None

Scope

The #57 Designer acceptance pass found that the work-engine Operations Home daily queue technically shows the right groups, but the desktop table is too cramped for real operator use. Headers, bundle badges, info copy, and proof controls wrap or collide in narrow columns, making next actions harder to scan.

Evidence:

• .tmp/screenshots/issue-57/desktop-work-engine-operations-home-daily-queue.png
• .tmp/screenshots/issue-57/mobile-pixel7-work-engine-operations-home-daily-queue.png

Observed examples:

• DESCRIPTION header wraps as DESCRIPTIO N.
• Bundle badge and info text visually collide in several task rows.
• Required-link and action columns compress to tiny fragments such as U, -, or Follow-up controls placeholders.
• Desktop table layout does not meet the design-system goal for dense but readable operational rows.

Acceptance Criteria

• Desktop daily queue rows can show date, description, workflow, status/proof, assignee, required proof, and next action without text overlap or clipped one-letter controls.
• Queue groups remain visually distinct: Follow-ups due, Overdue, At risk, Today, Waiting.
• Required link/file/artifact controls remain usable at normal desktop widths.
• Pixel 7 stacked rows preserve labels and touch targets without introducing horizontal overflow.
• Screenshot evidence is captured for desktop and Pixel 7 Operations Home.

Suggested Verification

• Run the work-engine browser flow with representative due, overdue, waiting/follow-up, and missing-proof tasks.
• Capture desktop and Pixel 7 screenshots of Operations Home.
• Run relevant work-engine frontend/E2E checks.

[alexeygrigorev]

Software Engineer handoff for #61

Summary:

• Reworked the Operations Home daily queue from the old eight-column fixed table into a denser seven-column queue: Date, Task/workflow, Status/Proof, Assignee, Required Proof, Next Action.
• Added dashboard-specific grid sizing for desktop rows, full-width queue group/action rows, stacked proof controls, wider dashboard shell, and mobile overrides that keep Pixel 7 rows card-stacked without horizontal overflow.
• Added a focused Playwright regression that seeds follow-up due, overdue, at-risk, today, and waiting rows and asserts readable desktop controls plus Pixel 7 no-overflow behavior.

Changed files:

• work-engine/src/public/app.js
• work-engine/src/pages/index.html
• work-engine/e2e/home-dashboard.spec.js
• work-engine/tests/home-dashboard.test.ts

Screenshots:

• .tmp/screenshots/issue-61/desktop-work-engine-operations-home-daily-queue.png
• .tmp/screenshots/issue-61/mobile-pixel7-work-engine-operations-home-daily-queue.png

Verification:

• PASS npm --prefix work-engine test — 677 passed
• PASS npm --prefix work-engine run typecheck
• PASS npm --prefix work-engine run build
• PASS npx playwright test e2e/home-dashboard.spec.js -g "Dashboard daily queue layout keeps dense operational rows readable" — 1 passed
• PASS npx playwright test — 308 passed
• PASS git diff --check

Notes:

• An initial focused E2E attempt hit a shared port collision with another worktree on 3001; rerun passed after the port was free.
• No source repos outside dataops were modified. No commit made.

Ready for Tester and Designer review.

[alexeygrigorev]

DESIGN PASS — #61

Role: Designer
Route inspected: work-engine Operations Home daily queue (/#/)
Viewport coverage: desktop 1440x1000; Pixel 7 412x915

Verdict: PASS

Checks:

• Desktop daily queue rows are dense but readable: date, task/workflow, status/proof, assignee, required proof, and next action remain scannable without the Run unified V1 operator UX acceptance pass across daily workflows #57 one-letter/control collision defects.
• Headers no longer wrap badly; Required Proof and Next Action stay readable at desktop width.
• Required proof controls and proof/action columns remain usable; waiting follow-up controls move into full-width rows with usable button/input sizes.
• Queue groups are visually distinct: Follow-ups due, Overdue, At risk, Today, Waiting.
• Pixel 7 layout stacks rows as cards with labels preserved, no visible overlap, and no horizontal overflow.

Screenshot evidence inspected:

• .tmp/screenshots/issue-61/desktop-work-engine-operations-home-daily-queue.png
• .tmp/screenshots/issue-61/mobile-pixel7-work-engine-operations-home-daily-queue.png

Verification run:

• PASS npm --prefix work-engine run test:e2e -- --grep "Dashboard daily queue layout keeps dense operational rows readable" — 1 passed

No Designer changes made. After Tester passes, #61 can proceed to PM acceptance.

[alexeygrigorev]

TEST PASS

Tester gate for #61 completed on branch worktree-issue-61 in /home/alexey/git/dataops/.tmp/worktrees/issue-61. No code was committed.

Changed files reviewed:

• work-engine/src/public/app.js
• work-engine/src/pages/index.html
• work-engine/e2e/home-dashboard.spec.js
• work-engine/tests/home-dashboard.test.ts

Verification commands:

• PASS npm --prefix work-engine test — exit 0, 677 passed
• PASS npm --prefix work-engine run typecheck — exit 0
• PASS npm --prefix work-engine run build — exit 0
• PASS node --check work-engine/src/public/app.js — exit 0
• PASS git diff --check — exit 0
• PASS cd work-engine && npx playwright test e2e/home-dashboard.spec.js -g "Dashboard daily queue layout keeps dense operational rows readable" — exit 0, 1 passed
• PASS npm --prefix work-engine run test:e2e — clean rerun exit 0, 308 passed

Note: an earlier full E2E attempt hit local EADDRINUSE on port 3001 and was interrupted with exit 130 after cascading environmental failures. I confirmed no lingering process, reran from a clean port state, and the full suite passed.

Screenshot and layout evidence:

• SWE screenshots inspected:
  • .tmp/screenshots/issue-61/desktop-work-engine-operations-home-daily-queue.png
  • .tmp/screenshots/issue-61/mobile-pixel7-work-engine-operations-home-daily-queue.png
• Tester screenshots captured and inspected:
  • .tmp/screenshots/issue-61/tester-desktop-work-engine-operations-home-daily-queue.png
  • .tmp/screenshots/issue-61/tester-mobile-pixel7-work-engine-operations-home-daily-queue.png
  • .tmp/screenshots/issue-61/tester-layout-evidence.json

Acceptance criteria:

• PASS Desktop daily queue rows show date, task/workflow, status/proof, assignee, required proof, and next action without visible overlap or clipped one-letter controls. Tester measurement: desktop scrollWidth=1440, clientWidth=1440, no detected cell overflows; action buttons measured 88-116px wide.
• PASS Queue groups remain visually distinct. Tester data and screenshots include Follow-ups due, Overdue, At risk, Today, and Waiting group bands.
• PASS Required link/file/artifact controls remain usable at normal desktop widths. Required proof input measured 162px wide on desktop; external status proof and follow-up controls remain readable in screenshot inspection.
• PASS Pixel 7 stacked rows preserve labels and touch targets without horizontal overflow. Tester measurement: mobile scrollWidth=412, clientWidth=412, hasHorizontalOverflow=false; row labels repeat as Date, Task, Status / Proof, Assignee, Required Proof, Next Action; controls measured 32-38px high.
• PASS Screenshot evidence captured for desktop and Pixel 7 Operations Home.

No Tester blockers found. Ready for Designer review; after Designer review passes, this is ready for PM acceptance from the Tester side.

[alexeygrigorev]

PM ACCEPT — #61

Operator-perspective acceptance passed.

Checks performed:

• Reviewed the groomed Fix daily queue table wrapping and overlap in V1 dashboard #61 scope and confirmed the branch only addresses the Operations Home daily queue readability/actionability defect from Run unified V1 operator UX acceptance pass across daily workflows #57.
• Reviewed SWE handoff, Designer PASS, and Tester PASS evidence.
• Inspected the desktop and Pixel 7 screenshot evidence under .tmp/screenshots/issue-61/.
• Ran PM spot-check: npm --prefix work-engine run test:e2e -- --grep "Dashboard daily queue layout keeps dense operational rows readable" — PASS, 1 passed.

Acceptance criteria:

• PASS Desktop daily queue is readable and actionable: date, task/workflow, status/proof, assignee, required proof, and next action are scannable without the Run unified V1 operator UX acceptance pass across daily workflows #57 one-letter/control-collision defects.
• PASS Queue groups remain visually distinct: Follow-ups due, Overdue, At risk, Today, Waiting.
• PASS Required proof and follow-up/action controls remain usable at desktop width.
• PASS Pixel 7 layout stacks rows with labels and reachable controls, without horizontal overflow in the inspected evidence.
• PASS Screenshot evidence exists for desktop and Pixel 7 Operations Home.

#57 impact: this resolves the #61 daily queue layout blocker identified in the #57 Designer findings. #57 still has any separate blockers outside #61, including #62, until those are accepted separately.

No PM blockers. Branch may be committed with Closes #61.

[alexeygrigorev]

ON-CALL REPORT — #61 / commit 4d4c6f3

Run inspected:

• Deploy DataOps V1 Lambda run 28321629963: https://github.com/DataTalksClub/dataops/actions/runs/28321629963
• Head SHA: 4d4c6f31c0177a0cfbf875839856547399d12d52
• Branch/event: main / push
• Overall conclusion: FAIL, due AWS deploy-role permission drift.

CI results:

• PASS Check DataOps v1 app job in 3m50s.
• PASS docs app tests.
• PASS browser-backed docs portal flow.
• PASS work-engine tests.
• PASS work-engine typecheck.
• PASS work-engine build.
• PASS work-engine Playwright E2E.
• PASS search index build.
• PASS search handler smoke against built index.
• PASS full app handler smoke.
• PASS SAM setup, sam validate, and SAM build.

Deploy results:

• FAIL Deploy DataOps v1 app job at Deploy DataOps v1 stack.
• Configure AWS credentials and Build SAM artifact passed.
• Deployed smoke tests were skipped because sam deploy failed before stack update success.
• CloudFormation attempted to add DataOpsExportArchiveBucket (AWS::S3::Bucket) plus the daily work-engine EventBridge resources.
• Failure message: assumed role arn:aws:sts::817685572750:assumed-role/dataops-github-actions-deploy/dataops-v1-deploy is not authorized to perform s3:CreateBucket on arn:aws:s3:::dataops-v1-dataopsexportarchivebucket-xui0whem1kxc because no identity-based policy allows s3:CreateBucket.
• Stack dataops-v1 rolled back to UPDATE_ROLLBACK_COMPLETE.

Classification:

• Not a Fix daily queue table wrapping and overlap in V1 dashboard #61 repo/test regression. The commit-facing checks, including the work-engine E2E coverage relevant to the daily queue layout, passed.
• External AWS deploy-role drift, matching the known P0: Reconcile retained DataOps intake table blocking deploy #60 blocker class. P0: Reconcile retained DataOps intake table blocking deploy #60 already tracks the credentialed AWS deploy-role update path; the latest failure adds missing S3 bucket creation permission for DataOpsExportArchiveBucket on top of the previously observed EventBridge permission drift.

On-call action:

• No code changes made.
• No fix commit pushed.
• Did not rerun or watch indefinitely because the remaining blocker requires credentialed AWS IAM/CloudFormation work.

Remaining blocker:

• A credentialed AWS operator must update dataops-github-actions-deploy / stack dataops-v1-github-actions in eu-west-1 so it can create/manage the DataOps stack resources now required by main, specifically including S3 bucket creation for DataOpsExportArchiveBucket and the EventBridge permissions tracked by P0: Reconcile retained DataOps intake table blocking deploy #60. After that, rerun Deploy DataOps V1 Lambda on main and monitor deployed smoke tests.