These tasks mix the unit on new data, the way production work arrives: a release script needs a file name, a CI job needs to know whether requirements are pinned, a load balancer reads a health check, and an API gateway enforces a rate limit.
Each one has a boundary on purpose: a scope before a breaking-change marker, an option line in a requirements file, a failure that should degrade rather than take the service down, a request exactly one window later, a nested setting next to the one being overridden, a field trying to overwrite the log level, and a version that sorts differently as text. Name the boundary before you write the code, and let the hidden tests confirm it.
Out: 'fernhill_sync'. Wheel names use underscores inside the project name.