build: route .ww directories as packages

docs/test-system-v2.md

@@ -265,6 +265,26 @@ directory/recursive selection, package/import identities, graph/action
 identities, persistence formats (build 18, test 19, semantic 3), and test
 process topology are explicit non-effects.
 
+An existing local directory whose requested build basename ends `.ww`
+(including a visible `_test.ww` symlink to a directory) remains a directory
+package, not a raw named test source. WWstage `ww build` now uses the same
+symlink-following requested-kind decision as Cstage and enters the established
+directory coordinator. The directory's actual `*_test.ww` entries remain
+excluded from production and available to `ww test`; the requested suffix does
+not itself create a test variant. Raw `ww test`, `test -c`, and `test -S` were
+already stat-routed and do not change. The focused package observer directly
+measures Cstage/WWstage build diagnostics and semantic/public artifact-byte
+parity, direct and symlinked `.ww` directories, a dotted dependency, output
+modes, cold/warm transaction behavior, compiler and signaled-linker failure
+preservation, selected-route concurrency, cleanup, and the exact test-command
+behavior. Direct driver interruption remains owned by the unchanged directory
+machinery and is not claimed fixed here. The shared resolver and `ww run` are
+deliberately unchanged—and the observer
+retains their pre-existing stage difference—because pinned Go's run command
+has a distinct named-file front door.
+No test product, result, package/import identity, or serialized format changes;
+build remains 18, test remains 19, and semantic storage remains 3.
+
 List mode uses that same product process and initialization boundary but starts
 no per-test child. The shared language harness emits only selected qualified
 test names, one per line in descriptor order. A valid filter selecting no tests