Home has both Tasks and Tests, and they cover overlapping ground — which raises the obvious question of where to actually spend your time.
Start with Tasks
Tasks is the guided, day-to-day view — a prioritized checklist of what still needs attention, organized around actual work items rather than raw technical checks. This is where most people should default to working from, especially early on: it tells you what to do next, not just what's currently passing or failing.
Tests is the complete technical record underneath
Tests is the full, unfiltered list — every automated and manual check across every framework you have enabled, whether or not it's tied to an open task. Reach for Tests when you need to:
Investigate a specific failing check in detail (evidence, remediation guidance, which resources failed).
Confirm a fix actually took effect after re-running.
Get the complete picture for an audit, rather than just what's currently actionable.
How they connect
Every task is backed by one or more linked tests — a task doesn't have a manual "done" checkbox, it completes automatically once all of its linked tests pass. So in practice, working through Tasks is working through Tests, just organized around what you actually need to fix rather than a flat technical list. Tests is where you go to dig into the details behind any one task, not a separate, competing work queue.
