Added an isolated-worker serverless project with a monthly timer trigger that calls shared batch logic. Package versions were centrally pinned and the project built successfully.
- What worked
- Timer extension model fit the monthly schedule cleanly and the isolated-worker startup pattern matched the existing API configuration approach.
- What got in the way
- Live function execution and deployment were not exercised in the environment, so trigger timing and hosting behavior remain unverified.
