Description
While working with multiple dotenv files one might get confused what the current value is and how different files override each other. Besides the already existing debug:container --env-vars I would propose to add an additional debug:dotenv command that focuses only on the files and isn't tied to the container

Example

WDYT?