You are an expert technical writer and curriculum designer. I want you to iteratively review and improve the following text for a technical lab/tutorial.

Please review the text against these core criteria:

1. Alignment with Recent Lab Updates & Architecture: Verify that the section is accurately synchronized with the latest codebase, architectural mechanics, and UI features:
   - Standardized Navigation & UI Terminology: References to `Campaign Studio` (or `Campaigns`), `Auction Simulator`, and `Bidding Policy` (direct telemetry queries to BigQuery Studio in the Google Cloud Console).
   - First-Price Auction Mechanics: Accurately explaining that winners pay exact submitted bids and that the optimal bid is competitor P90 + $0.05 safety buffer.
   - 5-Cycle Synchronized Simulation: 500,000-auction flights structured into five 100,000-auction cycles (10 ticks each), halting at cycle checkpoints to audit BigQuery telemetry and reason before applying updated bids on flight resumption.
   - Two Flaws of Deterministic Rules: Contrasting the AI agent against the heuristic rule's Surge Lag Trap (crawling too slowly at $9.60 CPM) and Dropout Overpayment Trap (bidding $8.00+ on collapsed $0.85 CPM traffic).
   - ADK 2.0 & Gemini Tooling: Proper usage of structured tools (`get_campaign_config`, `query_telemetry`, `get_bidding_history`, `update_bid_cpm`).
   - Reflective Bid Shading: Auditing multi-window BigQuery telemetry to detect competitor exit and shade bids down.
   - Formatting & Code Standards: Enforcing a strict 88-character maximum line length for code blocks and commands.
2. Interest & Narrative: There must be a compelling story that pulls the reader in. Put the reader directly in the shoes of an operator facing a plausibly real-world business problem with real stakes. The tone should be engaging, professional, and slightly dramatic to make the problem feel urgent, while still teaching practical solutions.
3. Flow & Structure: The narrative must flow seamlessly. Ensure there are strong, logical transitions moving from (A) Setting up the business problem, to (B) Explaining the technical background/mechanics, to (C) Introducing the proposed solution.
4. Clarity & Conciseness: The narrative should enhance the technical concepts, not distract from them. Ensure the text is punchy. Remove unnecessary fluff and avoid using complex jargon without immediately defining it in plain English.
5. Actionability & Orientation: The text must clearly distinguish between theoretical background ("how it works in theory") and the project deliverables ("what you will build"). Ensure the reader is always perfectly oriented to their goals.
6. Formatting for Scannability: Use Markdown effectively to make the text highly scannable. Use bold text to highlight key terms, short paragraphs, bulleted lists for multiple items, and headers to break up distinct concepts.
7. Empathetic Tone: The tone should be encouraging. When introducing a complex technical concept, subtly acknowledge the complexity while assuring the reader that the upcoming steps will break it down into manageable pieces.
8. Visual Aids (Image Placeholders): Identify moments in the text where a diagram, flowchart, or screenshot would significantly improve understanding. Do NOT attempt to generate or render the images. Instead, insert a descriptive placeholder exactly where the image should go, using this format: `[IMAGE RECOMMENDATION: A detailed description of what the visual should show, e.g., 'A flowchart showing the agent querying BigQuery and updating the ad server API']`.

Your task is to execute the following iterative process:
1. Review: Read the text and evaluate it against all the criteria above, specifically auditing for any outdated terminology, legacy mechanics, or discrepancies with recent lab updates.
2. Recommend: Outline specific changes needed to improve the text based on the criteria. Also, explicitly list the visual aids and architectural alignments you plan to recommend.
3. Implement: Rewrite the section entirely, applying your recommendations, aligning with recent lab updates, and inserting the `[IMAGE RECOMMENDATION: ...]` placeholders where appropriate.
4. Refine: Review your own rewrite. If the transitions feel bumpy, the narrative isn't gripping, the image placeholders aren't clear, or any legacy discrepancies remain, refine it again until it perfectly meets the criteria.

Here is the text to improve:

[INSERT YOUR TEXT HERE]