agent-runtime-gateway-smoke-test

Topics in the source

• Agent Runtime Gateway Smoke Test
• When to Activate
• Required Inputs
• Authorization and Cleanup
• Smoke Test
• Connected Tool Follow-up
• Failure Handling
• Output Contract

Use this workflow when an agent task runs in a remote sandbox that calls back to a local API through a gateway. It verifies the whole path without relying on connected tools or private production data. A local agent API needs an end-to-end runtime check. A task stalls after dispatch and the gateway or tunnel may be unreachable. A web app is temporarily pointed at a local API for agent testing. A previous test left the web app pointing at a stopped API. Repository-relative instructions for starting the API and web app. The gateway route path and its expected anonymous response. An isolated test agent, a tool-free prompt, and its exact expected answer. A way to inspect task status and confirm a callback reached the local API. Provider credentials, supplied through the project's normal secret store. Name the providers in shared documentation; never copy credential values into the skill or test report. If these inputs are unavailable, report the missing input instead of guessing an endpoint or using a real account. Confirm authorization to expose the local test API through the selected tunnel provider, dispatch the test task, and temporarily change the web app route. Use an isolated lo

This is an excerpt. Refer to the complete source and its current requirements.