docs(changeset): name both clocks the single-package capture differs in

The unchanged-face claim was measured again from a committed tree, with
compile.ts reverted to its pre-fix blob for the before leg and the restore
proven by hash. The two captures are 2038 bytes each, as recorded — but
they differ in TWO fields, not one: `Build complete (Nms)` and
`Load time: Nms`. Naming one of them made the sentence read as a stricter
measurement than the one that was taken, and a reader reproducing it would
have found a second difference the text does not account for.

Both are clocks, so the claim the bullet makes is unchanged: on a stack
with no `packages[]` this fix moves no rendered byte.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DvvamiacK328idtBYJBxV3

Author: claude

.changeset/18780-build-text-face-advisory-count.md

@@ -17,7 +17,7 @@ os validate        4 advisory entries           <- since #18769
 ```
 
 - **The list moves, not the count.** #11529 settled this axis one list over: the summary counts the whole set and the printer NAMES what it withheld, because a count quietly shrunk to match a short list is the false-clean direction — it deletes a finding from the text face of the command that ships while `--json` and `os validate` keep reporting it. The fourth advisory now prints.
-- **What an author sees change**: on a stack that declares `packages[]`, the advisory block is rendered after the `Running author-time rules per package (N)...` step line instead of before it, and it now carries the per-package findings — the ones whose `where` reads `package '<id>' — …`. A stack with no `packages[]` is unchanged — measured on a single-package fixture, the before/after captures are 2038 bytes each and differ only in the `Build complete (Nms)` timer: its list was already complete, and the block still precedes every later step line.
+- **What an author sees change**: on a stack that declares `packages[]`, the advisory block is rendered after the `Running author-time rules per package (N)...` step line instead of before it, and it now carries the per-package findings — the ones whose `where` reads `package '<id>' — …`. A stack with no `packages[]` is unchanged — measured on a single-package fixture, the before/after captures are 2038 bytes each and differ only in the run's two clocks, `Load time: Nms` and `Build complete (Nms)`: its list was already complete, and the block still precedes every later step line.
 - **Still ONE printer call.** The block is deferred to the point where the list is complete rather than printed twice, so the 50-entry cap and its `… and N more … not shown` notice keep judging one list. A second `printAuthoringAdvisories` for the survivors alone would have given the cap a second budget and the notice a second, partial total.
 - **The author-time rule FAILURE faces keep their advisories.** A union-level failure exits before the per-package pass runs, so its block is byte-for-byte what it was; the per-package failure face now prints the per-package advisories too, which its own `--json` twin has published since #11772.