Record why the popup gate fails on a drifted gatelock

The RecoveryLoop call in HostileLock matches gatelock 0.4.0, which is what
requirements.txt pins and what the pylint hook installs. gatelock 0.5.0
regroups the five arguments into a RecoveryCollaborators object, so running
this gate against a locally-installed 0.5.0 fails with

    RecoveryLoop.__init__() takes 3 positional arguments but 6 were given

That is environment drift, not a defect in the check -- against the pinned
version the gate runs and passes both halves. Comment says so, and says how to
resync, so the next reader does not "fix" the code to match whatever happens to
be installed. (I nearly did; against the pin that edit would have broken CI.)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y

scripts/_popup_form_check.py

@@ -43,6 +43,13 @@ class HostileLock:
         # A RecoveryLoop built only to borrow gatelock's real grab predicate;
         # this harness drives the ticks itself, so the collaborators are never
         # called -- the same MagicMock stand-ins gatelock's own tests use.
+        #
+        # This is the gatelock 0.4.0 signature, which is what requirements.txt
+        # pins. gatelock 0.5.0 regroups these into a RecoveryCollaborators
+        # object, so running against a locally-installed 0.5.0 raises
+        # "takes 3 positional arguments but 6 were given" -- that is an
+        # environment drift, not a bug here. Fix it by matching the pin:
+        #   pip install -e . && pip install -r requirements.txt
         self._loop = RecoveryLoop(
             root, LockConfig(mode="hard"), MagicMock(), MagicMock(), MagicMock()
         )