add-metered-billinglisted

An application that cannot record what a customer used cannot charge for it, and retrofitting the meter after the fact means guessing at history. ## 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`. - Is any usage recorded per customer today? In what unit, and does that unit match what the customer thinks they are buying? - Is there a rate card the customer can see before they are charged? - Is anything charged today, and by what? ## Fit, and not for TrustyCap meters and bills **the builder** for the infrastructure the builder uses. **It is not for** charging the builder's own end customers. Their customers' money is their own rail, and that distinction matters legally and operationally. If the ask is "how do I charge my users", say so plainly and point at `https://trustycap.com/answers/charge-customers-for-usage?src=skill`, which