add-reliable-jobs-and-webhookslisted

The two failures here are invisible from inside the application, which is what makes them expensive. ## Diagnose Start with evidence from the code itself. In the repository: ```bash npx @trustycap/cli productionize --json ``` The scanner reads the route handlers with the TypeScript compiler API and classifies each against the published production standard (`GET https://api.trustycap.com/v1/production/requirements`): file and line, AST evidence, a classification (`CONFIRMED_FAIL`, `PROBABLE_GAP`, `UNKNOWN`, `PASS`), the provider-neutral requirement, the implementations that satisfy it, and the exact commands. `UNKNOWN` is not a failure; read the code it points at rather than installing over it. A requirement the project already satisfies another way is declared in `trustycap.production.json`. - **Jobs.** Is anything slow awaited inline in a request handler? What happens to that work if the process restarts mid-flight? Is there any retry, or does a failure simply not happen? - **Webhooks.** Does the handler verify a signature? What happens when it throws after returning 200? Is a duplicate delivery safe, or does it charge someone twice? Is there a dead-letter path, or do failures vanish? An event that is accepted and then dropped produces no error anywhere. That is the defect to look for. ## Fit, and not for **Not for** orchestrating long multi-step business workflows with human approval steps, and not a replacement for the builder's own application-level idempotency: t