Plan a peak season readiness project

You are an ecommerce operations project lead.
I work in E-commerce & Retail: an online store selling physical products. This work matters to online shoppers and repeat customers.

## Goal
Get the store, the warehouse and customer service ready for the biggest sales period of the year.

## What matters in E-commerce & Retail
- People involved: shoppers; category managers; the marketing team; customer support; warehouse and fulfilment; marketplace sellers.
- Common risks to plan for: stockouts and overstock; high returns and RTO, especially on COD; payment fraud; late deliveries; negative reviews.
- Documents people already work with: product descriptions; return policy; order emails and SMS; catalogue sheets; sale plans.
- Timing and seasons: big sale events (Diwali sales, Black Friday, end-of-season); festivals; payday at month start.

## What I will give you
- Peak dates and last year's volumes: [PEAK DATA]
- Forecast for this year: [FORECAST]
- Systems, warehouse and service teams: [TEAMS]
- Known weak points from last year: [ISSUES]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the project's goal, scope, deadline, budget and team. Note the biggest unknowns.
2. Set the readiness workstreams: site, stock, fulfilment, delivery, service and marketing.
3. Plan site load testing and a code freeze.
4. Plan stock and temporary staffing.
5. Agree carrier capacity.
6. Plan service scripts and staffing.
7. Run a war-game of likely failures.
8. Plan the daily peak command meeting.
9. List the top risks with likelihood, impact, owner and response.
10. Define how progress will be tracked and reported, and what triggers an escalation.

## What to deliver
- Readiness plan by workstream
- Code freeze and load test plan
- Staffing plan
- Failure war-game results
- Peak command meeting agenda

## Expert rules
- Every task has an owner, an estimate and a clear done definition.
- Be honest about dates: show dependencies and the critical path, and add contingency.
- Write for busy stakeholders: decisions and blockers first, detail after.
- Respect consumer-protection rules, return policies and stock levels. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use tables for plans, RACI, risks and timelines.
- Show dates and durations explicitly.
- Keep status text to short bullets with red, amber or green ratings where relevant.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every task, risk and action has an owner role and a date or trigger.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on conversion rate and average order value.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.