Exercise 1: Why a Compute Hour Measures Parallel Time, Not Summed Duration — Possible Solution
====================================================================================================

The chapter's own real, verified example makes the mechanism concrete:
running 5 real tests of 12 minutes each together consumes exactly 1
compute hour. If compute hours were instead measured by simply adding
up every individual test's own duration - 5 tests times 12 minutes
each - that would total 60 minutes of summed duration, which happens
to equal 1 hour in this specific example too, but only because the
example was chosen to make that coincidence clear. The real, important
distinction is in what's actually being measured.

Compute hours genuinely reflect real, elapsed wall-clock time consumed
by Xcode Cloud's own infrastructure while a task runs, not the
theoretical sum of every individual piece of work if it had been done
one after another. Since Xcode Cloud genuinely runs tests in parallel
- multiple real device configurations tested simultaneously rather
than sequentially - the actual elapsed time to get all 5 tests done is
much shorter than 60 minutes of sequential execution would take. The
compute-hour billing reflects that real, actual parallel execution
time, which is why running many tests in parallel can complete, and be
billed, far faster than running the same total amount of testing work
one test at a time.

If billing were instead based on summed individual durations
regardless of parallelism, there would be no real, meaningful
incentive to actually run tests in parallel at all - a real, wide
device-configuration test suite could take dramatically longer in
wall-clock time while costing the same on paper, defeating one of
Xcode Cloud's own stated real benefits (fast feedback while still
developing on the Mac).

ANSWER: A compute hour measures the real, actual elapsed time Xcode
Cloud's own infrastructure spends running a task, not the sum of every
individual test's own duration - because tests genuinely run in
parallel, this means billing reflects the real, faster wall-clock time
parallel execution actually achieves, which is exactly what
incentivizes and rewards Xcode Cloud's own real parallel testing
capability.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains the real distinction between wall-clock elapsed time and
summed individual duration, and connects it to why that distinction
matters for Xcode Cloud's own stated parallel-testing benefit, rather
than just restating the chapter's own example.