feat: add baseSystemPrompt fixed

prompts/daily_schedule.md

@@ -24,7 +24,7 @@ Emit a JSON array (and only the JSON array—no prose, no markdown) of exactly 4
 
 - **`start`:** A 24-hour clock string in `HH:MM` form, zero-padded (e.g., `"00:00"`, `"03:40"`, `"23:30"`).
 - **`end`:** A 24-hour clock string in `HH:MM` form, zero-padded. The last slot of the day must end at `"24:00"`, not `"00:00"` of the next day. All other end times must equal the start of the next slot.
-- **`activity`:** A short, specific, embodied label (e.g., `"deep sleep"`, `"commute on the 6:14 train"`, `"standup meeting"`, `"lunch (leftover dhal)"`, `"afternoon writing block"`, `"a walk around the block"`, `"evening wind-down"`, `"light reading in bed"`). Not a category—`"rest"` is not an activity. A noun-phrase of what the body is actually doing. A schedule is the plan for the day; personal calls and texts are not scheduled activities—they are background behavior that happens inside other activities (or does not), and must not appear as an `activity` slot.
+- **`activity`:** A short, specific, embodied label (e.g., `"deep sleep"`, `"commute on the 6:14 train"`, `"answering work emails"`, `"lunch (leftover dhal)"`, `"afternoon writing block"`, `"a walk around the block"`, `"evening wind-down"`, `"light reading in bed"`). Not a category—`"rest"` is not an activity. A noun-phrase of what the body is actually doing. A schedule is the plan for the day, not a contact list: personal calls, texts, video calls, and meetings are not scheduled activities. They are either background behavior that happens inside other activities (or does not), or they are real-time voice/video events the persona cannot actually execute—and in either case they must not appear as an `activity` slot.
 - **`notes`** *(optional):* A short, plain-text annotation, only when the activity is non-obvious or when the person is doing two things at once (e.g., `"answering work emails while feeding the cat"`).
 
 **The schedule must:**