Fix
- File catalog stopped importing after a container update, so archives could not be browsed or restored file-by-file (#506). The catalog is written into each client's
.catalog-logsdirectory and read by the web user. That access depends on the SSH user being in thewww-datagroup and the directory being group-owned bywww-data. A container recreate that reassignedwww-data's GID, or rebuilt an SSH user without the group, broke both: the web user could no longer reach the directory, so the server reported "no catalog file arrived" even though the backup and the file were fine. The container now restores the group membership and the directory ownership on every start, and the streaming channel heals the directory itself on the next backup, so no manual step is needed. Existing archives that missed their catalog can be rebuilt from the repository's Rebuild Catalog action.
No agent change; agent stays 2.96.6.