feat(energy): visible identity and inline task specs in notebook 03

guides/03-customize-agent-strategy.md

@@ -12,7 +12,7 @@ The [architecture atlas §05](https://vectorinstitute.github.io/agentic-forecast
 
 One object defines what an agent *is*: [`AgentConfig`](../aieng-forecasting/aieng/forecasting/methods/agentic/agent_factory.py) — name, model, system instruction, capabilities (search / code execution / function tools), and skill directories. Two more objects define its *role in an experiment*: a **prompt builder** (serializes the task + cutoff-scoped data into the user payload) and an **output schema** (the structured forecast it must return). [`AgentPredictor`](../aieng-forecasting/aieng/forecasting/methods/agentic/predictor.py) marries the two, and its `predict(task, context)` slots straight into the guide-2 harness.
 
-That split is deliberate and worth internalizing: **the same identity can play several roles** (energy's notebook 03 runs one agent config against trajectory, binary-shock, and scenario tasks), and **the same role can be played by different identities** (which is how you A/B two strategies fairly).
+That split is deliberate and worth internalizing: **the same identity can play several roles** (energy's notebook 03 is the worked example: one visible `analyst_config`, then three editable user-payload **task specs** for trajectory, binary-shock, and scenario), and **the same role can be played by different identities** (which is how you A/B two strategies fairly).
 
 Your edit surface is the **starter agent** — `starter_agent/` plus `99_starter_agent.ipynb` — a small, hackable template built for exactly this, and every implementation (#1 sp500, #2 food price, #3 energy, #4 BoC rate decisions) ships its own copy. This guide's file links point at energy's; open the pair for the track you actually picked. The **analyst agent** ([`analyst_agent/agent.py`](../implementations/energy_oil_forecasting/analyst_agent/agent.py)) is the finished four-level example to study: `basic` (no tools) → `news` (search) → `code_exec` (search + sandbox + skills) → `tool` (search + a fixed AutoARIMA function tool).