ADFA-4128: qb 03 review fixes — align tool-path DTO test with contract

Finding (Important, pr03-review.md): DaemonProtocolDtoTest's first test was
named "configure without optional toolchain paths means self-discovery" with a
comment calling null the "discover from ANDROID_HOME" signal — the opposite of
the contract in the same commit (DaemonProtocol.kt KDoc: "required, as the
daemon never guesses a tool path"; README: configure answers ok:false with one
diagnostic per missing field) and of the daemon's actual behavior at stack tip
(DaemonService.configure rejects null/blank aapt2/d8Jar/androidJar).

Fix: renamed the test and rewrote the comment so null reads as "not supplied,
and configure rejects it", per the documented contract. The assertions were
already correct (null IS the DTO default) and are unchanged; the rejection
behavior itself is asserted in the daemon module's DaemonServiceTest at stack
tip, so no rejection assertion is duplicated here.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Kj9YeCDHGp9DU8LPtfWJ7W

Author: fryanpan

quickbuild/protocol/src/test/kotlin/org/appdevforall/cotg/quickbuild/protocol/DaemonProtocolDtoTest.kt

@@ -12,10 +12,11 @@ import org.junit.jupiter.api.Test
  */
 class DaemonProtocolDtoTest {
 	@Test
-	fun `configure without optional toolchain paths means self-discovery and the v1 minApi floor`() {
+	fun `configure defaults unsupplied toolchain paths to null - which the daemon rejects - and the v1 minApi floor`() {
 		val request = ConfigureRequest(1, "/p", listOf("/a.jar"), "/out")
 
-		// Null here is the "discover from ANDROID_HOME" signal, not an error.
+		// Null means "not supplied": the daemon never discovers tool paths, so configure
+		// answers ok:false with one diagnostic per null/blank path (see the KDoc and README).
 		assertThat(request.aapt2).isNull()
 		assertThat(request.d8Jar).isNull()
 		assertThat(request.androidJar).isNull()