style: the 98 ruff could not fix, so the linter is a signal again

The pass before this applied ruff's own fixes. These are the ones needing a
decision, and the point of doing them is that `ruff check .` now passes: a
linter reporting 98 known-acceptable findings reports nothing, because the next
real one arrives invisible.

**Lines over 100 (70).** Mostly wrapped where they stood. Two exceptions: the
aligned trailing comments in `protocol.py`'s message table were shortened rather
than wrapped, because wrapping one row of a table breaks the table; and in
`models.py` the column comments moved above their columns for the same reason.

**Imports below the first statement (14).** `csam.py` kept its FastAPI imports
under a section header halfway down the file; two node tests had a constant and
a `pytestmark` wedged between two import blocks. Moved, not suppressed.

**Bindings nothing reads (4).** Three in tests, where the call stays and only the
name goes — `_user(client, "listener")` is there to create the user, not to
return one. The fourth was in `revocation.py` and was not a lint finding at all:
`_connect_and_listen` opened an httpx stream to the WebSocket URL, did `pass`,
and then opened the real connection through the `websockets` library. One
pointless request per connect, left over from before that library was used
directly. Removed, and `httpx` with it.

**`l` as a name (4)**, **semicolons (6)** in the POC spikes, and the rest.

2893 passed, the same count as the two commits before it.

`meshbay_node/revocation.py` is worth a decision separately: 154 lines that
nothing imports, superseded by `hub_client.maintain_ws`'s `on_revocation`. This
commit only stopped it failing the linter.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/packages/meshbay-hub/tests/test_memory_ceiling.py b/packages/meshbay-hub/tests/test_memory_ceiling.py
index 1654825..5984292 100644
--- a/packages/meshbay-hub/tests/test_memory_ceiling.py
+++ b/packages/meshbay-hub/tests/test_memory_ceiling.py
@@ -246,11 +246,11 @@ def test_no_unguarded_memory_floor(target_fn):
     # definition out before looking. Comments go too — the branch that used to
     # be the bug is now described in one, and a test that reads prose is the
     # mistake already recorded in CLAUDE.md for the packaged systemd unit.
-    start = next(n for n, l in enumerate(lines) if "const _memoryFloor" in l)
+    start = next(n for n, ln in enumerate(lines) if "const _memoryFloor" in ln)
     end = next(n for n in range(start, len(lines)) if lines[n].strip() == "};")
     rest = lines[:start] + lines[end + 1:]
-    code = [re.sub(r"//.*$", "", l) for l in rest]
-    bare = [l.strip() for l in code if re.search(r"\breturn null\b", l)]
+    code = [re.sub(r"//.*$", "", ln) for ln in rest]
+    bare = [ln.strip() for ln in code if re.search(r"\breturn null\b", ln)]
     assert bare == [], (
         "an unguarded in-memory fallback was added to _openDownloadTarget; "
         "return _memoryFloor() instead: " + "; ".join(bare))