test: update coverage comment to reflect current reality

- Remove all historical references (#48, first-principles, newly extracted, etc.)
- Remove mentions of deleted components (5s Timer, old copy state machine)
- Make the comment strictly about what the tests actually cover and the real shortcoming (no automated QML coverage)
- Per request: code comments exist to explain the code, not preserve history

test/lib.test.js

@@ -4,16 +4,13 @@ import lib from "../tailscalectl/lib.js"
 const { parsePeers, makeExitNodeCommand, findActiveExitNode, errorMessage, formatError, getStatusCommand, isValidExitNodeHostname, getClipboardCommands, buildToggleCommand, parseStatusResult, getStrings, shouldShowClearExitNode, isActiveExitNode } = lib
 
 /*
- * Test coverage note for #48:
+ * Unit tests for the pure functions exported from lib.js.
- * All pure functions exported from lib.js (including the newly extracted
- * getStrings, shouldShowClearExitNode, isActiveExitNode, and getClipboardCommands
- * are exercised here via node:test.
  *
- * The four Process objects, 5-second Timer, onExited handlers, copy fallback
+ * All functions in lib.js are exercised via Node's built-in test runner.
- * state machine, and overall widget behavior in TailscaleWidget.qml have no
+ *
- * automated test coverage. There is no QML test runner in this project.
+ * TailscaleWidget.qml has no automated test coverage. The four Process
- * Those paths are verified manually (see verification checklist in the
+ * objects, their onExited handlers, and all widget UI behavior must be
- * feature branch commits).
+ * verified manually.
  */
 
 test("parsePeers extracts exitNode from ExitNodeOption", () => {