Prepare design doc ahead of balloting

- Rename the design doc.
- Cross out rejected options 2 and 5
- Add notes to 2 and 5 calling this out

(other changes may be added from the previous thread in #503 and WG call notes from 2023-10-30)

exploration/text-vs-code.md → exploration/delimiting-variant-patterns.md

@@ -14,6 +14,7 @@ Status: **Proposed**
 		<dd>2023-09-13</dd>
 		<dt>Pull Request</dt>
 		<dd><a href="https://github.com/unicode-org/message-format-wg/pull/474">#474</a></dd>
+		<dd><a href="https://github.com/unicode-org/message-format-wg/pull/503">#503</a></dd>
 	</dl>
 </details>
 
@@ -150,10 +151,10 @@ Currently the syntax uses the first alternative below.
 There are five candidates for handling the boundaries between code and patterns:
 
 1. Always quote non-simple patterns (current design)
-2. Never quote patterns (all whitespace is significant)
+2. ~~Never quote patterns (all whitespace is significant)~~
 3. Permit non-simple patterns to be quoted and trim unquoted whitespace
 4. Trim all unquoted whitespace, but do not permit quoting non-simple patterns
-5. Selectively trim patterns (all whitespace is otherwise significant)
+5. ~~Selectively trim patterns (all whitespace is otherwise significant)~~
 
 ### Always Quote
 
@@ -183,6 +184,9 @@ Cons:
 
 ### Never Quote Patterns
 
+> [!IMPORTANT]
+> This option was rejected by the working group in the 2023-10-30 call.
+
 In this alternative, all non-code whitespace is significant. 
 We have to use a slightly different syntax in the example, so that
 the boundary between code and pattern works.
@@ -264,6 +268,9 @@ Cons:
 
 ### Selective Trimming
 
+> [!IMPORTANT]
+> This option was rejected by the working group in the 2023-10-30 call.
+
 In this alternative, only specific whitespace is automatically trimmed
 and the whitespace can be omitted.
 This is similar to "Never Quote Patterns" in that all whitespace
@@ -536,4 +543,4 @@ characters (including line breaks, control characters, etc.) and rely upon escap
 in those outer formats to aid human comprehension (e.g., depending upon container
 format, a U+000A LINE FEED might be represented as `\n`, `\012`, `\x0A`, `\u000A`,
 `\U0000000A`, `&#xA;`, `&NewLine;`, `%0A`, `<LF>`, or something else entirely).
-</details>
+</details>