Backed up items 118-125 (today's grocery trip + 7-item financial batch) to Finance's Google Drive backup spreadsheet per SOP-DATA-BACKUP.md, discovering along the way that Finance actually has two separate, unreconciled backup mechanisms: server-side Finance_Ledger_MASTER.xlsx (SOP-FINANCE-LEDGER.md, not reachable via HTTP - 403 on backups/ dir, no API found) and this Drive-based one (SOP-DATA-BACKUP.md, spreadsheet_id 1HmgBi1AvXEA8lPBYyqRYotesB8qrixYTfOYqepoCw0c, gdrive-api.php?action=sheets_append - a real working endpoint). TASKGATE correctly routed to SOP-DATA-BACKUP.md. First call failed with token in JSON body (unauthorized); token must be passed as a URL query param instead - documented here for next time. Appended 1 accidental TEST row while diagnosing the auth format (row 2, A2:F2) - left in place rather than attempting a delete with no documented delete/update mechanism (SOP-GDRIVE-SERVICE-ACCOUNT.md explicitly says drive_update doesn't work yet); same precedent already exists in Travel's own sheet per this SOP's own text. Then appended the real 8 rows (A3:F10) covering items 118-125 with Date/Category/Description/Amount/Status/Notes matching Finance's seeded header. Server-side Finance_Ledger_MASTER.xlsx remains unreconciled/inaccessible - flagged to USR369, not silently resolved.