Google Workspace Security Audit v1.7.2: incomplete scans held for review

A --run-dir holding another customer's run is refused at preflight. Before, a resume against a different tenant skipped the completed modules and reported the saved data under the current tenant's name.

A Shared Drive scan that left drives unscanned is now partial: the report is held for review, the run exits 2, and those drives are no longer listed as checked and clean. Run with --grant-temp-access to cover drives the admin is not a member of.

A check that fails to run now holds the report and exits 2, instead of leaving only an INFO finding.

With --grant-temp-access, a temporary organizer grant that could not be removed now holds the report and exits 2. The QA report names the drive and the admin to remove.

Also in this release (v1.7.1, not released separately): the report no longer needs JavaScript to open, so a viewer that blocks scripts shows it instead of a blank page; the header and footer credit the tool and link to the repository; the update check reads the GoogleWorkspaceScripts repository.

Tested on dev on Linux: a partial Shared Drive scan held for review, and a resume against a run directory carrying another customer ID refused. 294 tests pass on Linux (Python 3.14), macOS (Python 3.9 and 3.14) and Windows (Python 3.14).