During flag parsing, verify that `--embed_changelist` does not contain a newline character.
Document that neither this flag nor any key/value in the workspace status info may contain a newline, and that there should be no duplicate keys.
The build will already fail during build info parsing if `--embed_changelist` contains a newline. This change makes it fail faster.
PiperOrigin-RevId: 344884670
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index 20933c4..bea8fd5 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -1423,7 +1423,8 @@
The program should print zero or more key/value pairs to standard output, one entry on each line,
then exit with zero (otherwise the build fails). The key names can be anything but they may only
use upper case letters and underscores. The first space after the key name separates it from the
- value. The value is the rest of the line (including additional whitespaces).
+ value. The value is the rest of the line (including additional whitespaces). Neither the key nor
+ the value may span multiple lines. Keys must not be duplicated.
</p>
<p>
Bazel partitions the keys into two buckets: "stable" and "volatile". (The names "stable" and
