make-app-production-readylisted

The application works. What it does not have is everything underneath a product that has customers. This installs that layer in one pass, and the builder keeps their brand, their pricing and their customer. ## Diagnose before installing anything ## Scan the code before you decide Evidence beats inference. In the repository, run: ```bash npx @trustycap/cli productionize --json ``` It scans the route handlers with the TypeScript compiler API and classifies each against the published production standard (`GET https://api.trustycap.com/v1/production/requirements`). Every finding carries the file and line, the 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: the scanner did not see enough, so read the code it points at rather than installing over it. If the project already satisfies a requirement another way, declare it in `trustycap.production.json` and move on. ## Ask what the platform already gave them Before the codebase, the platform. A Lovable project arrives with a database, a login page, file storage, scheduled jobs and a payment provider already wired up. A v0 project arrives with an interface and nothing behind it. They look the same from the outside and they are not the same problem, and recommending a database to somebody who already has one is the fastest way to lose their trust. ```bash curl -s -X POST