fmt-workspaces: exit 2 means no verdict, not no output (improvise-ximf)

The unreached-package arm exits 2 and names the package's Cargo.toml, so the
usage text's "NO file is named" was false for it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VdfEGXA7aJ6ftMsCc9PJze

context/test-evidence/tooling.md

@@ -417,9 +417,11 @@ getting wrong. The line the split actually needs is **"did the gate run"**:
 - exit 1 — rustfmt did not certify a root clean. A diff or a refusal to parse;
   either way **a file is named** and the tree is what is wrong.
 - exit 2 — the gate did not run. Usage, no cargo, no rustfmt, `cargo metadata`
-  failed, no `[workspace]` root. **No file is named.** Every such cause is
-  checked *above* the loop, which is what makes the narrowing true rather than
-  hopeful.
+  failed, no `[workspace]` root. **No source file is named.** Every such cause
+  is checked *above* the loop, which is what makes the narrowing true rather
+  than hopeful. (Since improvise-90ea, a package no root reaches is also exit 2,
+  and it names that package's `Cargo.toml`, which is the reason no verdict
+  exists. The line is "no verdict", not "no output"; improvise-ximf.)
 
 Both directions are now pinned, and two further rivals were injected:
 

scripts/fmt-workspaces.sh

@@ -19,7 +19,8 @@ exit 1  rustfmt did not certify a root clean: a file differs from rustfmt's
         and the tree is what is wrong.
 exit 2  the gate did not run: usage error, no cargo, no rustfmt, cargo
         metadata failed, no [workspace] root found, or a [package] that no
-        root has as a member. NO verdict was produced and NO file is named.
+        root has as a member. NO verdict was produced. No SOURCE file is
+        named; the unreached-package case names its Cargo.toml.
 
 The split is "did the gate run", not "is every exit-1 cause a diff". That is
 narrower than it sounds and it is deliberate -- see the note on rc=1 below.