searches.yaml example uses 'boards' field, but code only recognizes 'sites', causing config to be ignored

[bincat233]

Summary

When configuring searches.yaml, the example file and the wizard-generated config use the boards: field. However, the actual discovery logic (jobspy, etc.) only recognizes the sites: field. As a result, users who follow the example and configure boards: are unable to control the search platforms (e.g., cannot disable zip_recruiter).

Steps to Reproduce

1. Reference config/searches.example.yaml and configure the boards: field (e.g., only include indeed/linkedin)
2. Run applypilot run discover (or other discovery commands)

Expected Behavior

• User configuration of boards: should take effect, or at least trigger an error/warning.
• The example, wizard, and core code should use a consistent field name.

Actual Behavior

• The boards: field is ignored; discovery logic only recognizes sites:.
• If sites: is not set, zip_recruiter (and others) are forcibly included.
• New users following the example find their config ineffective, with no clear explanation unless they read the source code.

Suggestions

• Unify the field name across the example, wizard, and main code (preferably sites:).
• Alternatively, make code compatible with boards: (e.g., sites = cfg.get("sites") or cfg.get("boards"))
• Ensure documentation, code, and wizard all describe fields consistently.

---

Version: 4a8d521
Command: applypilot run discover