In an eis-chat multi-agent build, aspire.config.json https profile pins the Aspire dashboard (:18888), OTLP (:4318), and resource-service (:18891) endpoints. aspire start --isolated randomizes resource ports and user secrets but NOT these profile-pinned infra ports, so a second isolated apphost collides with a running base and attaches to it instead of spawning its own. That blocks parallel sub-agents from each running a true isolated LIVE apphost to verify streaming/DB actions (they fall back to SSR-server-only verification, which is how a broken live chat shipped once). Proposal: --isolated should also randomize (or offer a first-class per-instance override for) the dashboard/OTLP/resource-service endpoints, so N isolated apphosts run simultaneously without editing the shared config.
In an eis-chat multi-agent build, aspire.config.json https profile pins the Aspire dashboard (:18888), OTLP (:4318), and resource-service (:18891) endpoints. aspire start --isolated randomizes resource ports and user secrets but NOT these profile-pinned infra ports, so a second isolated apphost collides with a running base and attaches to it instead of spawning its own. That blocks parallel sub-agents from each running a true isolated LIVE apphost to verify streaming/DB actions (they fall back to SSR-server-only verification, which is how a broken live chat shipped once). Proposal: --isolated should also randomize (or offer a first-class per-instance override for) the dashboard/OTLP/resource-service endpoints, so N isolated apphosts run simultaneously without editing the shared config.