Mark 112534 Google Drive backup verified

dataset_guide/HF_DATASET_CARD.md

@@ -31,7 +31,7 @@ Only validation-passing checkpoints should be uploaded or used for training.
 | Checkpoint | Size | JSONL | In-bundle duplicates | Status |
 | --- | ---: | --- | ---: | --- |
 | `checkpoint_20260611_104104_bundle01_20g` | 19.04 GiB | valid, legacy multi-part | 0 | uploaded to Hugging Face |
-| `checkpoint_20260611_112534_bundle01_20g` | 19.11 GiB | valid, single JSONL | 0 | uploaded to Hugging Face; Google Drive local single-file copy present; Drive cloud sync not claimed |
+| `checkpoint_20260611_112534_bundle01_20g` | 19.11 GiB | valid, single JSONL | 0 | uploaded to Hugging Face; Google Drive cloud verified by rclone SHA256/size check |
 
 ## Repository Layout
 

dataset_guide/TARGET_400GB_POLICY.md

@@ -67,17 +67,18 @@ Never materialize the whole 400GB dataset twice. The safe loop is:
    `dataset/<checkpoint>/dataset/<checkpoint>.jsonl` and deleting each source
    part after it is appended.
 5. Upload that checkpoint to Hugging Face.
-6. Copy or upload that checkpoint to Google Drive and wait for cloud sync.
-7. Delete the local workspace checkpoint after HF is verified and Drive has a
-   local copy; delete any duplicate Drive local part files only after the single
-   JSONL is present and at least one verified remote copy exists.
+6. Upload that checkpoint to Google Drive with a low-RSS path such as rclone and
+   verify remote size plus SHA256.
+7. Delete the local workspace checkpoint after HF and Google Drive remotes are
+   both verified; delete duplicate Drive part files only after the single JSONL
+   is present and at least one verified remote copy exists.
 
 ## Google Drive Verification Rule
 
 Google Drive Desktop local copy is not the same as cloud upload completion.
-Cloud completion is confirmed only when DriveFS metadata no longer shows local
-placeholder IDs for the JSONL files and the Drive app has no pending sync/error
-state for the checkpoint.
+Cloud completion is confirmed by either DriveFS metadata with no pending
+sync/error state or by a direct low-RSS Drive API path such as rclone returning a
+remote listing whose size and SHA256 match the local checkpoint manifest.
 
 Google Drive Desktop is not allowed to exceed the RSS safety budget. If the
 Drive app grows above the upload-process safety threshold, stop it and use a

dataset_guide/checkpoint_reports/checkpoint_20260611_112534_bundle01_20g/UPLOAD_READY.md

@@ -1,6 +1,6 @@
 # Upload Ready
 
-This checkpoint is ready for Hugging Face use as a single JSONL file. Google Drive has a local single-file copy; cloud sync must be verified separately because Google Drive Desktop exceeded the safety RSS threshold during sync.
+This checkpoint is ready for Hugging Face and Google Drive use as a single JSONL file. Google Drive cloud backup was verified with rclone by matching size and SHA256.
 
 - Checkpoint: `checkpoint_20260611_112534_bundle01_20g`
 - Size: 19.11 GiB
@@ -14,4 +14,5 @@ This checkpoint is ready for Hugging Face use as a single JSONL file. Google Dri
 - In-bundle duplicate records: 0
 
 HF verification: uploaded single JSONL and removed legacy `w*-part-*.jsonl` files.
-SSD note: local workspace checkpoint is absent; the remaining local copy is under Google Drive Desktop storage.
+Google Drive verification: rclone remote listing shows one JSONL file, size `20,523,612,203` bytes, SHA256 `a0b2f654ee1ea558416af615998ca4699908dfc94bb747536d7483569918afbb`.
+SSD note: local workspace checkpoint is absent; the remaining local copy is under Google Drive Desktop storage. Do not delete that DriveFS file with `rm`, because deletion may propagate to the cloud copy.