Yogesh OjhaandClaude Opus 5 ca918eb356 fix(backup): an archive carried no scan media and could carry no volumes ...

The worker writes scan media as root, so `tar -cf scan_media.tar` run
as the host user failed on every scan directory. The failure went to
/dev/null and the `||` wrote an empty tar instead, and the dump
reported success: every archive taken so far holds no screenshots and
no captured responses. Measured on this instance — 10 KB before, 566
MB and 27,987 entries after. The tar and the restore both run in a
container now, which is also the only way the restore could remove the
old tree.

The volume names were guessed as <directory>_<volume>, which is wrong
whenever the compose project name is not the directory name, and the
guess was wrapped in `|| true`, so that also produced an empty archive
quietly. The project name comes from compose, and a missing volume is
an error.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DafWxfoWZXVDgr9KroJBDZ

2026-09-16 11:33:10 +05:30

..

backup.sh

fix(backup): an archive carried no scan media and could carry no volumes

2026-09-16 11:33:10 +05:30

connector_e2e.py

chore: production-readiness review across the tree

2026-09-13 18:03:29 +05:30

connector_journey.py

feat(connectors): browsing lands in the endpoints inventory

2026-09-12 16:39:23 +05:30

fetch_content_wordlist.py

style: strip explanatory comments across the codebase

2026-09-11 14:11:23 +05:30

fetch_port_registry.py

chore: production-readiness review across the tree

2026-09-13 18:03:29 +05:30

fetch_report_fonts.py

style: strip explanatory comments across the codebase

2026-09-11 14:11:23 +05:30

fetch_subdomain_wordlist.py

style: strip explanatory comments across the codebase

2026-09-11 14:11:23 +05:30