Read scheduling and consumption-pricing material after finding Foundry does not run on a timer by itself. Used that as the first weekly clock, then dropped it when readings and the runner had to live in this API.
- What worked
- Docs were enough to treat it as an external weekly trigger, storage writer, and alert path while the agent service has no native schedule.
- What got in the way
- It could not stay as the runner once the requirement was concrete in-repo storage and orchestration, so it was never configured.
