M src/daemon/spawn.ts → src/daemon/spawn.ts

@@ -32,16 +32,6 @@ if (isWindows) return;
   unlink(DAEMON_SOCKET_PATH).catch(() => {});
 };
 
-/**
- * Whether the daemon endpoint could plausibly exist, judged without connecting.
- *
- * On POSIX a missing socket file means the daemon definitely isn't running, so
- * callers can short-circuit. Windows named pipes are NOT filesystem entries —
- * access() always fails on `\\.\pipe\…` even while the daemon is serving it — so
- * on Windows the answer is always "maybe" and the caller must probe instead.
- *
- * Platform and path are parameters so the branch is testable off-platform.
- */
 export const daemonSocketMayExist = async (
   platform: NodeJS.Platform = process.platform,
   socketPath: string = DAEMON_SOCKET_PATH,

M src/domains/fill-engine.ts → src/domains/fill-engine.ts

@@ -1,18 +1,3 @@
-/**
- * The one in-page fill implementation, shared by browser_fill and
- * browser_fill_form so the two can no longer disagree about the same element.
- *
- * `this` is the target element and `value` is the requested value. Two call-site
- * differences are parameters rather than forks:
- *   rejectSelect — browser_fill refuses a <select> and points at
- *                  browser_select_option; browser_fill_form fills it.
- *   focusFirst   — browser_fill_form focuses the field first; browser_fill
- *                  documents that it does not move focus.
- *
- * Returns a PageResult (see form.ts): { ok, reason?, kind?, value?, text?,
- * checked?, changed?, options?, tag? }.
- */
-
 export type FillOptions = {
   readonly rejectSelect: boolean;
   readonly focusFirst: boolean;