Research: compare unified task, worker, and PR views

[srctl]

The current Jobs view shows execution but leaves task priority/status, two-task capacity, human attention, and GitHub review/check state disconnected. This research compares three task-level experiences above the worker monitor in #4 and recommends A: task workspace + selected detail, with a Needs you filter and mobile list/detail navigation.

Findings, tradeoffs, assumptions, open decisions and run instructions · Verification results and limitations

Compare editable concepts

Option	Desktop	Mobile
A · Task workspace — recommended	Editable Excalidraw · PNG · SVG	Editable Excalidraw · PNG · SVG
B · Status board	Editable Excalidraw · PNG	Editable Excalidraw · PNG
C · Attention inbox	Editable Excalidraw · PNG	Editable Excalidraw · PNG

A keeps progress and attention together; B makes lifecycle stages easy to scan but disperses blockers; C accelerates triage but gives quiet work less prominence. These exports are labeled design wireframes, separate from actual rendered screenshot evidence below.

The isolated interactive prototype switches among the options and exercises search/filtering, source drilldown, a stale GitHub snapshot and a verified handoff. All data and destinations are fictional. Task status, job lifecycle, worker observation, PR state and checks remain distinct. Human review is not Done; only humans mark Done. Blocked/uncertain work retains its execution reservation until confirmed handoff or stop; the proposed capacity policy is an explicit review decision, not production behavior.

Verification

• Cleanup validation: repository lint/format, prototype typecheck and isolated prototype build passed; local Markdown and PR artifact links checked. App typecheck passed during the original research validation.
• Six native .excalidraw files: loaded in Excalidraw 0.18.0, element counts and native text preserved through serialization, SVG exports rendered into PNGs. Editor screenshots included.
• Desktop/mobile browser checks rerun after cleanup: passed source drilldown, stale-source display, Human review distinction, attention filters, empty/title search, missing PR, slot release, reset, alternate layouts, mobile Back preservation, overflow and no external/API requests or browser exceptions.
• All 13 recaptured prototype screenshots were pixel-identical to the retained evidence.
• No full app regression/auth suite, real-source integration, actual worker control, user study, screen-reader audit, dark-mode or performance tests. Concise verification notes are committed; one-off scripts, raw logs and capture metadata are excluded.

Actual rendered before / after

Captured baseline before implementation. Same blocked Repair export flow assignment, fixture job summary/output, light mode, UTC, scale 1. Desktop 1440×1100; mobile 390×844. Full-page heights vary. Before opens the existing job/output disclosures; after opens the same task detail.

Baseline limitation: before images render actual Jobs content/StyleX from 3f7bae2 with an isolated presentation shell and inert router/server/stop boundaries. They are not authenticated live Roost screenshots. Both views use the same current-job fixtures; the unified view also exposes two tasks without current jobs. No live data or settings were accessed.

Before · existing Jobs fixture harness	After · unified fixture prototype

Mobile list · Human review · GitHub unavailable · Verified handoff

All deliverables are under docs/prototypes/unified-task-view/: findings, runnable fixture UI, six editable Excalidraw scenes, SVG/PNG exports, rendered screenshots and concise verification notes. The one-off capture/generation/validation scripts, custom validation editor, raw logs, metadata and capture-only baseline route are excluded; local copies remain under ignored .roost/unified-task-view-cleanup/ for coordinator reference. Open native files directly in Excalidraw. No production integration, dependency manifest, host configuration, synchronization service, worker monitor or automation changes. No merge, deploy, Notion/Roost update or Done action. Ready for the experience decision before any separately authorized implementation.