Should `cwd` be set when using multiple docker compose files?

Hey folks! I'm trying to run service x together with a cluster of services y. The "gateway" of services y provides a docker-compose file for all of its dependencies, as does service x. I thought I would add a Tiltfile from service x like so:

docker_compose(["./docker-compose.yml", "../service-y-gateway/docker-compose.yml"])

This mostly works, except for 1 thing. service-y-gateway's docker-compose file runs "itself" using context: ., which seems to resolve to service-x instead of service-y-gateway. I'm guessing because we run tilt up from service-x. The result, however, is that service-x is running labeled as service-y-gateway.

I had (not sure whether naively or not) expected the cwd for executing each docker-compose file to be set to that file's containing folder. Is that a fair expectation? What I'd like to prevent is having to adjust the docker-compose file for this sort of cross-service use, since it should also stay usable isolated from other docker-compose files... Would love to to hear whether I'm using tilt correctly, and if this is a use-case that can be accommodated or not.

Reproduce the setup from service-x using ./docker-compose.yml and ../service-y-gateway/docker-compose.yml in the Tiltfile. Check how each compose file resolves context when run together versus in isolation. Done means service-y-gateway's context uses its own containing folder without requiring changes that break standalone use.