docs: address Qodo review on PR #21 (#22)

Two findings, both legit:

1. README settings.json snippet contradicted its preceding comment —
   comment talked about "disabling the passthrough" but the snippet
   set the flag to true (enable). Rewrote the prose to be unambiguous:
   the snippet is an explicit opt-in for older 3.x cores; mention
   `false` as the disable case in the same comment.

2. pad-select-server.js / pad-toggle-server.js comments framed the
   warning case as "explicit operator opt-out", but the runtime check
   is `=== true`, so the false branch also fires when the flag is
   absent (pre-flip cores, or operators who removed the key). Reworded
   to cover both cases — "absent on pre-flip cores, or explicitly
   false on current ones" — so future maintainers debugging
   padWideSupported off don't chase a phantom opt-out.

Behavior unchanged.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: JohnMcLear

README.md

@@ -184,11 +184,13 @@ const state = myToggle.init(); // reads cookie, binds checkbox
 
 Parallel checkboxes in **both** the User Settings panel and the Pad Wide Settings panel — matching how native settings (sticky chat, line numbers, etc.) work. The pad-wide value rides Etherpad's existing `padoptions` broadcast/persist rail, so changes propagate to every connected client and are remembered across reloads. The pad creator can `enforceSettings` to lock the user-side checkbox for everyone.
 
-Requires Etherpad with the `ep_*` padOptions passthrough patch ([PR #7698](https://github.com/ether/etherpad/pull/7698), shipped in `>= 3.0.0`) AND the runtime flag `settings.enablePluginPadOptions` not set to `false` (default `true` on current cores; earlier 3.x releases shipped it default `false` so operators on those versions need to flip it explicitly). When pad-wide is unavailable the column is hidden automatically and the user-side cookie toggle keeps working — plugins built on this helper run everywhere. The console warning logged on degradation names the specific cause so an admin can tell whether to upgrade the core or to flip the runtime flag.
+Requires Etherpad with the `ep_*` padOptions passthrough patch ([PR #7698](https://github.com/ether/etherpad/pull/7698), shipped in `>= 3.0.0`) AND `settings.enablePluginPadOptions === true`. Current cores default the flag to `true` (see ether/etherpad#7841); earlier 3.x releases shipped it default `false` so operators on those versions need the explicit opt-in below. When pad-wide is unavailable the column is hidden automatically and the user-side cookie toggle keeps working — plugins built on this helper run everywhere. The console warning logged on degradation names the specific cause so an admin can tell whether to upgrade the core or to flip the runtime flag.
 
 ```json
-// settings.json — only needed on older 3.x cores that shipped this opt-in,
-// or to explicitly disable the passthrough on current cores.
+// settings.json — explicit opt-in for older 3.x cores that shipped this
+// flag default-false. Omit on current cores (it's already the default).
+// To explicitly disable the passthrough on a current core, set it to
+// `false` here instead.
 {
   "enablePluginPadOptions": true
 }

pad-select-server.js

@@ -114,9 +114,10 @@ const padSelectServer = (rawConfig) => {
               padWideSupported: isPadWideActive(),
               // Granular flags so the client's degradation warning can
               // name the specific cause — missing patch (Etherpad <
-              // 3.0.0) vs. explicit operator opt-out
-              // (settings.enablePluginPadOptions = false). See
-              // pad-toggle-server.js for the same rationale.
+              // 3.0.0) vs. runtime flag not enabled
+              // (settings.enablePluginPadOptions !== true; either absent
+              // on older 3.x cores or explicitly false on current ones).
+              // See pad-toggle-server.js for the same rationale.
               patchPresent: padOptionsPluginPassthrough,
               runtimeEnabled: runtimeFlagEnabled,
               options,

pad-toggle-server.js

@@ -65,11 +65,11 @@ const padToggleServer = (rawConfig) => {
   const {pluginName, settingId, l10nId, defaultLabel, defaultEnabled} = validateConfig(rawConfig);
   let cachedDefaultEnabled = defaultEnabled;
   // Etherpad >= 3.0.0 introduced settings.enablePluginPadOptions as a runtime
-  // gate on the ep_* passthrough (default true since the flag-flip; older 3.x
+  // gate on the ep_* passthrough (default true on current cores; older 3.x
   // releases shipped with it default false). We grab it from loadSettings so
-  // eejsBlock_padSettings + clientVars correctly no-op when an admin has
-  // opted out, even though PluginCapabilities reports the patch is present
-  // in the core.
+  // eejsBlock_padSettings + clientVars correctly no-op when the flag isn't
+  // enabled (absent on pre-flip cores, or explicitly false), even though
+  // PluginCapabilities reports the patch is present in the core.
   let runtimeFlagEnabled = false;
 
   const isPadWideActive = () => padOptionsPluginPassthrough && runtimeFlagEnabled;