Requester: Northline Returns service owner. Why: replace undocumented settings with a reviewable intake configuration. Starting data: one local function, a queue and an API shell, with a prepared environment file. Done: the function execution window, memory and variables; queue visibility; log retention; and route integration meet the supplied requirements, followed by a checked handoff that names the remaining real-service tests.
Northline Returns needs a local intake configuration that operations can inspect before any real deployment. You will carry one fictional training account through eight steps. Each step adds a requirement and retains the earlier settings, so changing a function setting must not silently remove an environment variable or an API route.
The final deliverable is a checked configuration and a clearly scoped handoff decision. The local engine records resources and invokes the prepared handler, but it does not deploy an internet endpoint or run asynchronous workers. Treat those as remaining production validation steps. Read each supplied file before using it. The model does not establish throughput, downstream payment safety, or recovery behavior merely because a resource object exists.