ww: recursive DIR/... package discovery for ww test

docs/test-system-v2.md

@@ -188,7 +188,12 @@ and nonempty-version-constant assertions.
 `ww test` delegates directory package requests to the native package
 coordinator. The coordinator owns discovery, package grouping, same-package and
 external-package test composition, filtering, result aggregation, and its
-internal temporary workspace. With `-c`, it publishes each exact
+internal temporary workspace. A trailing `...` path element (`ww test lib/...`,
+Go's `./...` form) is recognized by both driver stages before path resolution
+and walks the tree rooted at the prefix: every subdirectory whose name does not
+begin with `.` or `_` is descended with the same lstat/no-symlink discipline,
+each test-bearing directory becomes one package run, and source-bearing
+directories without tests report the usual `?` line. With `-c`, it publishes each exact
 `<package>.test` binary and adjacent `<package>.test.sepwork` tree in the
 package directory; those become caller-owned artifacts. Without `-c`, it
 removes the temporary binary and scratch with its workspace. The language
@@ -306,7 +311,6 @@ timeout policy in this architecture.
 Carried over from the dissolved project plan; each is deliberate scope, not
 drift:
 
-- Recursive package discovery (a `./...`-equivalent pattern) for `ww test`.
 - Package-level concurrency for the coordinator's builds (it is
   single-threaded by design today).
 - A package-level `-o` contract (single-file `ww test -o` exists; directory