libsync-diagnostics-and-tooling

To troubleshoot libsync application health issues like failed album downloads, you can run read-only diagnostic scripts to query database states, check download statuses, and identify discrepancies between the database and disk.

You can check database states and deduplication logic in libsync by executing Python diagnostic scripts that query and report on application logs and internal health metrics without requiring manual observation.

Yes, you need Python installed in your environment to run the scriptable libsync diagnostic tools, which you can initiate by executing the env-doctor.sh shell script from the skill directory.

Yes, you can use Python scripts to redact config secrets during application health checks, as the diagnostic toolkit includes specific runnable tools for securely probing WebSocket data and verifying configuration settings.

The best way to investigate discrepancies between the libsync database and disk is to use dedicated troubleshooting scripts that measure application health and report on download statuses to pinpoint sync failures.