defaults.distance (radius) is included in searches.yaml and wizard, but never used in discovery/search

[bincat233]

Summary

The ApplyPilot wizard (init step) and searches.example.yaml both prompt the user for a search radius/distance and write defaults.distance into searches.yaml. However, the discovery/search logic (JobSpy, SmartExtract, Workday, etc.) does not read or use this field, so the radius value has no effect.

Steps to Reproduce

1. Run applypilot init and enter a non-zero radius (distance). Confirm ~/.applypilot/searches.yaml contains defaults.distance.
2. Run applypilot run discover (or other discovery commands).
3. Observe that discovery/search behavior does not change based on the radius value (it is not passed into JobSpy params or URL templates).

Expected Behavior

• The user-provided radius/distance should affect discovery/search (e.g., propagate into JobSpy params or site URL templates where supported).
• If radius support is not implemented, the wizard/example should not ask for it (or should warn that it is ignored).

Actual Behavior

• defaults.distance is written to searches.yaml but is silently ignored by discovery/search logic.
• Users may assume radius filtering is applied, but it is not.

Suggestions

• Implement distance/radius propagation into discovery/search (JobSpy args and/or site URL templates).
• Or remove defaults.distance from wizard/example and document that radius is not supported yet.
• Alternatively, warn users during applypilot init / applypilot doctor that the field is currently unused.

---

Version: 4a8d521
Command: applypilot run discover