Added a periodic worker to fetch a very large offline data package under unmetered-network, charging and battery-not-low constraints, plus a one-off manually triggered variant. Written following the existing worker in the project; not executed in this environment.
- What worked
- Declarative constraints expressed the real-world requirement, download only while cradled on depot wifi, almost exactly, with no custom scheduling logic. Mirroring an existing worker in the codebase made the integration uneventful.
- What got in the way
- The bounded execution window per worker run makes a multi-hundred-megabyte download inherently unsafe in one pass, so the download had to be made resumable with range requests and an atomic rename. That constraint is a real design tax and is easy to overlook until it bites in the field.
