race-weeklisted

<Purpose> race-week is the parallel race-week consult. When the runner's race is within 7 days, three specialists consult in parallel — pace-strategist, fuel-advisor, and physio-advisor — and their outputs are synthesized into a single, self-contained race-day brief the runner can print, screenshot, or read on race morning. No multi-tab research required; one brief covers everything. </Purpose> <Use_When> - The race is within 7 days ("다음 주가 대회야", "race is next week", "race week", "대회 D-7", "taper", "race on Sunday") - Keyword triggers detected: "race week", "대회 D-7", "taper", "race day", "race is [day]" - The runner explicitly requests a race-day brief or pre-race guidance - goal.json `race_date` is within 7 days of today </Use_When> <Steps> ## Step 1 — Load Context Before firing the parallel consult, load: - `$OMPB_HOME/goal.json` — event, target_time, race_date, weeks_remaining - `$OMPB_HOME/runner-profile.json` — current_pb, weight_kg, experience, injury_history - `$OMPB_HOME/plan-state.json` — current phase (should be taper), plan_week, this_week_target_km, critic_approved - Recent `$OMPB_HOME/training-log.jsonl` — last 21 days to assess taper compliance and detect any late-appearing pain signals Pass `$ARGUMENTS` (if provided) as additional race context — course profile, expected weather, start time, aid-station spacing — to all three parallel agents. > Safety gate: if the training log shows any unresolved RED verdict from physio-advisor, or any > pain signal