fix: wire the lit orchestrator demo to its required subagents

[stablegenius49]

Description

This wires the Lit orchestrator sample to the ports already documented in the orchestrator README so npm run demo:orchestrator can actually boot the full sample stack.

What changed:

• added orchestrator-specific subagent scripts for the restaurant, contact lookup, and rizzcharts agents
• updated serve:agent:orchestrator to pass the default --subagent_urls values the orchestrator requires
• updated demo:orchestrator to launch the shell plus all three subagents before starting the orchestrator

Fixes #586.

Pre-launch Checklist

• I signed the CLA.
• I read the Contributors Guide.
• I read the Style Guide.
• I have added updates to the CHANGELOG.
• I updated/added relevant documentation.
• My code changes (if any) have tests.

Tests:

• added a local Node assertion that validates the updated package.json scripts wire the documented ports and subagent URLs.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request successfully wires up the Lit orchestrator demo by adding and updating the necessary npm scripts in package.json. The changes appear to be functionally correct. My review includes two suggestions to improve the maintainability and robustness of these new scripts by reducing a very long command and eliminating duplicated port numbers.

[gemini-code-assist]

The ports for the subagents (10003, 10004, 10005) are hardcoded in this script and also in the serve:agent:*:orchestrator scripts on lines 13-15. This duplication means that if a port number changes, it must be updated in two places, which is error-prone and violates the DRY principle. Consider using a mechanism to define these ports only once. For example, you could use a tool like cross-env to set environment variables for the ports and reference them in the scripts, making them more robust and easier to maintain.

[gemini-code-assist]

This script definition is very long, which harms readability and maintainability. To make it cleaner, you could extract the logic for running the subagents into a separate helper script.

For example, you could add a serve:subagents:orchestrator script:

"serve:subagents:orchestrator": "concurrently -k -n \"REST,CONT,RIZZ\" -c \"blue,green,yellow\" \"npm run serve:agent:restaurant:orchestrator\" \"npm run serve:agent:contact_lookup:orchestrator\" \"npm run serve:agent:rizzcharts:orchestrator\""

Then, the demo:orchestrator script would be much simpler:

"demo:orchestrator": "npm install && npm run build:renderer && concurrently -k -n \"SHELL,AGENTS,ORCH\" -c \"magenta,white,cyan\" \"npm run serve:shell\" \"npm run serve:subagents:orchestrator\" \"npm run serve:agent:orchestrator\""