Post analytics for a connected account

Reads a token's Trust Kit setup straight from the chain and returns it as a public document: every module found, every wallet it references with its live balance, and — the part that matters — exactly what can change, who can change it, and how fast. **It works for any token on any supported chain.** There is no allowlist and no putty-only path: a module is recognised by the getters its contract answers, so a token launched on Pons or Hookr reads the same as one launched here, and a token putty never heard of reads too. A token with no modules returns an empty `modules` array, not a 404 — the token is real, its setup is simply empty. **Every amount is a decimal string in the token's base unit.** Divide by `10^decimals` to display one; do not parse with `Number()`, which loses precision on exactly the values a trust page exists to be precise about. **`mutable` is the load-bearing field.** A control with `mutable: false` is a Solidity `immutable`: there is no setter in the bytecode, so nothing can change it. A control with `mutable: true` always carries a `range` and a `timelockSeconds` — the projector's one invariant — so a bounded, delayed change cannot be rendered as an instant one. When a bound or a timelock could not be read from the chain, the parameter is reported as immutable and a warning is recorded, because showing an unbounded parameter as bounded is the one failure this page must not have. `provenance.warnings` is empty only when the whole document was read. A partial read is reported as partial rather than presented as complete, and a node that could not answer never becomes a silent zero.