Bind each customer to a Verae userId for hop tracing
Some checks are pending
offline / test (push) Waiting to run

Signup registers/binds a Verae central user and stores veraeUserId. Public access stays the zappier API key. Chain JWTs stay server-side behind tokenRef. Authz, billing, and jobs.watch carry veraeUserId.
This commit is contained in:
George Lambert 2026-09-11 16:18:06 -04:00
parent 1b199ca4d4
commit 345aeeead9
79 changed files with 703 additions and 95 deletions

View file

@ -2,7 +2,7 @@
**Package:** `zappier-account-balance`
**Source:** `packages/zappier-account-balance/src/books.js`
**Lines:** 90
**Lines:** 100
## What this module is
@ -30,8 +30,9 @@ Implementation module in `zappier-account-balance`. The tables below are extract
| Name | Parameters |
|------|------------|
| `constructor` | `(none)` |
| `remember` | `customerId, veraeUserId` |
| `prepaidCents` | `customerId` |
| `adjust` | `{ customerId, cents, reason, agent, kind = 'credit' }` |
| `adjust` | `{ customerId, cents, reason, agent, kind = 'credit', veraeUserId }` |
| `recordUsage` | `entry` |
| `recordPayment` | `entry` |
| `statement` | `customerId` |
@ -42,7 +43,7 @@ _No imports detected._
## Call graph (identifiers invoked)
`constructor`, `prepaidCents`, `adjust`, `trunc`, `now`, `toString`, `random`, `slice`, `toISOString`, `unshift`, `recordUsage`, `recordPayment`, `statement`, `filter`, `match`, `handle`, `endsWith`
`constructor`, `remember`, `prepaidCents`, `adjust`, `trunc`, `now`, `toString`, `random`, `slice`, `toISOString`, `unshift`, `recordUsage`, `recordPayment`, `statement`, `filter`, `match`, `handle`, `endsWith`
Each identifier is a call site in this file. Follow the import list to see the defining module; open that modules MD for parameter and return types.