Word the progress queue depths as states and guard -A 7

[zaihuaji]

Summary

• to transfer was wrong. Status 'T' is BSTATS 'Tarred Files' - built, awaiting upload. But -A 3 is CTACTS = 1|2 and neither transfer branch in start_actions fires for it (acts&BCKACT = 0, acts&TBACTS != TBACTS), so an -A 3 report was claiming 1671 units of work that run never performs. Both queue depths are now worded as states: 6 Quasar Backup tar file(s) left to build and 1671 tarred.
• -A 7 could never report progress. CBACTS = 7 was missing from the check_batch_deadline() action list, even though -A 7 (1+2+4) is documented in dsquasar.usg and is the longest-running combination. Added.
• Corrected a code comment that claimed -A 3 runs the transfer phase; only -A 4, -A 6 and -A 7 do.

Test plan

• python3 -m py_compile clean
• guard coverage table: -A 2/3/4/6/7 guarded, -A 1/8/16 not; transfers=True only for -A 4/6/7
• rendered message checked against the real report wording
• walltime-reachability, one-report-per-run and stall-detection harnesses all still pass
• confirm the next -A 3 progress email reads ... left to build and N tarred

Generated with Claude Code