Map string settings to appropriate types

[hsimah]

FacetWP sends through 'yes' and 'no' for some settings. These really should be boolean values on the consumer end. Check other settings for similar issues.

[justlevine]

🤖 Automated Triage

Classification: type: enhancement ⚡ · priority: low · scope: documentation 📚 (preserved: type, status)
Agent-feasible: Yes — bounded scope. The task is to audit the settings mapping logic, find where 'yes'/'no' string values are passed through from FacetWP, and convert them to boolean on the GraphQL side. Clear pattern: map known string settings to their typed equivalents.
Estimated effort: Agent low · Human low

Summary: FacetWP sends 'yes'/'no' strings for boolean-ish settings. These should be mapped to proper GraphQL Boolean types in the schema registration. A systematic audit of all settings types and their FacetWP source values would catch similar issues.

Next steps: Ready for planning loop. Candidate for good first issue 🐣 — the pattern is straightforward: grep settings registration, add type casting, test.