lint: make check_no_print path-allowlist Windows-safe

The CLI-print allowlist compared paths via
\`str(rel).startswith(str(p) + \"/\")\`. On Windows this never
matched because \`str(rel)\` uses backslashes, so the CLI
allowlist silently failed and every \`print()\` in
\`geno_lewm/cli/verify.py\` was flagged as a violation, breaking
the gates job + two unit tests on every Windows runner.

Switch to component-tuple comparison (\`rel.parts[:n] == p.parts\`)
so the same allowlist matches on POSIX and Windows.

Confirmed by downloading the pytest artifact from the prior
Windows run; both failures (\`test_print_in_cli_dir_is_allowed\` and
\`test_real_package_passes\`) trace to this single AST-linter
regression. Local Linux suite still passes.

Author: claude

tools/lint/check_no_print.py

@@ -53,7 +53,11 @@ def _is_allowlisted(file: Path) -> bool:
         rel = file.resolve().relative_to(PACKAGE_DIR.resolve())
     except ValueError:
         return False  # outside the canonical package — still scanned (test fixtures use tmp dirs)
-    return any(str(rel).startswith(str(p) + "/") or rel == p for p in _ALLOWED_PRINT_PATHS)
+    # Compare via path components, not str().startswith, so the
+    # allowlist matches the same way on Windows (backslashes) and
+    # POSIX (forward slashes).
+    rel_parts = rel.parts
+    return any(rel_parts[: len(p.parts)] == p.parts or rel == p for p in _ALLOWED_PRINT_PATHS)
 
 
 def check_file(path: Path) -> list[Violation]: