[yawboakye]

Summary

• add a Has experience option to developer skill search
• build the complete directory relation in Developers::DirectorySearch
• add a covering (skill_id, profile_id) index for the skill-to-profile lookup

Behavior

• the existing skill filter still includes every developer who lists that skill
• Has experience narrows results to developers who linked the selected skill to an experience entry
• without a selected skill, Has experience finds developers with any experience-backed skill

Query structure

Developers::DirectorySearch owns the text, skill, experience, country, availability, and remote filters and returns a composable Active Record relation. The controller only resolves the selected skill and supplies normalized filter inputs.

Skill matching remains a selective IN subquery, separate from the free-text search join. SQLite's query plan uses covering indexes for both developers_profile_skills and developers_experience_skills, avoiding profile-skill table lookups.

Testing

• test/services/developers/directory_search_test.rb
• test/integration/public_site_test.rb
• test/models/developers/profile_test.rb
• 25 runs, 191 assertions, 0 failures, 0 errors
• StandardRB passes for the changed Ruby files

Local Rails test startup requires the existing Vips.block workaround because libvips is unavailable on this machine; only that initialization hook was stubbed for the focused test run.