PackageFlashyFinancial

@flashyfinancial/wallet-wdk

The FlashyFinancial-scoped home of the wallet capability: the AAO WalletCapability, a FlashyOS authorizer client, an MCP elicitation handler, and a WDK policy rule that defers to the authorization plane — extracted verbatim from flashyos/packages/wallet-wdk into wallet-core.

version 0.1.0 · measured 2026-10-30 from a checkout · source: github.com/FlashyFinancial/wallet-core/packages/wallet-wdk

npm i @flashyfinancial/wallet-wdk — prepared, not yet published; @flashyos/wallet-wdk is the copy the registry serves today

The same OperationRecord, extractors and FlashyOSAuthorizer as @flashyos/wallet-wdk, documented on that page; only the npm scope, the cross-package dependency versions that name it, and the repository and homepage fields changed. Nothing here diverges in behaviour from the flashyos original as of the commit that created the repository.

Edge cases — each one paid for once

An extraction is not a move: two scopes carry one code until somebody reconciles them

wallet-core’s README says it plainly — flashyos’s own copies of the three packages are untouched and keep publishing as @flashyos/*, so a fix landing in one tree does not land in the other, and having flashyos consume these packages instead of its own copies is a deliberate follow-up that has not happened. A reader choosing a scope today is choosing which copy’s future fixes they get, and this catalogue links both rather than pretending there is one.

← Full catalog · The doctrine behind the tools · Adopt one