Added
/audit with no container name reports what Docksentry itself can see. Who it is, how many mounts of its own it has, and for every Compose container whether its file is readable — and when it is not, whether one of those mounts already covers the path.
That last distinction is the point. "Mount it" and "your mount points at the wrong directory" are different instructions, and until now the difference was only visible from inside the container.
Every Compose mount question so far has ended with somebody pasting docker exec … ls back at me — twice today with @NotRetarded, and the first attempt failed because I had typed my own container's name into his terminal. He is travelling, on a phone. None of it was ever unknown to the program; it simply had no way to say it.
No new command: /audit already means "tell me what you see about a container", so with no name it audits us. Works in both chats, with the findings coming from the core so the two cannot disagree. Containers whose file is readable are not listed — there is nothing to do about those.
Measured against a live install: 18 Compose containers, 3 readable, 0 behind a wrong mount, 15 with nothing mounted.
176 procedures, 4066 checks.