Make agent URLs configurable and update quickstart docs

[zeroasterisk]

This PR addresses onboarding friction by making agent URLs configurable via env vars and updating the quickstart documentation.

[gemini-code-assist]

Code Review

This pull request updates the quickstart documentation to use specific demo commands and introduces environment variable support for configuring agent URLs in the Lit client samples. The review feedback suggests using distinct ports in the documentation examples to avoid confusion and adding optional chaining when accessing environment variables in TypeScript to improve robustness and adhere to style guidelines.

[gemini-code-assist]

The example shows both agents using the same port (8000). Since these are typically separate processes, it is clearer to show them on different ports to avoid potential port conflicts for users trying to run both demos simultaneously.

Suggested change

	export VITE_RESTAURANT_AGENT_URL="http://localhost:8000"
	export VITE_CONTACTS_AGENT_URL="http://localhost:8000"
	export VITE_RESTAURANT_AGENT_URL="http://localhost:8000"
	export VITE_CONTACTS_AGENT_URL="http://localhost:8001"

[gemini-code-assist]

Accessing (import.meta as any).env without optional chaining can cause a runtime error if env is undefined (e.g., in certain test environments or non-Vite builds). Adding optional chaining makes the code more robust. Additionally, while any is used here to bypass missing type definitions for import.meta.env, it is generally discouraged in TypeScript per standard style guides.

Suggested change

	serverUrl: (import.meta as any).env.VITE_CONTACTS_AGENT_URL || "http://localhost:10003",
	serverUrl: (import.meta as any).env?.VITE_CONTACTS_AGENT_URL || "http://localhost:10003",

References

1. The TypeScript style guide generally discourages the use of the any type to maintain type safety and prevent runtime errors. ^(link)

[gemini-code-assist]

Using (import.meta as any).env without optional chaining can cause a runtime error if env is undefined. Adding optional chaining makes the code more resilient. Also, avoiding any is preferred for better type safety.

Suggested change

	serverUrl: (import.meta as any).env.VITE_RESTAURANT_AGENT_URL || "http://localhost:10002",
	serverUrl: (import.meta as any).env?.VITE_RESTAURANT_AGENT_URL || "http://localhost:10002",

References

1. The TypeScript style guide generally discourages the use of the any type to maintain type safety and prevent runtime errors. ^(link)

[ditman]

Small change, please try not to use as any, instead, define the type that you expect for ImportMeta!

[ditman]

The contacts sample is gone from the shell app, this is not needed anymore!

[ditman]

Please, don't do as any here. Maybe define an ImportMeta and ImportMetaEnv types (as described here).

Also, when have you found yourself needing this? I normally start the demos with npm run demo:blah and that has all the batteries included!