WorkBuddy stuck on models.json when integrating DeepSeek V4 – anyone know where I went wrong?

I came across an article about the WorkBuddy low-code platform that mentioned you can build your own Skills, set up triggers, and even swap in a specific version of DeepSeek. I thought it made sense. After all, I spend my days shuffling expense reports and spreadsheets back and forth, and I hate repetitive work the most. So I figured I'd try connecting WorkBuddy with DeepSeek to automate some summaries.