Clean up Azure files and topics after sync failures #736

Blocked by #734. The upload retries did not need the fix (#735) deployed and are done; the rest can proceed as noted.

What we know from production as of 4 Oct 2026 (Mission Control, /jobs):

Failed DocumentsSyncJob runs: 129

• 101 uploads failed with RecordNotFound, across 28 topics (21250 to 21632). Retried 5 Oct 2026; all succeeded. Spot check one in Azure (21529 had 14 missing).
• 8 deletes failed with RecordNotFound (topics 21579, 21580, 21583, 21705). The old files are probably still in Azure. Check each before retrying: a delete works by filename, so it would remove a file re-added under the same name.
• 16 deletes failed with Azure 404. The file was never in Azure. Check a few, then discard.
• 4 uploads failed with Azure 416 InvalidRange (topics 21250, 21328, 21458, 21499). Retried 5 Oct 2026; all succeeded. Cause not established.

Data

• 0 byte documents: topic 21476 needs its PDF re-uploaded. Find any others.
• Duplicate topics: 21486 to 21489 are four copies of the same topic. Find any others and decide which to keep.
• The duplicates reported in Discrepancies between SkillRx and Azure #734 (21480 to 21483, 21485) are already deleted. Confirm one good copy of each remains and its file is in Azure.
• Topics with no document attached. Find and fix or remove.
• Topic 21477: file is in SkillRx and Azure but was not listed on the device. Recheck after the above.

CSV export (Topic.csv and File.csv stale since June)

Cause: a test provider was deleted while it still had one topic ("TEST"), which broke both generators every hour. Code fix is in #737.

• Delete the orphaned topic in production (done 5 Oct 2026).
• Confirm Topic.csv and File.csv on Azure have a fresh date after the next hourly run.
• Remove the TEST topic's file from Azure if one was uploaded.