ww: report no test files for empty test packages

docs/test-system-v2.md

@@ -207,9 +207,10 @@ not followed. A wildcard cannot consume a non-terminal exact `vendor` element,
 while an explicitly vendor-rooted pattern remains legal. Every selected
 test-bearing directory becomes exactly one package run, binary, and result even
 when both internal and external actions exist. Selected source-bearing
-directories without selected test files report the usual `?` line after
-ordinary production validation, with no support, generated main, link, binary,
-result, or process. The coordinator first
+directories without selected test files report exactly
+`?    <package> [no test files]\n` after ordinary production validation, with
+no support, generated main, link, binary, captured runtime result, or process.
+The coordinator first
 launches one driver plan for the complete command-global package/action union.
 After that shared build completes, `-j N` schedules up to N successful selected
 test binaries concurrently under `os.exec` start/poll supervision (no threads);
@@ -230,9 +231,10 @@ names reject before tools; exact `/dev/null` discards every copy and permits
 duplicate names. The private test link still runs unless `-c` suppresses it;
 the raw single-file compatibility route also links into driver-owned private
 storage instead of using `/dev/null` as an artifact or `.sepwork` stem. A
-package with no selected test source validates production
-but publishes nothing and does not create an otherwise unneeded output
-directory. Successful `-c` output is silent apart from no-test reporting.
+package with no selected test source validates production, reports the same
+`[no test files]` result, publishes nothing, and does not create an otherwise
+unneeded output directory. Successful `-c` output is silent apart from that
+no-test-files report.
 
 The package suite also pins the adjacent `ww build` output-directory branch.
 After normal loading, an existing directory (including a symlink to one) or an