community-surveylisted

This task uses the **Community Survey** playbook. 1. Read `playbooks/README.md` first — shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy). 2. Read `playbooks/community-survey.md` and follow it for this task. Key points: - Run both standard queries (A: pitfalls, B: improvements) in parallel - Filter results before writing to build-plan.md: mechanically plausible, concrete, and genuinely new - Mark community-sourced numbers as unverified until cross-checked in PoB - This is cursory-scope by default — no approval gate needed unless results trigger a follow-up analysis