data: replace personal_health_diet demo prompt with four_day_workweek

Swap the diet-overhaul question for a business-focused 4-day work week
question (220-person professional-services firm, COO POV) so the
default demo bank is consistently business / management / civic
scenarios instead of mixing personal-health cases.

Co-authored-by: Cursor <cursoragent@cursor.com>

backend/app/data/demo_questions.json

@@ -50,10 +50,10 @@
       "text": "I'm CTO of a 12-person AI startup that's about to release our first real product: a domain-specific reasoning agent for legal-contract review. We've raised a Series A. The founding team is split on whether to release our core inference stack as open source under a permissive license. The arguments for: faster developer adoption, recruiting, brand-building, the ecosystem moves fast and we'll be left behind otherwise. The arguments against: a well-funded competitor could fork us, our investors are nervous, and our actual moat is the domain training data, not the inference code. I'd like to land on a defensible decision in the next six weeks. What framework should we use, and what's the right answer for a company in roughly our position?"
     },
     {
-      "id": "personal_health_diet",
-      "category": "health",
-      "title": "Diet overhaul with conflicting advice",
-      "text": "I'm 41, somewhat overweight, with borderline-high blood pressure and slightly elevated LDL cholesterol. My doctor wants me to lose roughly 30 pounds and lower my blood pressure without yet starting medication. I have done short stints with several diets over the years - low carb, intermittent fasting, Mediterranean, and a vegan stretch - and lost weight on each before regaining it. I have a desk job, two school-age kids, and I cook most of our meals. I'm not interested in supplements with weak evidence, but I am willing to commit to a structured plan if it's actually likely to work for someone like me long-term. What should the plan look like, and what trade-offs am I implicitly making by picking one?"
+      "id": "four_day_workweek",
+      "category": "workplace / management",
+      "title": "Whether a 220-person firm should adopt a permanent 4-day work week",
+      "text": "I'm the COO of a 220-person professional-services firm in the Midwest US (architecture and engineering consulting). Two of our regional competitors have piloted 4-day work weeks for the past year and are leaning on it heavily in their recruiting; we've lost three good candidates to them in the last six months. Our partners are split on whether to follow. The case for: better retention, a stronger applicant pipeline, well-publicized productivity gains in some studies, and our work is mostly project-based so client deliverables don't strictly need a Friday. The case against: about 30% of our work involves real-time coordination with construction crews and government agencies that operate Mon-Fri; some senior partners worry it signals we are unserious; to absorb the cost we'd need to either stretch hours into longer days, cut staffing slightly, or accept lower billable utilization for at least the first year; and we have no clean way to roll it back if it doesn't work. Roughly half our staff are early-career employees with young kids; the other half are senior people who built the firm working 60-hour weeks and have mixed feelings about offering juniors a shorter week. Should we do it, what structure makes sense if we do, and how would we know at the 12-month mark whether it's working?"
     },
     {
       "id": "community_park_grant",