chore(sync): cascade socket-hook marker fix from socket-repo-template

Pre-commit/pre-push scanners and the logger-guard hook now recognize
`//` and `/* */` comment prefixes in addition to `#`, so `.ts`/`.mts`
files can use `// socket-hook: allow logger` naturally.

Author: jdalton

.claude/hooks/logger-guard/index.mts

@@ -68,7 +68,11 @@ const LOGGER_LEAK_RE =
 
 const COMMENT_LINE_RE = /^\s*(\*|\/\/|#)/
 const JSDOC_TAG_RE = /@(example|param|returns?|see|link)\b/
-const SOCKET_HOOK_MARKER_RE = /#\s*socket-hook:\s*allow(?:\s+([\w-]+))?/
+// Accept `#`, `//`, or `/*` comment prefixes — same as the git pre-
+// commit/pre-push scanners. This hook is invoked on TS/JS edits where
+// `// socket-hook: allow logger` is the only natural spelling.
+const SOCKET_HOOK_MARKER_RE =
+  /(?:#|\/\/|\/\*)\s*socket-hook:\s*allow(?:\s+([\w-]+))?/
 
 function isMarkerSuppressed(line: string): boolean {
   const m = line.match(SOCKET_HOOK_MARKER_RE)

.claude/hooks/logger-guard/test/logger-guard.test.mts

@@ -115,6 +115,28 @@ test('respects bare # socket-hook: allow marker', async () => {
   assert.equal(code, 0)
 })
 
+test('respects // socket-hook: allow logger marker (slash-slash prefix)', async () => {
+  const { code } = await runHook({
+    tool_name: 'Edit',
+    tool_input: {
+      file_path: 'src/foo.ts',
+      new_string: 'process.stderr.write(buf) // socket-hook: allow logger',
+    },
+  })
+  assert.equal(code, 0)
+})
+
+test('respects /* socket-hook: allow logger */ marker (block-comment prefix)', async () => {
+  const { code } = await runHook({
+    tool_name: 'Edit',
+    tool_input: {
+      file_path: 'src/foo.ts',
+      new_string: 'console.error("a") /* socket-hook: allow logger */',
+    },
+  })
+  assert.equal(code, 0)
+})
+
 test('does not flag JSDoc examples', async () => {
   const { code } = await runHook({
     tool_name: 'Write',

.git-hooks/_helpers.mts

@@ -102,8 +102,15 @@ const PERSONAL_PATH_PLACEHOLDER_RE =
 
 // Per-line opt-out marker for our pre-commit / pre-push scanners.
 //
-// Canonical form:    # socket-hook: allow
-// Targeted form:     # socket-hook: allow <rule>
+// Canonical form:    <comment-prefix> socket-hook: allow
+// Targeted form:     <comment-prefix> socket-hook: allow <rule>
+//
+// `<comment-prefix>` is whichever comment style the host file uses —
+// `#` for shell / YAML / TOML / Dockerfile, `//` for TS / JS / Rust /
+// Go / C-family, or `/*` for the C-block-comment opener. The hook is
+// invoked from many file types; pinning to `#` made the marker fail
+// silently in `.ts` / `.mts` files (where `// socket-hook: allow` is
+// the only sensible spelling) and confused contributors.
 //
 // The targeted form names a specific rule (`personal-path`, `npx`,
 // `aws-key`, etc.) and is recommended for reviewers; the bare `allow`
@@ -113,8 +120,9 @@ const PERSONAL_PATH_PLACEHOLDER_RE =
 // Legacy `# zizmor: ...` markers are still recognized for one cycle so
 // existing files don't have to be rewritten in the same change that
 // renames the marker.
-const SOCKET_HOOK_MARKER_RE = /#\s*socket-hook:\s*allow(?:\s+([\w-]+))?/
-const LEGACY_ZIZMOR_MARKER_RE = /#\s*zizmor:\s*[\w-]+/
+const SOCKET_HOOK_MARKER_RE =
+  /(?:#|\/\/|\/\*)\s*socket-hook:\s*allow(?:\s+([\w-]+))?/
+const LEGACY_ZIZMOR_MARKER_RE = /(?:#|\/\/|\/\*)\s*zizmor:\s*[\w-]+/
 
 function lineIsSuppressed(line: string, rule?: string): boolean {
   if (LEGACY_ZIZMOR_MARKER_RE.test(line)) {