You are playing the Regex Pattern Matcher game against o1 - (low).

Game history:
Turn 1: o1 - (low) proposed text with target items: ["sample.test+filtered@sub.example.co.uk","user+alias@domain-x.edu","\"quoted.name\"@strange-domain.info","+1 (202) 555-0147 ext. 105","202-555-0199","+44 (0) 20 7123 4567","2023-12-31","31/12/2023","12.31.2023","31 Jan 2023","INV-2023-ABCD","REF#XF-9999","ID:EE-12345","TCK-abc-001"]
Current turn: 1 of 10
You are the SOLVER.

Your opponent has provided the following challenge:

Text: "Below is the ultimate regex gauntlet:

1) E-mails:
   - Valid:  sample.test+filtered@sub.example.co.uk, user+alias@domain-x.edu, "quoted.name"@strange-domain.info
   - Invalid: sample@@double-ats.com, user@non.existent TLD, user@domain,com (comma instead of dot)

2) Phone numbers:
   - Valid:  +1 (202) 555-0147 ext. 105, 202-555-0199, +44 (0) 20 7123 4567
   - Invalid: +1-202-555, 020) 1234-567 (missing parentheses), 555-012-3456 (too few digits)

3) Dates:
   - Valid:  2023-12-31, 31/12/2023, 12.31.2023, 31 Jan 2023
   - Invalid: 2023.31.12 (mixed order), 31/13/2023 (month out of range)

4) Reference IDs:
   - Valid:  INV-2023-ABCD, REF#XF-9999, ID:EE-12345, TCK-abc-001
   - Invalid: INV-2023- (missing segment), ABCD-123-?? (invalid symbols)

5) Misc:
   - Potential traps: a (202) near parentheses mismatch, user@domain,, (double commas), partially quoted “names”, or phone formats missing key pieces.

Challenge text to find the valid items:

"If you need support, contact sample.test+filtered@sub.example.co.uk or call +1 (202) 555-0147 ext. 105 right away. We also accept emails at user+alias@domain-x.edu or weird addresses like user@domain,com (which is invalid). For UK residents, dial +44 (0) 20 7123 4567. Our old numbers like +1-202-555 or 555-012-3456 are incomplete.

Dates can be typed as 2023-12-31 or 31 Jan 2023. Please do not use 2023.31.12 or 31/13/2023. We support 31/12/2023 or 12.31.2023 with different separators. Reference IDs like INV-2023-ABCD or TCK-abc-001 are acceptable, but be wary of ABCD-123-?? which is not. Also, "quoted.name"@strange-domain.info is a valid email, while sample@@double-ats.com is not.

Don’t forget the extension (ext. 105) in phone numbers, or the correct “quoted.name” format. Our official reference code is REF#XF-9999 and ID:EE-12345. Watch out for tricky near-valid formats like 020) 1234-567 which has mismatched parentheses.
"
"

You need to create a regular expression pattern that matches EXACTLY these items in the text:
[
  "sample.test+filtered@sub.example.co.uk",
  "user+alias@domain-x.edu",
  "\"quoted.name\"@strange-domain.info",
  "+1 (202) 555-0147 ext. 105",
  "202-555-0199",
  "+44 (0) 20 7123 4567",
  "2023-12-31",
  "31/12/2023",
  "12.31.2023",
  "31 Jan 2023",
  "INV-2023-ABCD",
  "REF#XF-9999",
  "ID:EE-12345",
  "TCK-abc-001"
]

Rules:
1. Your regex must match ALL of the target items in the text.
2. Your regex must NOT match anything else in the text.
3. The pattern should be a valid JavaScript regular expression.
4. Do not include the leading and trailing slashes or flags in your pattern.

You'll use the "make_move" function to submit your solution with:
1. reasoning: Your reasoning for this regex pattern
2. move: The regex pattern as a simple string

Example of what the function parameters should include:
- reasoning: "This pattern matches email addresses by using..."
- move: "[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}"

IMPORTANT:
- The regex pattern should be a simple string.
- Do NOT use raw regex notation with slashes like /pattern/.
- Do NOT escape characters unless they need to be escaped in the regex itself.
- For example, to match parentheses, use "\(\)" not "\\(\\)".
- When your pattern contains backslashes, each backslash itself in the string should be a single backslash, not doubled.

Think carefully and test your pattern mentally before submitting.