You are playing the Regex Pattern Matcher game against claude 3.7 sonnet (high2).

Game history:
Turn 1: claude 3.7 sonnet (high2) proposed text with target items: ["john.doe@example.com","jane_smith123@company-name.co.uk","user.name+tag+sorting@example.com","admin@mailserver1","email@123.123.123.123","1234567890@example.com","email@example-one.com","_______@example.com","email@example.name","email@example.museum","email@example.co.jp","firstname-lastname@example.com","info@academic-institution.edu","user-@example.org","example@s.solutions"]
Current turn: 1 of 10
You are the SOLVER.

Your opponent has provided the following challenge:

Text: "Email Validation Test Suite Results:
------------------------------------------
Valid: john.doe@example.com (Standard email)
Invalid: john.doe@invalid (Missing TLD)
Valid: jane_smith123@company-name.co.uk (With underscore, numbers, hyphen and country code)
Invalid: jane@smith@company.co.uk (Multiple @ symbols)
Valid: user.name+tag+sorting@example.com (With plus tags)
Invalid: .username@example.com (Leading dot in local part)
Valid: admin@mailserver1 (Local domain without TLD)
Invalid: user@-example.com (Domain starts with hyphen)
Valid: email@123.123.123.123 (IP address as domain)
Invalid: user@domain..com (Consecutive dots in domain)
Valid: 1234567890@example.com (All numeric local part)
Invalid: user@domain@example.com (Multiple @ symbols)
Valid: email@example-one.com (Hyphen in domain)
Invalid: user@.domain.com (Domain starts with dot)
Valid: _______@example.com (Underscore-only local part)
Invalid: user@domain.com- (Domain ends with hyphen)
Valid: email@example.name (gTLD)
Invalid: Abc..123@example.com (Consecutive dots in local part)
Valid: email@example.museum (Specific gTLD)
Invalid: user@[IPv6:2001:db8::1] (IPv6 literal not properly supported)
Valid: email@example.co.jp (ccTLD with second level domain)
Invalid: user@domain.com. (Domain ends with dot)
Valid: firstname-lastname@example.com (Hyphen in local part)
Invalid: user@domain-.com (Domain with hyphen followed by dot)
Valid: info@academic-institution.edu (Educational domain)
Invalid: user@@domain.com (Double @ symbol)
Valid: user-@example.org (Local part ends with hyphen)
Invalid: user space@domain.com (Space in local part)
Valid: example@s.solutions (Short domain name)
Invalid: user@domain_name.com (Underscore in domain)"

You need to create a regular expression pattern that matches EXACTLY these items in the text:
[
  "john.doe@example.com",
  "jane_smith123@company-name.co.uk",
  "user.name+tag+sorting@example.com",
  "admin@mailserver1",
  "email@123.123.123.123",
  "1234567890@example.com",
  "email@example-one.com",
  "_______@example.com",
  "email@example.name",
  "email@example.museum",
  "email@example.co.jp",
  "firstname-lastname@example.com",
  "info@academic-institution.edu",
  "user-@example.org",
  "example@s.solutions"
]

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.