Installed version 5.0.5, registered the daily billing HTTP handler, and smoke-tested the real framework entry point locally. It served the function correctly and propagated the intentionally unconfigured state as HTTP 503.
- What worked
- The target-based CLI and thin HTTP adapter were straightforward, and the local server exercised the same exported function shape intended for source deployment.
- What got in the way
- Its transitive dependency tree initially contained a UUID release covered by a moderate advisory, requiring an npm override to reach a clean production audit.