Drop an internal-tracking reference from a connection comment

An isolation_level setter comment referenced an internal development
episode ("the same widening round"); reword it to keep the technical
point (it mirrors the autocommit setter's value-storage discipline)
without the internal reference. Extend the source-scan guard test to
also catch development-episode "round" phrasing, which the prior
digit-anchored pattern missed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: antoineleclair

src/dqlitedbapi/connection.py

@@ -3408,7 +3408,7 @@ def isolation_level(self, value: object) -> None:
         # so the getter round-trips — without storage, the canonical
         # cross-driver idiom assigns the value silently and the next
         # read returns the default. Mirrors the ``autocommit.setter``
-        # storage discipline established in the same widening round.
+        # storage discipline.
         #
         # **Inner-AsyncConnection slot is INDEPENDENT.** The setter
         # stores on the sync wrapper only; ``self._async_conn

tests/test_no_workflow_references_in_source.py

@@ -23,6 +23,11 @@
     re.compile(r"ISSUE-\d+"),
     re.compile(r"\b[Cc]ycle \d+"),
     re.compile(r"\bround \d+"),
+    # "round" used in the development-episode sense (a "widening round",
+    # the "prior round"). Anchored to dev-process qualifiers so the
+    # legitimate algorithmic/technical uses ("import cycle", "settle
+    # round", "round-trip", "a round of retries") are NOT flagged.
+    re.compile(r"\b(?:prior|previous|earlier|widening|hardening|audit) round\b"),
     re.compile(r"\b[Bb]undle [A-Z]\b"),
     re.compile(r"\bPhase \d+\b"),
 )