fix(import[gitlab]) Emit qualified warning when client filters reduce count below limit

why: The count < limit early return in _warn_truncation suppressed the
qualified warning whenever filters excluded enough repos to keep count
under the limit, even when total_available exceeded count.
what:
- Skip early return when has_client_filters=True so total_available > count
  can still trigger the qualified warning
- Update _warn_truncation docstring to explain new semantics
- Add test_gitlab_truncation_warning_count_below_limit_with_filters

Author: tony

src/vcspull/_internal/remotes/gitlab.py

@@ -367,11 +367,16 @@ def _warn_truncation(
         x_next_page : str | None
             Value of x-next-page header (None if absent/empty)
         has_client_filters : bool
-            True when any client-side filter (skip_groups, language, topics) is
-            active; used to qualify the warning message so the server-side
-            total is not presented as the filtered total.
+            True when any client-side filter (skip_groups, language, topics,
+            min_stars) is active; suppresses the early ``count < limit`` return
+            so the qualified warning can fire even when count < limit.
         """
-        if count < limit:
+        # Without client-side filters, count < limit means we consumed all
+        # server results without hitting the limit — no truncation to warn about.
+        # With active filters, skip the early return: count < limit may simply
+        # reflect that filters excluded repos, while total_available still
+        # exceeds count and is worth surfacing to the user.
+        if count < limit and not has_client_filters:
             return
 
         if total_available is not None and total_available > count:

tests/_internal/remotes/test_gitlab.py

@@ -888,6 +888,45 @@ def urlopen_side_effect(
     assert "server total includes projects excluded" in caplog.text
 
 
+def test_gitlab_truncation_warning_count_below_limit_with_filters(
+    monkeypatch: pytest.MonkeyPatch,
+    caplog: pytest.LogCaptureFixture,
+) -> None:
+    """Qualified warning fires even when count < limit, if client filters are active.
+
+    Regression test: the count < limit early return in _warn_truncation must
+    not suppress the warning when has_client_filters=True.
+    """
+    import logging
+
+    caplog.set_level(logging.WARNING)
+
+    # _make_group_project has namespace full_path="testgroup";
+    # skip_groups=["testgroup"] filters every repo → count=0 < limit=20
+    repos = [_make_group_project(f"proj-{i}") for i in range(5)]
+    headers = {"x-total": "5"}
+
+    def urlopen_side_effect(
+        request: urllib.request.Request,
+        timeout: int | None = None,
+    ) -> MockHTTPResponse:
+        return MockHTTPResponse(json.dumps(repos).encode(), headers, 200)
+
+    monkeypatch.setattr("urllib.request.urlopen", urlopen_side_effect)
+
+    importer = GitLabImporter()
+    options = ImportOptions(
+        mode=ImportMode.ORG,
+        target="testgroup",
+        limit=20,
+        skip_groups=["testgroup"],  # owner="testgroup", so all 5 repos are excluded
+    )
+    list(importer.fetch_repos(options))
+
+    # count=0 < limit=20, but has_client_filters=True → qualified warning should fire
+    assert "server total includes projects excluded" in caplog.text
+
+
 # ---------------------------------------------------------------------------
 # with_shared URL parameter tests
 # ---------------------------------------------------------------------------