zeus-proof-and-analysis-toolkit

Enumerate every trigger event (screen focus, app foreground, wallet create/delete) and every piece of shared mutable state, then build an interleaving table of operation steps versus concurrent events. Classify each cell as serialized, tolerated with a named retryable error, or unreachable with a named guard, and reproduce the bad interleaving before the fix.

Build a matrix of persisted states (fresh install, legacy blob, v2 keychain blob, iCloud-restored device) against each migration in actual execution order read from the code. Prove every cell terminates validly, prove one-shot flags are idempotent even if the app is killed mid-migration, and cover both legacy and v2 load paths.

BackendUtils.call returns false synchronously when the active backend class lacks the method, with no throw. Because EmbeddedLND and LndHub extend LND, a missing override means the method is inherited from LND rather than absent, which can leak unsupported capabilities like supportsChannelFundMax on LndHub.

Unit-trace every variable in the amount path, confining each x1000 or /1000 conversion to a named wire boundary, and use BigNumber instead of floats. Test boundary values 0, 1, 999, 1000, 1001 sats, msat remainders, and fee-equals-amount cases, since Zeus's routing fee rule switches behavior at 1000 sats.

Do not use it for change-control rules, PR gating, migration authoring mechanics, backend capability matrices, historical incident timelines, jest configuration, runtime log capture, or Lightning protocol theory. Those belong to sibling Zeus skills; this toolkit owns only the analysis methods that produce correctness evidence.