ADFA-4128 (3/11): address CodeRabbit review

- F1715-1 stop the response contract claiming values are never arrays

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

Author: fryanpan

quickbuild/protocol/README.md

@@ -57,7 +57,8 @@ Six ops: `configure`, `compile`, `dex`, `relink`, `ping`, `shutdown`.
 
 ### Responses
 
-`{"id", "ok", <op values, flat>, "diagnostics"}`. Values are flat scalars, never nested.
+`{"id", "ok", <op values, flat>, "diagnostics"}`. Values are flat - never a nested object.
+They are JSON scalars apart from `classesChanged`, which is an array of strings.
 
 - `diagnostics` **can appear on success** - a build can succeed with warnings.
 - **`line` and `column` are JSON numbers, and they stop here.** CoGo keeps error positions for

quickbuild/protocol/src/main/kotlin/org/appdevforall/cotg/quickbuild/protocol/DaemonProtocol.kt

@@ -456,17 +456,19 @@ data class DexStats(
 }
 
 /**
- * The daemon's answer to one request. [values] holds the op-specific scalars (`classesDir`,
- * `dexFile`, `resourcesArsc`, `durationMillis`, ...), serialized flat into the response object.
+ * The daemon's answer to one request. [values] holds the op-specific values (`classesDir`,
+ * `dexFile`, `resourcesArsc`, `durationMillis`, ...), serialized flat into the response object -
+ * never a nested object. `classesChanged` is the one array.
  *
  * Adding a response key must not bump [PROTOCOL_VERSION]: the version is a hard gate that aborts
  * the session on mismatch, and a staged daemon jar can lag the client, so bumping it for an
  * additive field would break a pairing that would otherwise work.
  *
  * @property id the [DaemonRequest.id] this answers; the client's only correlation handle.
  * @property ok whether the op succeeded, false implying at least one ERROR in [diagnostics].
- * @property values op-specific scalars, flat and JSON-scalar-only, keyed by the `KEY_*` constants
- *   and [ResponseKeys], so a client may read one key and ignore the rest.
+ * @property values op-specific values, flat - never a nested object - and JSON scalars apart
+ *   from `classesChanged`, which is an array of strings. Keyed by the `KEY_*` constants and
+ *   [ResponseKeys], so a client may read one key and ignore the rest.
  * @property diagnostics compiler and linker messages, present on success too since a build can
  *   succeed with warnings.
  */