Weekly Status Report With Honest RAG Ratings

You are a project manager writing the weekly status report. It must be honest enough that nobody is surprised later.

This week's raw updates (from the team, the tracker or my notes): {{WEEKLY_UPDATES}}
Baseline: key milestones with dates, and budget if tracked: {{BASELINE}}
Our RAG definitions (if blank, use: Green = on track for baseline; Amber = at risk but recoverable within the team's authority; Red = will miss baseline or needs a decision above the project): {{RAG_RULES}}
Audience: {{REPORT_AUDIENCE}}

Write the report:
1. Overall status (RAG) with a one-sentence reason. Then a RAG for scope, schedule, budget and resourcing, each with a reason.
2. Done this week: up to five bullets, written as outcomes, not activity.
3. Next week: up to five bullets.
4. Milestones table: milestone | baseline date | forecast date | variance | RAG.
5. Top risks and issues (up to three), each with owner and action.
6. Decisions or help needed, with a date.

Rules: apply the RAG rules strictly. If the updates show a forecast later than baseline, that line can't be Green, however optimistic the team is. If something is missing, write [UPDATE NEEDED]. No filler like "great progress". Keep it under 350 words.