chore(github): use TSDoc for the new wiring comments

Author: waleedlatif1

apps/sim/blocks/blocks/github.param-wiring.test.ts

@@ -3,9 +3,11 @@
  */
 import { describe, expect, it, vi } from 'vitest'
 
-// vitest.setup.ts stubs `@/tools/registry` to an empty map so unrelated suites
-// do not pay to load every tool. This suite asserts against the REAL tool
-// params, so it opts back in.
+/**
+ * Uses the real tool registry: these assertions are about the params GitHub's
+ * tools actually declare, which the global `@/tools/registry` mock in
+ * vitest.setup.ts empties.
+ */
 vi.unmock('@/tools/registry')
 
 import { GitHubBlock, GitHubV2Block } from '@/blocks/blocks/github'

apps/sim/blocks/blocks/github.ts

@@ -2311,8 +2311,12 @@ Return ONLY the timestamp string - no explanations, no quotes, no extra text.`,
         if (params.fork_name) result.name = params.fork_name
         if (params.fork_sort) result.sort = params.fork_sort
 
-        // A dropdown stores its option id, so this arrives as the string
-        // 'true'/'false' while the tool declares `public` as a boolean.
+        /**
+         * A dropdown stores its option id, so this arrives as the string
+         * 'true'/'false' while the tool declares `public` as a boolean. The
+         * generic handler only JSON-parses `json`/`array` inputs, so nothing
+         * else coerces it.
+         */
         if (params.gist_public) {
           result.public = params.gist_public === true || params.gist_public === 'true'
         }