The SimpleFIN protocol only defines pending=1 (include pending); pending
transactions are excluded by default when the param is absent. Bridges
presence-check the param, so the pending=0 we sent when the 'Include
pending transactions' setting (or SIMPLEFIN_INCLUDE_PENDING=0) was
disabled behaved exactly like pending=1, making the setting a no-op —
pending transactions kept being downloaded, causing pending/posted
duplicates and churn.
Omit the pending query param entirely unless pending is enabled, per
the spec.
Fixes#2440
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
d61ee3abea