v0.1.9

Documented

• The README and llms.txt examples now catch NwcError and map code and
  walletCode to not-sent, refused and ambiguous outcomes, define every
  variable they use, and name farrier-kit in the install line.
• llms.txt lists the fields of NwcCapabilities, PayInvoiceResult,
  NwcTransaction, GetInfoResult and GetBalanceResult, the units of
  amount and what payInvoice's optional amount is for, the
  NwcTransport interface, the pool argument of NostrRelayTransport and
  the extension 05 parameters.
• listTransactions rejects a limit above 20 with INVALID_REQUEST; the
  docs previously said it was capped. The README and llms.txt now say so.
• connect() is optional: request methods call it when no capabilities are
  cached. Documented, with the effect of close().
• AGENTS.md classes INVALID_RESPONSE and ambiguous WALLET_ERROR codes
  with the other post-publication failures.
• The README names the type-only core and filter nostr-tools subpaths and
  no longer names the internal execute method.
• recipes/ is now in the published package, and the README links
  RELEASING.md by its repository URL because it is not published.

---

Reproducible build: byte-identical output verified across two independent CI runners.

Artefact integrity

file:      forgesworn-nwc-kit-0.1.9.tgz
size:      47777 bytes
sha256:    16e91c7bbf48b6449e8dd82afd618f7104c2211a723170561a87cced4c86c7cd
sha512-XmszWLHjYWztbBENgerjFizZiB1Qzg8VTcFhW6QynT1c2xvp6DVByzY6s5VZLo4myq6JIdWZ8AG1VRerG6KyWA==

Verify against the registry tarball:

curl -sLO https://registry.npmjs.org/@forgesworn/nwc-kit/-/nwc-kit-0.1.9.tgz
shasum -a 256 nwc-kit-0.1.9.tgz