[codetalks-hw]

Summary

Documentation follow-ups in the ran-energy-saving README (en/zh).

Quickstart

• Three labelled steps: Step 1 create the repository .venv, Step 2 configure the sample, Step 3 run the sample.
• The step descriptions live in the prose; the command blocks now contain only commands.
• The Windows interpreter path is a separate tip.
• The output sentence now reads: "Both client and server logs stream to the terminal live and interleaved, with background processes automatically terminating when the client exits."

Project layout (§1.1)

• server_main.py: the A2A SDK app assembly includes the push-notification module by default; server-side integration points to the INTEGRATION POINT comment in build_server_runtime.
• scenario_data.py: the "not removable until both sides are replaced" clause is removed.
• task_execution.py: describes the TaskExecutionService execution entry point plus the demo service that simulates progress and generates intent reports.
• run_demo.py: simplified to the non-blocking launcher behavior (the cross-platform claim is dropped).

UC1 wording

The README used the undefined abbreviation UC1; both rows now describe the demo execution and its scripted progress/report data directly. Code comments keep UC1 where the RAN interface specification is already named.

Docs-only; no behavior change.