Challenge 1: What a Linux User Should Actually Expect From Cap --
Solution Walkthrough

A Linux-based reader should expect Cap to be the closest thing in
this course to a genuine equivalent for Screen Studio and Screenify
Studio, but not yet a fully finished one. Per this chapter, Cap is
currently available for macOS and Windows, with Linux support
explicitly described as still in development rather than already
shipped. This is a meaningfully different status from "cross-platform
today" -- it means Linux support is a real, stated direction for the
project, not vaporware, but it also means a Linux user can't yet
assume full feature parity or a polished, finished release the way a
Windows or Mac user currently can.

The practical takeaway: a Linux-based reader should treat Cap as the
right project to watch and likely adopt once Linux support matures,
rather than assuming today's Windows/Mac experience is already
available to them unchanged. Checking Cap's own current release
status directly, rather than relying on this chapter alone, would be
the sensible next step before committing to it for an actual Linux
workflow right now.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the reader picks up on the chapter's own
precise wording ("still in development" vs. already shipped) rather
than assuming "cross-platform, open-source" automatically means full
parity across every platform mentioned -- a real distinction the
chapter deliberately calls out rather than glossing over.