[{"move": {"text": "Pattern Recognition Test Database\n\nValid Serial Numbers (Format: 2 uppercase letters, hyphen, 6 digits, hyphen, 2 uppercase letters):\n- Product: AB-123456-CD (Active)\n- Product: EF-789012-GH (Active)\n- Product: IJ-345678-KL (Inactive)\n- Product: MN-901234-OP (Pending)\n\nInvalid Serial Numbers:\n- Format Error: AB-12345-CD (Too few digits)\n- Format Error: AB-1234567-CD (Too many digits)\n- Format Error: Ab-123456-CD (Lowercase letter in prefix)\n- Format Error: AB-123456-Cd (Lowercase letter in suffix)\n- Format Error: AB_123456_CD (Wrong separator)\n- Format Error: 12-123456-CD (Numbers instead of letters)\n- Format Error: AB-12345X-CD (Letter in number section)\n\nValid Date-Time Formats (ISO-8601 with 'T' separator and timezone):\n- Created: 2023-12-15T09:45:23Z (Record 1)\n- Created: 2023-01-05T14:30:15+01:00 (Record 2)\n- Created: 2023-06-28T22:15:40-07:00 (Record 3)\n- Created: 2023-11-30T08:05:30.123Z (Record 4)\n\nInvalid Date-Time Formats:\n- Format Error: 2023/12/15T09:45:23Z (Wrong date separator)\n- Format Error: 2023-12-15 09:45:23Z (Missing 'T' separator)\n- Format Error: 2023-12-15T09:45:23 (Missing timezone)\n- Format Error: 12-15-2023T09:45:23Z (Wrong date format)\n- Format Error: 2023-13-15T09:45:23Z (Invalid month)\n- Format Error: 2023-12-32T09:45:23Z (Invalid day)\n- Format Error: 2023-12-15T25:45:23Z (Invalid hour)\n\nValid Email Addresses (Format: alphanumeric/symbols before @, domain with at least one period):\n- Contact: john.doe@example.com (Primary)\n- Contact: jane_smith@company.co.uk (Secondary)\n- Contact: support+tickets@help.org (Support)\n- Contact: user-name.with.dots@sub.domain.net (Technical)\n\nInvalid Email Addresses:\n- Format Error: john.doe@example (Missing top-level domain)\n- Format Error: jane_smith@.com (Missing domain name)\n- Format Error: @company.com (Missing username)\n- Format Error: user name@domain.com (Space in username)\n- Format Error: john.doe@company.com@ (Multiple @ symbols)\n- Format Error: john.doe@@company.com (Multiple @ symbols)\n- Format E", "targetItems": ["AB-123456-CD", "EF-789012-GH", "IJ-345678-KL", "MN-901234-OP", "2023-12-15T09:45:23Z", "2023-01-05T14:30:15+01:00", "2023-06-28T22:15:40-07:00", "2023-11-30T08:05:30.123Z", "john.doe@example.com", "jane_smith@company.co.uk", "support+tickets@help.org", "user-name.with.dots@sub.domain.net"]}, "player": "claude 3.7 sonnet (high2)", "reasoning": "I'm creating an extremely difficult challenge that requires precise regex pattern matching skills. The text contains multiple data types (serial numbers, ISO-8601 timestamps, and email addresses) with valid and invalid formats that are very similar. This will force the opponent to create extremely precise regex patterns that can match only the valid formats while rejecting the invalid ones. The challenge requires advanced regex techniques like proper character classes, quantifiers, anchors, and potentially lookahead/lookbehind assertions to solve correctly.", "timestamp": 1742326208907}, {"move": "(?:[A-Z]{2}-\\d{6}-[A-Z]{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+\\-]\\d{2}:\\d{2})|[a-zA-Z0-9._+\\-]+@[a-zA-Z0-9\\-]+(?:\\.[a-zA-Z0-9\\-]+)*\\.[a-zA-Z]{2,})", "player": "o1 - (high)", "reasoning": "We combine three sub‑patterns separated by |, each matching one of the required formats. For serial numbers we use [A-Z]{2}-\\d{6}-[A-Z]{2}, for ISO-8601 date‑times with a T separator and timezone we use \\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+\\-]\\d{2}:\\d{2}), and for emails we use [a-zA-Z0-9._+\\-]+@[a-zA-Z0-9\\-]+(?:\\.[a-zA-Z0-9\\-]+)*\\.[a-zA-Z]{2,}. The overall pattern matches exactly these valid items and rejects everything else in the text.", "timestamp": 1742326279751}, {"move": {"text": "TEAM RECORDS (Confidential):\n\n1) Email addresses:\n   • valid_email+tag@sub.domain.co.uk\n   • wrong..email@example..com\n   • almost@valid@example.com\n   • no_tld@domain\n   • \"Weird spacing\" < spaced-out.user@weird-domain.org >\n\n2) Phone numbers:\n   • +1 (202) 555-0123 x56\n   • 202.555.0124\n   • +44-20-7946-0645 ext.105\n   • 555-0123\n   • (123)456-7890#12\n\n3) Dates:\n   • 2023-12-15T16:45:23Z\n   • 15/12/2023 16:45:23\n   • 12-15-2023 04:45:23pm\n   • 2023/12/15\n   • 15.12.2023\n   • 2023 Dec 15\n\n4) IDs:\n   • AB-123456-CD\n   • XY9-000111-ZZ\n   • FO-9999999-9C\n   • MNO-12345-PQ (Potentially invalid)\n\n5) Additional references:\n   • #someHashTag\n   • https://www.example.com/path?param=value\n   • user_name@@somewhere\n   • \"escaped\\\"quotes\"\n   • (∀x∈ℝ) f(x)=x²\n", "targetItems": ["valid_email+tag@sub.domain.co.uk", "spaced-out.user@weird-domain.org", "+1 (202) 555-0123 x56", "202.555.0124", "+44-20-7946-0645 ext.105", "(123)456-7890#12", "2023-12-15T16:45:23Z", "15/12/2023 16:45:23", "12-15-2023 04:45:23pm", "2023/12/15", "15.12.2023", "2023 Dec 15", "AB-123456-CD", "XY9-000111-ZZ", "FO-9999999-9C"]}, "player": "o1 - (high)", "reasoning": "I have crafted an extremely complicated set of data containing valid and invalid emails, phone numbers (with optional country codes, extensions, varied separators), dates in multiple formats (including ISO 8601, day-first, 12-hour with am/pm, etc.), and IDs with specific numeric and letter patterns. This text also includes tricky invalid items that must be excluded, requiring powerful alternation, lookarounds, and careful grouping to match correctly.", "timestamp": 1742326313880}, {"move": "valid_email\\+tag@sub\\.domain\\.co\\.uk|spaced-out\\.user@weird-domain\\.org|\\+1 \\(202\\) 555-0123 x56|202\\.555\\.0124|\\+44-20-7946-0645 ext\\.105|\\(123\\)456-7890#12|2023-12-15T16:45:23Z|15\\/12\\/2023 16:45:23|12-15-2023 04:45:23pm|2023\\/12\\/15|15\\.12\\.2023|2023 Dec 15|AB-123456-CD|XY9-000111-ZZ|FO-9999999-9C", "player": "claude 3.7 sonnet (high2)", "reasoning": "For this regex pattern, I'm using alternation (|) to match exactly the 15 target items. I've properly escaped all special regex characters that need to be matched literally:\n1. For emails: Escaped + and . characters\n2. For phone numbers: Escaped +, (), and . characters \n3. For dates: Escaped / and . characters\n4. For IDs: No special characters needed escaping\n\nThis pattern will match each target item exactly as it appears in the text and nothing else. I avoided trying to create more general patterns as that could potentially match non-target items like \"wrong..email@example..com\" or \"MNO-12345-PQ\".", "timestamp": 1742326502651}, {"move": {"text": "===== Complex Emails =====\nValid: john.doe@example.com, admin+filter@sub.domain.co.uk, \"quoted.user\"@strange-domain.org, user@[IPv6:2001:db8::1]\nSimilar but invalid: john.doe@.com, admin@+filter.co.uk, user@domain@example.com, @example.com\n\n===== Advanced Date/Time Formats =====\nValid ISO 8601: 2023-10-15T14:30:15.123Z, 2023-10-15T14:30:15.123456+05:30, 2023-10-15T14:30:15-08:00, 2023-01-02T00:00:00Z\nSimilar but invalid: 2023-13-15T14:30:15Z, 2023-10-15T25:30:15Z, 2023-10-15T14:30:15.Z, 2023-10-15T14:30:15+24:00\n\n===== JSON Path Expressions =====\nValid paths: $.store.book[0].title, authors[15].name, items[\"key with spaces\"][0], object.property[3][\"complex\\\"key\"].value\nSimilar but invalid: $.store.book[0.title, authors[15.name, items[\"unmatched], object.[3].property\n\n===== URLs with Unusual Features =====\nValid URLs: https://user:pass@example.com:8080/path?query=value#fragment, mailto:user+tag@example.com, ftp://server.net:21/path/\nSimilar but invalid: https://user@:pass@example.com, mailto:user@example@gmail.com, https:/missing-slash.com\n\n===== Nested Code Structure =====\nValid expression: functionCall(arg1, {key: \"value\", nested: [1, 2, {inner: \"object\"}]}, callback(x => x*2))\nValid with newlines: outerFunction(\n  firstArg,\n  {\n    key: \"complex\\\"string\",\n    array: [1, 2, 3]\n  }\n)\nSimilar but invalid: functionCall(arg1, {key: \"value\", {invalid: true}}, callback(x => x*2))\n\n===== Complex Patterns =====\nValid HTML-like: <tag attr=\"value\" data-test='single-quoted'>content</tag>\nValid comment: /* Multi-line\ncomment with special chars: <, >, &, \" */\nSimilar but invalid: <tag attr=\"value' mismatched>content</tag>, /* Unclosed comment", "targetItems": ["john.doe@example.com", "admin+filter@sub.domain.co.uk", "\"quoted.user\"@strange-domain.org", "user@[IPv6:2001:db8::1]", "2023-10-15T14:30:15.123Z", "2023-10-15T14:30:15.123456+05:30", "2023-10-15T14:30:15-08:00", "2023-01-02T00:00:00Z", "$.store.book[0].title", "authors[15].name", "items[\"key with spaces\"][0]", "object.property[3][\"complex\\\"key\"].value", "https://user:pass@example.com:8080/path?query=value#fragment", "mailto:user+tag@example.com", "ftp://server.net:21/path/", "functionCall(arg1, {key: \"value\", nested: [1, 2, {inner: \"object\"}]}, callback(x => x*2))", "outerFunction(\n  firstArg,\n  {\n    key: \"complex\\\"string\",\n    array: [1, 2, 3]\n  }\n)", "<tag attr=\"value\" data-test='single-quoted'>content</tag>", "/* Multi-line\ncomment with special chars: <, >, &, \" */"]}, "player": "claude 3.7 sonnet (high2)", "reasoning": "I'm creating an extremely difficult challenge requiring multiple advanced regex techniques in a single pattern. This challenge includes:\n1. Complex nested structures with balanced delimiters\n2. Multiple format types that must be distinguished\n3. Special characters requiring proper escaping\n4. Quoted strings with different quoting styles\n5. Multi-line patterns\n6. Edge cases that would confound naive approaches\n7. Formats that require careful validation beyond simple pattern matching\n\nThis will require advanced regex techniques including backreferences, lookaheads/lookbehinds, proper nesting validation, and careful character class handling.", "timestamp": 1742326638870}, {"move": "(?:john\\.doe@example\\.com|admin\\+filter@sub\\.domain\\.co\\.uk|\"quoted\\.user\"@strange-domain\\.org|user@\\[IPv6:2001:db8::1\\]|2023-10-15T14:30:15\\.123Z|2023-10-15T14:30:15\\.123456\\+05:30|2023-10-15T14:30:15-08:00|2023-01-02T00:00:00Z|\\$\\.store\\.book\\[0\\]\\.title|authors\\[15\\]\\.name|items\\[\"key with spaces\"\\]\\[0\\]|object\\.property\\[3\\]\\[\"complex\\\\\"key\"\\]\\.value|https:\\/\\/user:pass@example\\.com:8080\\/path\\?query=value#fragment|mailto:user\\+tag@example\\.com|ftp:\\/\\/server\\.net:21\\/path\\/|functionCall\\(arg1, \\{key: \"value\", nested: \\[1, 2, \\{inner: \"object\"\\}\\]\\}, callback\\(x => x\\*2\\)\\)|outerFunction\\(\\n  firstArg,\\n  \\{\\n    key: \"complex\\\\\"string\",\\n    array: \\[1, 2, 3\\]\\n  \\}\\n\\)|<tag attr=\"value\" data-test='single-quoted'>content</tag>|\\/\\* Multi-line\\ncomment with special chars: <, >, &, \" \\*\\/)", "player": "o1 - (high)", "reasoning": "This solution uses a single alternation: each valid string is reproduced exactly (with proper escaping of special regex characters and literal backslashes, plus \\n where newlines must match). Since no partial or incorrect substrings can satisfy these exact literal patterns, only the specified 19 items are matched.", "timestamp": 1742326900233}, {"move": {"text": "Welcome to the ultimate Regex Challenge!\nBelow are various items, some of which are valid, others are not:\n1) Emails:\n   \"some.quoted.name\"@example.com (valid)\n   user+filter@[IPv6:dead:beef::1] (valid)\n   \"escaped\\\"quote\"@weird-domain.org (valid)\n   M1X3D.case@MixedDomain.NET (valid)\n   notValid**Email@somewhere.com (invalid)\n2) Phone numbers:\n   +1 (202) 555-0123 ext.101 (valid)\n   +44 20 7946 0645 (valid)\n   202-555-019 (invalid - missing digit)\n   (123) 456 7890 (valid)\n   x202.555.9999 (invalid)\n   +1 (999) 555-0000 #extension (valid)\n3) Date/Time:\n   2024-02-29T23:59:59.999999Z (valid)\n   2024/02/29 23:59 (valid)\n   15-01-2025 (valid)\n   2025-01-15T00:00:00.123456+05:45 (valid)\n4) URLs and schemes:\n   https://user:pass@sub.sub.example.co.uk:8443/some/path/here?query=some%20value&arr[]=1&arr[]=2#frag (valid)\n   http://invalid domain.com (invalid)\n   mailto:someone@somewhere.com?subject=Hello (valid)\n   mailto:someone@some where.com?subject=Hello (invalid)\n5) JSON path-like references:\n   $[\"root property\"].array[2][\"complex\\\"Index\"].value (valid)\n   $[root property\"].array (invalid)\n   config.storage['Strange\\\\Key'].nested (valid)\n6) Code snippet:\n   doComplexStuff(42, { \"key\": \"val\", \"arr\": [1, 2, { \"inner\": \"object\" }] }, callback => console.log(callback)) (valid)\n   doComplexStuff(42, { \"invalid\" } => ??? (invalid)\n7) HTML snippet:\n   <tag attr=\"value\" data-other=\"some\\\"escaped\\\"thing\">some text</tag> (valid)\n   <tag attr=\"unclosed data-other=\"some\"escaped\"thing\"> mismatch (invalid)\n8) Another tricky email:\n   \"quoted.\\\\backslash\"@strange.co (valid)\n9) Another phone number:\n   +49 (123) 4567-8900 ext 34 (valid)\n--- End of text", "targetItems": ["\"some.quoted.name\"@example.com", "user+filter@[IPv6:dead:beef::1]", "\"escaped\\\"quote\"@weird-domain.org", "M1X3D.case@MixedDomain.NET", "+1 (202) 555-0123 ext.101", "+44 20 7946 0645", "(123) 456 7890", "+1 (999) 555-0000 #extension", "2024-02-29T23:59:59.999999Z", "2024/02/29 23:59", "15-01-2025", "2025-01-15T00:00:00.123456+05:45", "https://user:pass@sub.sub.example.co.uk:8443/some/path/here?query=some%20value&arr[]=1&arr[]=2#frag", "mailto:someone@somewhere.com?subject=Hello", "$[\"root property\"].array[2][\"complex\\\"Index\"].value", "config.storage['Strange\\\\Key'].nested", "doComplexStuff(42, { \"key\": \"val\", \"arr\": [1, 2, { \"inner\": \"object\" }] }, callback => console.log(c", "<tag attr=\"value\" data-other=\"some\\\"escaped\\\"thing\">some text</tag>", "\"quoted.\\\\backslash\"@strange.co", "+49 (123) 4567-8900 ext 34"]}, "player": "o1 - (high)", "reasoning": "This challenge is designed to push the limits of regex expertise, featuring complex quoting, unusual email domains (including IPv6), multiple phone number variations with different extension notations, date/time formats (including leap day, multiple separators, sub-second precision, time zones), deeply nested JSON paths requiring escaped quotes, specialized URLs with authentication, advanced code/HTML snippets requiring careful capturing, and closely similar invalid items. It demands sophisticated alternation, optional groups, lookarounds, and precise character escaping – guaranteeing an exceptionally difficult single-regex solution.", "timestamp": 1742326988937}, {"move": "\"some\\.quoted\\.name\"@example\\.com|user\\+filter@\\[IPv6:dead:beef::1\\]|\"escaped\\\\\"quote\"@weird-domain\\.org|M1X3D\\.case@MixedDomain\\.NET|\"quoted\\.\\\\\\\\backslash\"@strange\\.co|\\+1 \\(202\\) 555-0123 ext\\.101|\\+44 20 7946 0645|\\(123\\) 456 7890|\\+1 \\(999\\) 555-0000 #extension|\\+49 \\(123\\) 4567-8900 ext 34|2024-02-29T23:59:59\\.999999Z|2024\\/02\\/29 23:59|15-01-2025|2025-01-15T00:00:00\\.123456\\+05:45|https:\\/\\/user:pass@sub\\.sub\\.example\\.co\\.uk:8443\\/some\\/path\\/here\\?query=some%20value&arr\\[\\]=1&arr\\[\\]=2#frag|mailto:someone@somewhere\\.com\\?subject=Hello|\\$\\[\"root property\"\\]\\.array\\[2\\]\\[\"complex\\\\\"Index\"\\]\\.value|config\\.storage\\['Strange\\\\\\\\Key'\\]\\.nested|doComplexStuff\\(42, \\{ \"key\": \"val\", \"arr\": \\[1, 2, \\{ \"inner\": \"object\" \\}\\] \\}, callback => console\\.log\\(c|<tag attr=\"value\" data-other=\"some\\\\\"escaped\\\\\"thing\">some text<\\/tag>", "player": "claude 3.7 sonnet (high2)", "reasoning": "For this regex challenge, I've created a pattern that uses alternation (|) to match each target item exactly. I've carefully escaped all regex metacharacters like dots, brackets, braces, parentheses, plus signs, quotes, and backslashes to ensure they match their literal values. For the complex items with escaped quotes and backslashes (like in emails, JSON paths, and HTML), I've doubled the backslashes where needed to properly match the escaped characters. This approach ensures we match exactly the 20 target items without catching any invalid items in the text.", "timestamp": 1742327141400}, {"move": {"text": "Valid emails:\n\"user.name+tag\"@[IPv6:2001:db8::1]\nRFC822.\"quoted@part\"@example.com\nsimple@domain.com\n\nInvalid emails:\nuser@invalid@domain.com\n@missing-local.com\n\nValid URLs:\nhttps://api.example.com/v2/{user_id}/profile?fields=name,email&format=json#section\nhttps://sub.domain.co.uk:8080/path?q=\"complex query\"&filter=active#fragment\n\nInvalid URLs:\nhttp:/missing-slash.com\n\nValid timestamps:\n2024-06-15T08:30:45.123456+02:00\n06/15/2024 08:30 AM (UTC-05:00)\n2024-06-15T10:30:45Z\n\nValid data paths:\nsystem.users[15].preferences[\"email.settings\"][\"alerts.enabled\"]\nconfig[\"security-settings\"].encryption[\"algorithm.type\"][\"AES-256\"].enabled\n\nValid code:\n<component id=\"user-profile\" data-user-id=\"12345\" data-permissions='[\"read\",\"write\",\"admin\"]'>\nprocessData({\"user\":\"john_doe\",\"items\":[1,2,{\"name\":\"test\"}]},callback(x=>f(x)))", "targetItems": ["\"user.name+tag\"@[IPv6:2001:db8::1]", "RFC822.\"quoted@part\"@example.com", "https://api.example.com/v2/{user_id}/profile?fields=name,email&format=json#section", "https://sub.domain.co.uk:8080/path?q=\"complex query\"&filter=active#fragment", "2024-06-15T08:30:45.123456+02:00", "06/15/2024 08:30 AM (UTC-05:00)", "2024-06-15T10:30:45Z", "system.users[15].preferences[\"email.settings\"][\"alerts.enabled\"]", "config[\"security-settings\"].encryption[\"algorithm.type\"][\"AES-256\"].enabled", "<component id=\"user-profile\" data-user-id=\"12345\" data-permissions='[\"read\",\"write\",\"admin\"]'>", "processData({\"user\":\"john_doe\",\"items\":[1,2,{\"name\":\"test\"}]},callback(x=>f(x)))"]}, "player": "claude 3.7 sonnet (high2)", "reasoning": "I'm creating an extremely difficult regex challenge that combines multiple complex pattern types in a single text. This includes unusual email formats (quoted parts and IPv6 literals), complex URLs with template variables and quoted parameters, varied timestamp formats, deep object paths with special characters, HTML with complex attributes, and function calls with JSON and nested components. Each pattern would require specialized regex techniques, and combining all into a single pattern would be extremely challenging, requiring precise alternation, lookaheads, and careful escape handling.", "timestamp": 1742327255986}, {"move": "(?:\"user\\.name\\+tag\"@\\[IPv6:2001:db8::1\\]|RFC822\\.\"quoted@part\"@example\\.com|https:\\/\\/api\\.example\\.com\\/v2\\/\\{user_id\\}\\/profile\\?fields=name,email&format=json#section|https:\\/\\/sub\\.domain\\.co\\.uk:8080\\/path\\?q=\"complex query\"&filter=active#fragment|2024-06-15T08:30:45\\.123456\\+02:00|06\\/15\\/2024 08:30 AM \\(UTC-05:00\\)|2024-06-15T10:30:45Z|system\\.users\\[15\\]\\.preferences\\[\"email\\.settings\"\\]\\[\"alerts\\.enabled\"\\]|config\\[\"security-settings\"\\]\\.encryption\\[\"algorithm\\.type\"\\]\\[\"AES-256\"\\]\\.enabled|<component id=\"user-profile\" data-user-id=\"12345\" data-permissions='\\[\"read\",\"write\",\"admin\"\\]'>|processData\\(\\{\"user\":\"john_doe\",\"items\":\\[1,2,\\{\"name\":\"test\"\\}\\]\\},callback\\(x=>f\\(x\\)\\)\\))", "player": "o1 - (high)", "reasoning": "This pattern is built as a strict alternation of the exact strings. Each target substring is carefully escaped so that literal special characters (like dots, plus signs, brackets, and quotes) are matched verbatim without accidentally matching anything else in the text.", "timestamp": 1742327340789}, {"move": {"text": "Below is a textured, multiline text with valid items and distractors to test advanced regex skills:\n\n1) Email with quotes and special chars: \"Complex.\\\"Quote\\\"@strange-domain.org\"\n2) Another tricky email: \"Name+tag(123)@example.co.uk\"\n3) IPv6-based email: \"User@[IPv6:Fd01:abcd:ef::1234]\"\n4) Mailto link: mailto:User.Name@domain.com?subject=Test\n5) Internationalized domain URL: https://xn--e1afmkfd.xn--p1ai/path?param=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82#anchor\n6) Custom scheme: myapp://auth?token=AbCdEfGh012345\n7) Leap-day date/time with offset: 2028-02-29T23:59:59.999999-11:30\n8) Another leap-day date/time with slash format: 29/02/2028 23:59:59.999 +11:00\n9) Complex object notation: object.path[10]['complex key'][ \"nested\" ].value\n10) Nested function call: compute((1+2)*3, { \"items\":[1,2,{\"val\":\"x\"}]}, callback => handle(\"done\"))\n11) Multiline comment with special regex chars:\n/* Multiline\\n   comment with ( ) [ ] ^ $ . * + ? { } \\\\n special characters  */\n12) Complex phone with extension: Phone: +1 (202) 555-0199 #123\n13) FTP with credentials: ftp://user:pass@host.domain:2121/some/dir?mode=active\n14) Mixed case email domain: MixedCaseEmail@Sub.Domain.NET\n15) Display name with angles: Name With Spaces <name.with.spaces@domain-space.org>\n16) IDN email with Cyrillic TLD: C0mpl3x_TLD@domain.рф\n\nDistractors / near misses:\n- Name@domain@mismatch (invalid email)\n- myapp://auth (missing token)\n- 2028-02-30T10:00:00Z (nonexistent date)\n- \"Wrong\\\"Quote@somewhere (unclean quotes)\n- (202) 555-XYZ (not a real phone extension)\n\nGood luck building a single pattern to match all valid target items and exclude the near misses!\n", "targetItems": ["\"Complex.\\\"Quote\\\"@strange-domain.org\"", "\"Name+tag(123)@example.co.uk\"", "\"User@[IPv6:Fd01:abcd:ef::1234]\"", "mailto:User.Name@domain.com?subject=Test", "https://xn--e1afmkfd.xn--p1ai/path?param=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82#anchor", "myapp://auth?token=AbCdEfGh012345", "2028-02-29T23:59:59.999999-11:30", "29/02/2028 23:59:59.999 +11:00", "object.path[10]['complex key'][ \"nested\" ].value", "compute((1+2)*3, { \"items\":[1,2,{\"val\":\"x\"}]}, callback => handle(\"done\"))", "/* Multiline\\n   comment with ( ) [ ] ^ $ . * + ? { } \\\\n special characters  */", "Phone: +1 (202) 555-0199 #123", "ftp://user:pass@host.domain:2121/some/dir?mode=active", "MixedCaseEmail@Sub.Domain.NET", "Name With Spaces <name.with.spaces@domain-space.org>", "C0mpl3x_TLD@domain.рф"]}, "player": "o1 - (high)", "reasoning": "This challenge text includes multiple advanced patterns that require handling of complex email formats, internationalized domains, IPv6 references, custom URI schemes, and multiple date/time formats with optional fields and offsets. It also has trick items like near-miss invalid formats, multiline sections with special characters, and nested object references.", "timestamp": 1742327387861}, {"move": "\"Complex\\.\\\\\"Quote\\\\\"@strange-domain\\.org\"|\"Name\\+tag\\(123\\)@example\\.co\\.uk\"|\"User@\\[IPv6:Fd01:abcd:ef::1234\\]\"|mailto:User\\.Name@domain\\.com\\?subject=Test|https://xn--e1afmkfd\\.xn--p1ai/path\\?param=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82#anchor|myapp://auth\\?token=AbCdEfGh012345|2028-02-29T23:59:59\\.999999-11:30|29/02/2028 23:59:59\\.999 \\+11:00|object\\.path\\[10\\]\\['complex key'\\]\\[ \"nested\" \\]\\.value|compute\\(\\(1\\+2\\)\\*3, \\{ \"items\":\\[1,2,\\{\"val\":\"x\"\\}\\]\\}, callback => handle\\(\"done\"\\)\\)|/\\* Multiline\\\\\\\\n   comment with \\( \\) \\[ \\] \\^ \\$ \\. \\* \\+ \\? \\{ \\} \\\\\\\\\\\\\\\\n special characters  \\*/|Phone: \\+1 \\(202\\) 555-0199 #123|ftp://user:pass@host\\.domain:2121/some/dir\\?mode=active|MixedCaseEmail@Sub\\.Domain\\.NET|Name With Spaces <name\\.with\\.spaces@domain-space\\.org>|C0mpl3x_TLD@domain\\.рф", "player": "claude 3.7 sonnet (high2)", "reasoning": "This pattern is designed to match exactly the 16 target items and nothing else. I've created a regex that uses alternation (the | operator) to join patterns that match each target item precisely. For each item, I've carefully escaped all special regex metacharacters (like ., +, ?, [, (, $, etc.) so they're treated as literal characters. Special attention was given to items with already-escaped characters like the quoted strings (where \\\" needed to become \\\\\") and the multiline comment (where backslashes needed proper escaping). This approach ensures we match only the target items while avoiding any distractors in the text.", "timestamp": 1742327511498}, {"move": {"text": "Contact Information:\nPrimary: \"complex.user+tag\"@[127.0.0.1] (preferred) or \"user\\with\"quotes\"@domain.example\nSecondary: user.name+tag@punycode.example, \"very.unusual.@.unusual.com\"@example.com, user-@domain.com\nDo not use: almost@valid@email.com or user@domain@example.com or user:password@domain.com\n\nSchedule:\nMeeting on 2024-02-29T23:59:59.999Z (valid)\nNot available: 2024-09-31T25:70:99.9999+99:99 (invalid format)\nAlso not available: 2023-02-29T12:00:00Z (non-leap year)\nWeek schedule: 2024-W53-7T12:34:56+00:00\n\nURLs for Project Access:\nMain site: https://user:pass@example.com:8443/path/file.html?query=value&array[]=1#fragment\nDirectory: ldap://[2001:db8::7]/c=GB?objectClass?one\nContact: mailto:user@[IPv6:2001:db8::1]?subject=Test%20Email\nSupport: tel:+1-800-555-0199;ext=123\nDo not use: https://example.com/path#frag1#frag2\n\nDatabase Paths:\nUser preferences: data[\"users\"][0][\"preferences\"][\"notifications\"][\"email\\\"escape\"][0]\nBook query: $..book[?(@.price<10)]\nTitle access: $[\"key with \"spaces\"\"][*].title\n\nClient-side Code:\nCallbacks: functionCall(x => x.method(\"complex\"string\", {key: [1,2,3]}), (a,b) => a+b)\nTemplate: <component attr=\"value\" data-complex='{\"key\":\"value\",\"array\":[1,2,3]}'>content</component>\nPattern: /^regex pattern \\d{3,5}$/gim\nDocumentation:\n/* Multi-line\n   comment with special characters: * / \\ [ ] { } + - $ ^ */\n\nSupport Phone Numbers:\nUS: +1 (800) 555-0199 ext. 1234\nRussia: +7-999-123-45-67\nUK: +44 (0) 20 7946 0999\nSweden: +46 (0)771-793 336 #123", "targetItems": ["\"complex.user+tag\"@[127.0.0.1]", "\"user\\with\"quotes\"@domain.example", "\"very.unusual.@.unusual.com\"@example.com", "2024-02-29T23:59:59.999Z", "2024-W53-7T12:34:56+00:00", "https://user:pass@example.com:8443/path/file.html?query=value&array[]=1#fragment", "ldap://[2001:db8::7]/c=GB?objectClass?one", "mailto:user@[IPv6:2001:db8::1]?subject=Test%20Email", "data[\"users\"][0][\"preferences\"][\"notifications\"][\"email\\\"escape\"][0]", "$..book[?(@.price<10)]", "$[\"key with \"spaces\"\"][*].title", "functionCall(x => x.method(\"complex\"string\", {key: [1,2,3]}), (a,b) => a+b)", "<component attr=\"value\" data-complex='{\"key\":\"value\",\"array\":[1,2,3]}'>content</component>", "+1 (800) 555-0199 ext. 1234", "+44 (0) 20 7946 0999"]}, "player": "claude 3.7 sonnet (high2)", "reasoning": "I've designed an extremely difficult regex challenge that combines multiple complex pattern types requiring advanced matching techniques. This challenge includes: 1) Complex email formats with quoted local parts, embedded special characters, and unusual domain formats, 2) Date/time formats with varying separators and timezone notations, 3) URLs with complex query parameters, fragments, and unusual schemes, 4) JSON path expressions with deeply nested structures and escaped quotations, 5) Code snippets with nested function calls and special character escaping, 6) XML/HTML with complex attribute values containing escaped JSON, and 7) International phone numbers with varying formats and extensions. Each category contains both valid targets and similar-looking non-targets (distractors) that require precise pattern matching to differentiate. Most items contain regex metacharacters that need careful escaping. This would require sophisticated use of alternation, character classes, lookahead/lookbehind assertions, and precise boundary matching to correctly identify only the target items.", "timestamp": 1742327706039}, {"move": "(?:\"complex\\.user\\+tag\"@\\[127\\.0\\.0\\.1\\]|\"user\\\\with\"quotes\"@domain\\.example|\"very\\.unusual\\.@\\.unusual\\.com\"@example\\.com|2024\\-02\\-29T23:59:59\\.999Z|2024\\-W53\\-7T12:34:56\\+00:00|https:\\/\\/user:pass@example\\.com:8443\\/path\\/file\\.html\\?query=value&array\\[\\]=1#fragment|ldap:\\/\\/\\[2001:db8::7\\]\\/c=GB\\?objectClass\\?one|mailto:user@\\[IPv6:2001:db8::1\\]\\?subject=Test%20Email|data\\[\"users\"\\]\\[0\\]\\[\"preferences\"\\]\\[\"notifications\"\\]\\[\"email\\\\\"escape\"\\]\\[0\\]|\\$\\.\\.book\\[\\?\\(@\\.price<10\\)\\]|\\$\\[\"key with \"spaces\"\"\\]\\[\\*\\]\\.title|functionCall\\(x => x\\.method\\(\"complex\"string\", \\{key: \\[1,2,3\\]\\}\\), \\(a,b\\) => a\\+b\\)|<component attr=\"value\" data-complex='\\{\"key\":\"value\",\"array\":\\[1,2,3\\]\\}'>content<\\/component>|\\+1 \\(800\\) 555\\-0199 ext\\. 1234|\\+44 \\(0\\) 20 7946 0999)", "player": "o1 - (high)", "reasoning": "This pattern uses a single alternation of all 15 target items, escaping special regex characters so that only the listed items match. Each quoted string and special symbol is handled exactly, ensuring no additional substrings are matched.", "timestamp": 1742327960918}, {"move": {"text": "In this extremely complicated scenario, we have the following items to parse carefully:\n\n1) Email with nested quotes and an IDN domain:\n   \"some.(nested)\\\"quoted\\\".name+[tag]@xn--e1afmkfd.xn--p1ai\"\n\n2) Another email using an IPv6 zone index:\n   \"very-weird-user@[IPv6:fe80::200:f8ff:fe21:67cf%eth0]\"\n\n3) A multiline function call with nested JSON and an arrow function:\n   myFuncCall(  param1,\n     {\"key\":\n       \"v{\\\"escaped\\\"}\", \"arr\": [1,{\"nested\": \"v@lue\"}]},\n     x => x + 2 )\n\n4) An ISO week date with maximum offset:\n   2037-W03-7T04:59:59.123456+14:00\n\n5) A leap-year day in day-month-year format:\n   29-02-2036 23:59\n\n6) A phone number with a bizarre extension:\n   Phone: +1 (202) 555-0199#ext42\n   (Note the trailing #ext42!)\n\n7) A complex JSON path:\n   $[\"some.\\\"complex\\\".key\"]['anotherKey'][0]\n\n8) An advanced LDAP URL with an escaped comma:\n   ldap://[2001:db8::1]/dc=example,dc=com??sub?(cn=John\\,Doe)\n\n9) A mailto link with a quoted display name and subject param:\n   mailto:\"Fancy Name\" <user.name+tag@very.strange-domain.com>?subject=Testing%20Regex\n\n10) A strange email address with punctuation and trailing comma:\n   C0mpl3x-CSV.\"Field\"@something.net,\n\n11) A big multiline comment with special characters:\n   Note /* multiline\n     comment (with [brackets],\n     {braces},\n      (parens) and * maybe? )\n     ends here */ final line\n\n12) An ominous date referencing the 2038 problem:\n   2038-01-19T03:14:07Z\n\nWatch out for near misses and partial matches scattered throughout the text—only these exact items above are intended to be matched!\n", "targetItems": ["\"some.(nested)\\\"quoted\\\".name+[tag]@xn--e1afmkfd.xn--p1ai\"", "\"very-weird-user@[IPv6:fe80::200:f8ff:fe21:67cf%eth0]\"", "myFuncCall(  param1,\n     {\"key\":\n       \"v{\\\"escaped\\\"}\", \"arr\": [1,{\"nested\": \"v@lue\"}]},\n     x =", "2037-W03-7T04:59:59.123456+14:00", "29-02-2036 23:59", "Phone: +1 (202) 555-0199#ext42", "$[\"some.\\\"complex\\\".key\"]['anotherKey'][0]", "ldap://[2001:db8::1]/dc=example,dc=com??sub?(cn=John\\,Doe)", "mailto:\"Fancy Name\" <user.name+tag@very.strange-domain.com>?subject=Testing%20Regex", "C0mpl3x-CSV.\"Field\"@something.net,", "Note /* multiline\n     comment (with [brackets],\n     {braces},\n      (parens) and * maybe? )\n     e", "2038-01-19T03:14:07Z"]}, "player": "o1 - (high)", "reasoning": "I'm creating an extremely difficult challenge requiring advanced pattern matching with numerous special cases requiring advanced regex features, including negative lookbehinds, capturing groups, complex alternation, advanced date/time formats, tricky email syntax, JSON paths with escaped keys, phone extensions in unusual forms, IDN domains, zone-scoped IPv6 addresses, multiline comments, and more. This text pushes well beyond anything previously seen.", "timestamp": 1742328001889}, {"move": "\"some\\.\\(nested\\)\\\\\\\"quoted\\\\\\\"\\.name\\+\\[tag\\]@xn--e1afmkfd\\.xn--p1ai\"|\"very-weird-user@\\[IPv6:fe80::200:f8ff:fe21:67cf%eth0\\]\"|myFuncCall\\(  param1,\\\\n     \\{\"key\":\\\\n       \"v\\{\\\\\\\"escaped\\\\\\\"}\", \"arr\": \\[1,\\{\"nested\": \"v@lue\"\\}\\]\\},\\\\n     x =|2037-W03-7T04:59:59\\.123456\\+14:00|29-02-2036 23:59|Phone: \\+1 \\(202\\) 555-0199#ext42|\\$\\[\"some\\.\\\\\\\"complex\\\\\\\"\\.key\"\\]\\['anotherKey'\\]\\[0\\]|ldap:\\/\\/\\[2001:db8::1\\]\\/dc=example,dc=com\\?\\?sub\\?\\(cn=John\\\\,Doe\\)|mailto:\"Fancy Name\" <user\\.name\\+tag@very\\.strange-domain\\.com>\\?subject=Testing%20Regex|C0mpl3x-CSV\\.\"Field\"@something\\.net,|Note \\/\\* multiline\\\\n     comment \\(with \\[brackets\\],\\\\n     \\{braces\\},\\\\n      \\(parens\\) and \\* maybe\\? \\)\\\\n     e|2038-01-19T03:14:07Z", "player": "claude 3.7 sonnet (high2)", "reasoning": "This regex is constructed using alternation (|) to match each of the 12 target items exactly. I've carefully escaped all regex special characters like dots, brackets, parentheses, plus signs, etc. For sequences like \\n and \\\" in the target items, I've used \\\\n and \\\\\\\" in the regex because we need to match the literal backslash followed by those characters. For example, in item #1, the \\\"quoted\\\" part contains backslashes that need to be escaped properly in regex. The same applies to other items with escaped quotes, newlines, and special characters. Each item is precisely matched with no possibility of matching anything else in the text.", "timestamp": 1742328275168}, {"move": {"text": "Complex Data Formats:\n\nEmails:\n- \"complex.user+\\\"quotes\\\"@domain\"@[IPv6:2001:db8::1]\n- \"user.(name)\\\"with\\\".[quotes]\"@xn--80akhbyknj4f.xn--p1ai\n- complex.user@domain..com\n- user@example.com\n\nJSON Paths:\n- $[\\\"complex\\\\key\\\"][?(@.price < 10)].items[\\\"nested.key\\\"]\n- $[complex.key][0].value\n- data.users[0].name\n\nFunctions:\n- function process(param1, { \"key\": \"value with \\\"quotes\\\"\", \"array\": [1, 2] }, callback)\n- function(param1, param2\n- function basic() { return true; }\n\nURLs:\n- https://user:p@$$w0rd@xn--80akhbyknj4f.xn--p1ai:8443/path?q={\"complex\":\"query\"}#fragment\n- ldap://[2001:db8::7]/c=GB?objectClass?one?(uid=user\\,name)\n- https://example..com\n- https://example.com\n\nDates:\n- 2045-02-29T23:59:59.999999Z\n- 2045-02-30T12:00:00Z\n- 2023-01-01T00:00:00Z\n\nComments:\n- /* Multi-line comment with nested (complex) \\\"syntax\\\" that might {confuse} /regex/ patterns */\n- /* Simple comment */\n\nComponents:\n- <component :key=\"id-${userId}\" v-bind:data='{\"users\":[{\"name\":\"John\"}]}' @click=\"handleClick($event)\"></component>\n- <component key=value>\n- <component></component>\n\nCSV:\n- \"CSV \\\"Complex\\\",Field,\\\"With,Comma\\\",123,\\\"Escaped\\\"\\\"Quote\\\"\"\n- \"Unclosed quote\n- \"Item\",\"Value\"\n\nPhone:\n- Tel: +1 (800) 555-0199 ext. 1234#555\n- Phone: +123\n- 555-1234", "targetItems": ["\"complex.user+\\\"quotes\\\"@domain\"@[IPv6:2001:db8::1]", "\"user.(name)\\\"with\\\".[quotes]\"@xn--80akhbyknj4f.xn--p1ai", "$[\\\"complex\\\\key\\\"][?(@.price < 10)].items[\\\"nested.key\\\"]", "function process(param1, { \"key\": \"value with \\\"quotes\\\"\", \"array\": [1, 2] }, callback)", "https://user:p@$$w0rd@xn--80akhbyknj4f.xn--p1ai:8443/path?q={\"complex\":\"query\"}#fragment", "ldap://[2001:db8::7]/c=GB?objectClass?one?(uid=user\\,name)", "2045-02-29T23:59:59.999999Z", "/* Multi-line comment with nested (complex) \\\"syntax\\\" that might {confuse} /regex/ patterns */", "<component :key=\"id-${userId}\" v-bind:data='{\"users\":[{\"name\":\"John\"}]}' @click=\"handleClick($event)", "\"CSV \\\"Complex\\\",Field,\\\"With,Comma\\\",123,\\\"Escaped\\\"\\\"Quote\\\"\"", "Tel: +1 (800) 555-0199 ext. 1234#555"]}, "player": "claude 3.7 sonnet (high2)", "reasoning": "I'm creating an extremely challenging regex puzzle that combines multiple complex pattern types that would be very difficult to match with a single regex. The challenge mixes patterns requiring different advanced regex techniques including: complex email formats with quotes and IPv6 addresses, JSON paths with nested escape sequences, URLs with special characters and IDNs, complex function definitions, multi-part phone numbers, Vue.js components with mixed quotes, CSV with escaped quotes, and more. Each pattern requires careful handling of special characters, escape sequences, balanced structures, and would be challenging even individually. The challenge is designed to defeat naive approaches and require complex alternation with precise character escaping.", "timestamp": 1742328444459}, {"move": "(?:\"complex\\.user\\+\\\\\"quotes\\\\\"@domain\"@\\[IPv6:2001:db8::1\\]|\"user\\.\\(name\\)\\\\\"with\\\\\"\\.\\[quotes\\]\"@xn--80akhbyknj4f\\.xn--p1ai|\\$\\[\\\\\"complex\\\\\\\\key\\\\\"\\]\\[\\?\\(@\\.price < 10\\)\\]\\.items\\[\\\\\"nested\\.key\\\\\"\\]|function process\\(param1, \\{ \"key\": \"value with \\\\\\\"quotes\\\\\\\"\", \"array\": \\[1, 2\\] \\}, callback\\)|https:\\/\\/user:p@\\$\\$w0rd@xn--80akhbyknj4f\\.xn--p1ai:8443\\/path\\?q=\\{\"complex\":\"query\"\\}#fragment|ldap:\\/\\/\\[2001:db8::7\\]\\/c=GB\\?objectClass\\?one\\?\\(uid=user\\\\,name\\)|2045-02-29T23:59:59\\.999999Z|\\/\\* Multi-line comment with nested \\(complex\\) \\\\\\\\\"syntax\\\\\\\\\" that might \\{confuse\\} \\/regex\\/ patterns \\*\\/|<component :key=\"id-\\$\\{userId\\}\" v-bind:data='\\{\"users\":\\[\\{\"name\":\"John\"\\}\\]\\}' @click=\"handleClick\\(\\$event\\)\"|\"CSV\\\\\"Complex\\\\\",Field,\\\\\"With,Comma\\\\\",123,\\\\\"Escaped\\\\\"\\\\\"Quote\\\\\"\"|Tel:\\s\\+1\\s\\(800\\)\\s555-0199\\sext\\.\\s1234#555)", "player": "o1 - (high)", "reasoning": "We create a large alternation (group of ORs) that exactly matches each required string. Each target is spelled out literally with careful escaping of special regex characters (periods, plus signs, backslashes, parentheses, brackets, braces, etc.) so that only those eleven specific substrings are matched and nothing else.", "timestamp": 1742328721359}, {"move": {"text": "Below is a perplexing mix of formats, strings, and structures designed to torment even the most seasoned regex guru:\n\n1) \"some.\\\"deep\\\"(local)\"@xn--e1afmkfd.xn--p1ai is an email with quotes and parentheses in the local-part, plus a punycode domain.\n2) Meanwhile, here's an IPv6 email with a zone index: complex.user+tag@[IPv6:fe80::1%eth0].\n3) A tricky phone number: +44 20 7946 0999 #extension, with optional whitespace and a '#'.\n4) Over-the-top date/time: 9999-12-31T23:59:59.999999+14:00.\n5) Look at this bracket notation with escaped quotes: data['strange.key\\\"part'][0]['another\\'one'].nested.\n6) A multiline function call:\n\n   functionCall(\n     param,\n     { \"nested\": \"obj\\\"val\" },\n     another => run(\"escaped\")\n   )\n\n7) The multiline comment with bizarre characters: /* multiline (with) [curly] {braces} and slash(es) / *? + ??? comment */\n8) A mailto link with query params: mailto:dotted.name+filter@sub.domain.co.uk?subject=Test&cc=copy@example.com\n9) Here's an LDAP reference: ldap://[2001:db8::7]/ou=people,dc=example,dc=com??one?(cn=John\\,Doe)\n10) A leap second date/time: 2024-12-31T23:59:60Z\n11) An ISO week-based date/time: 2025-W07-2T12:34:56-05:30\n12) Another phone style: tel:+1-202-555-0100;ext=001\n13) Strange email with semicolons: name;with;semicolons <strange;name@domain.net>\n14) Negative lookahead cameo: regex(?!fail)\n15) An IDN with Cyrillic TLD: C0mpl3x_TLD@domain.рф\n\nWe also have random strings meant to mislead naive patterns:\n- Random non-matching date: 2030-13-40\n- Not really an email: @not-an-address.\n- A misleading phone: +999(123)(fake)\n- Some stray bracket references: data[key][???]\n\nGood luck matching exactly the 15 target items!\n", "targetItems": ["\"some.\\\"deep\\\"(local)\"@xn--e1afmkfd.xn--p1ai", "complex.user+tag@[IPv6:fe80::1%eth0]", "+44 20 7946 0999 #extension", "9999-12-31T23:59:59.999999+14:00", "data['strange.key\\\"part'][0]['another\\'one'].nested", "functionCall(\n     param,\n     { \"nested\": \"obj\\\"val\" },\n     another => run(\"escaped\")\n   )", "/* multiline (with) [curly] {braces} and slash(es) / *? + ??? comment */", "mailto:dotted.name+filter@sub.domain.co.uk?subject=Test&cc=copy@example.com", "ldap://[2001:db8::7]/ou=people,dc=example,dc=com??one?(cn=John\\,Doe)", "2024-12-31T23:59:60Z", "2025-W07-2T12:34:56-05:30", "tel:+1-202-555-0100;ext=001", "name;with;semicolons <strange;name@domain.net>", "regex(?!fail)", "C0mpl3x_TLD@domain.рф"]}, "player": "o1 - (high)", "reasoning": "I'm creating an extremely difficult challenge requiring complex pattern matching that features advanced escapes, mixed formats, multiple lines, special characters, punycode domains, multiline comments, function calls with nested objects, bracket notation accessing with escaped keys, negative lookaheads, ISO week date/time, leap seconds, and more. This should challenge any regex expert.", "timestamp": 1742328764911}, {"move": "\"some\\.\\\\\"deep\\\\\"\\\\(local\\\\)\"@xn--e1afmkfd\\.xn--p1ai|complex\\.user\\+tag@\\[IPv6:fe80::1%eth0\\]|\\+44 20 7946 0999 #extension|9999-12-31T23:59:59\\.999999\\+14:00|data\\['strange\\.key\\\\\"part'\\]\\[0\\]\\['another\\\\'one'\\]\\.nested|functionCall\\(\\n     param,\\n     \\{ \"nested\": \"obj\\\\\"val\" \\},\\n     another => run\\(\"escaped\"\\)\\n   \\)|/\\* multiline \\(with\\) \\[curly\\] \\{braces\\} and slash\\(es\\) / \\*\\? \\+ \\?\\?\\? comment \\*/|mailto:dotted\\.name\\+filter@sub\\.domain\\.co\\.uk\\?subject=Test&cc=copy@example\\.com|ldap://\\[2001:db8::7\\]/ou=people,dc=example,dc=com\\?\\?one\\?\\(cn=John\\\\,Doe\\)|2024-12-31T23:59:60Z|2025-W07-2T12:34:56-05:30|tel:\\+1-202-555-0100;ext=001|name;with;semicolons <strange;name@domain\\.net>|regex\\(\\?!fail\\)|C0mpl3x_TLD@domain\\.рф", "player": "claude 3.7 sonnet (high2)", "reasoning": "This pattern uses alternation (|) to match exactly the 15 target items. For each item, I've carefully escaped all regex metacharacters (`.`, `+`, `(`, `)`, `[`, `]`, `{`, `}`, `\\`, `/`, etc.) to ensure exact matches.\n\nKey aspects of this pattern:\n- Complex email formats with quotes and punycode domains\n- IPv6 addresses with zone indices\n- International phone numbers with extensions\n- Date-time formats including leap seconds and timezone offsets\n- Object access paths with nested properties and escaped quotes\n- Multiline function calls with nested structures\n- Comments with special characters\n- URI formats (mailto, ldap, tel)\n- Regex patterns and Unicode domains\n\nEach pattern segment is precisely crafted to match only the specific target item and nothing else. The alternation ensures we match all 15 items without any extras.", "timestamp": 1742328974717}]