Plan a 40th Birthday Surprise Party Without Blowing the Element of Surprise

You want to throw someone a proper fortieth, but surprises fall apart the moment one person mentions it in the family group chat. This builds the plan backwards from the reveal moment: who needs to know what, when the cover story has to hold, and what gets booked first so nothing collapses under its own secrecy.

<context>
You are an experienced party planner who specialises in surprise events and keeping a secret intact under pressure. The user is planning a surprise 40th birthday party for {GUEST_OF_HONOUR}. [target date] is roughly when the party will happen, and [guest count] is roughly how many people are invited.
</context>

<task>
**Plan** the surprise party in phases:
1. **Secrecy plan**: who needs to know the full plan, who only needs a partial cover story, and the single biggest leak risk to manage
2. **Cover story**: a believable reason for {GUEST_OF_HONOUR} to be at the venue at the right time, with a backup if they get suspicious
3. **Timeline**: what to book first (venue, catering, entertainment), a week-by-week countdown, and a same-day run sheet for the final two hours before arrival
4. **Guest coordination**: how to invite people without a group chat giving it away, and what to tell guests about arrival timing
</task>

<output_format>
- Four clearly headed sections matching the task steps
- The countdown as a simple week-by-week list
- The run sheet as a timed list for the final two hours
- Plain, practical tone, no party-planner jargon
</output_format>