Document agent_id resolution when version is omitted #111

Source

Discovered during E2E validation of #78.

Problem

docs/how-it-works.md documents the Foundry endpoint format as agent_id: my-agent:3 (name:version). In testing, a bare agent_id: FoundryAgent (no :version) was silently accepted and the cloud evaluation succeeded.

Questions to resolve in docs

• Does omitting the version default to "latest"? "deployed"? something else?
• Is reproducibility affected by omitting version (next run could pick up a different agent revision)?
• Should the runner log the resolved version on startup so logs and results.json are reproducible without re-checking the Foundry portal?

Likely fix

• Update docs (docs/how-it-works.md, docs/tutorial-basic-foundry-agent.md) to spell out behavior.
• Optionally: have the Foundry backend log the resolved agent name + version after the first API round-trip.

Severity

Low (docs / observability)