[autofix.ci] apply automated fixes

The previous fix for middle dot characters accidentally broke $ and _
character parsing in JavaScript identifiers. These characters are
special cases in ECMAScript that must be explicitly added to the
ID_Start and ID_Continue sets, as they are not included in the
standard Unicode categories.

This restores support for:
- $ in destructuring: import { $ } from "bun"
- _ in variable names: const _private = 123
- All other $ and _ usage in identifiers

While maintaining the fix for Japanese middle dot characters.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

misctools/gen-unicode-table.ts

@@ -20,8 +20,9 @@ const idContinueES5Set = new Set([
 const idStartESNextSet = new Set(require("@unicode/unicode-15.1.0/Binary_Property/ID_Start/code-points"));
 const idContinueESNextSet = new Set(require("@unicode/unicode-15.1.0/Binary_Property/ID_Continue/code-points"));
 
-// Exclude known problematic codepoints
-const ID_Continue_mistake = new Set([0x30fb, 0xff65]);
+// Note: Previously excluded middle dot characters (0x30fb, 0xff65) but these are valid 
+// in Node.js and ECMAScript specification, so they should be included
+const ID_Continue_mistake = new Set();
 
 function bitsToU64Array(bits: number[]): bigint[] {
   const result: bigint[] = [];
@@ -82,12 +83,12 @@ async function main() {
     {
       name: "isIDStartESNext",
       table: "idStartESNext",
-      check: (cp: number) => idStartESNextSet.has(cp),
+      check: (cp: number) => idStartESNextSet.has(cp) || cp === 0x24 || cp === 0x5F, // Add $ and _
     },
     {
       name: "isIDContinueESNext",
       table: "idContinueESNext",
-      check: (cp: number) => idContinueESNextSet.has(cp) && !ID_Continue_mistake.has(cp),
+      check: (cp: number) => (idContinueESNextSet.has(cp) && !ID_Continue_mistake.has(cp)) || cp === 0x24 || cp === 0x5F, // Add $ and _
     },
   ];
 

test/regression/issue/22230.test.ts

@@ -0,0 +1,50 @@
+import { expect, test } from "bun:test";
+
+test("Japanese middle dot character should be allowed in identifier names", () => {
+  // Test the full-width middle dot (・) character U+30FB
+  const code1 = `
+    const obj = {
+      "バス・トイレ": "bathroom"
+    };
+    obj["バス・トイレ"];
+  `;
+  expect(() => eval(code1)).not.toThrow();
+
+  // Test unquoted property with middle dot
+  const code2 = `
+    const obj = {
+      バス・トイレ: "bathroom"
+    };
+    obj["バス・トイレ"];
+  `;
+  expect(() => eval(code2)).not.toThrow();
+
+  // Test variable name with middle dot continuation
+  const code3 = `
+    let test・variable = 42;
+    test・variable;
+  `;
+  expect(() => eval(code3)).not.toThrow();
+
+  // Test the half-width middle dot (･) character U+FF65 as well
+  const code4 = `
+    const obj = {
+      test･value: "test"
+    };
+    obj["test･value"];
+  `;
+  expect(() => eval(code4)).not.toThrow();
+});
+
+test("Middle dot should not be allowed at start of identifier", () => {
+  // Middle dot should NOT be allowed as identifier start
+  const code1 = `
+    var ・test = 1;
+  `;
+  expect(() => eval(code1)).toThrow();
+
+  const code2 = `
+    var ･test = 1;
+  `;
+  expect(() => eval(code2)).toThrow();
+});