patchwork: fix type mismatch in patch filtering for project ID

Fix a critical bug in patch filtering where project ID comparison was
failing due to type mismatch. The configuration file specifies project
IDs as strings (e.g., "423"), but the Patchwork API returns them as
integers (e.g., 423). This caused the comparison in _is_patch_matching()
to fail, resulting in no patches being detected as matching.

This bug was preventing KPD from detecting candidate patches in lei-based
patchwork instances, including the Linux firmware loader project.

The fix converts the expected_value to int before comparison for properties
in PATCH_FILTERING_PROPERTIES (project, delegate).

Tested with the firmware loader project - now successfully detects patches
including "firmware_loader: prevent integer overflow in firmware_loading_timeout()".

Since lei-based patchwork instances now work, updates docs to declare it
as supported.

Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <[email protected]>

Author: mcgrof

CLAUDE.md

@@ -87,6 +87,7 @@ docker pull ghcr.io/kernel-patches/kernel-patches-daemon:latest
 - Authentication: GitHub Apps preferred over personal tokens
 - Mirror setup: Uses `mirror_dir` with fallback repositories for bandwidth optimization
 - Lookback period: Recommended 14-21 days for kernel projects (default 7 may be too short)
+- Lei-based patchwork support: Works with kernel.org's new subsystem-specific instances
 
 ### Testing Structure
 

CONFIG.md

@@ -142,6 +142,22 @@ KPD validates configuration on startup and will report specific errors for:
 - Check lookback period is appropriate (7 days may be too short for kernel projects)
 - Confirm search patterns match the patches you expect to process
 - Use `--dry-run-list-candidates-only` to debug patch detection
+- Verify project IDs in search_patterns are correct strings
+- For lei-based patchwork instances, ensure proper API endpoint access
+
+## Lei-based Patchwork Instances
+
+KPD supports the new lei-based patchwork instances deployed by kernel.org for specific subsystems. These instances:
+- Use pseudo email addresses like `[email protected]`
+- May have different API response characteristics
+- Are designed to limit patch scope to specific subsystems
+- Work with the same KPD configuration format
+
+When configuring for lei-based instances:
+1. Use the standard patchwork.kernel.org server
+2. Specify the correct project ID for your subsystem
+3. Consider longer lookback periods (14-21 days) as patches may have extended review cycles
+4. Test with dry-run mode to verify patch detection
 
 ## Example Configuration
 

kernel_patches_daemon/patchwork.py

@@ -380,7 +380,7 @@ def _is_patch_matching(self, patch: Dict[str, Any]) -> bool:
                         # these values can be None so we need to filter them out first
                         if not patch[prop_name]:
                             return False
-                        if patch[prop_name]["id"] != expected_value:
+                        if patch[prop_name]["id"] != int(expected_value):
                             return False
                     except KeyError:
                         return False