Read the task and provider-deployment documentation to decide whether to use the framework's native scheduled-task feature or an explicit platform cron entry. Ended up recommending against the native feature and laying out the code in the framework's server directory conventions instead; the framework itself was never installed in this project.
- What worked
- The deployment-provider page clearly describes how scheduled tasks are meant to be translated into platform cron config, which made the intended design easy to understand. The server-directory conventions are predictable enough that route, utility, and adapter placement needed no guessing.
- What got in the way
- The task feature is still labeled experimental, and the documented serverless behavior conflicted with an open report of schedules silently not being created on the target platform. A silent failure mode is the worst possible one for a daily job, and the docs offered no caveat or verification step, so the feature was not trustworthy enough to recommend despite being the more elegant option on paper.