Tracker: production-ready / first tagged release (bdk-dart 1.0.0)

This issue tracks the bar for the first tagged/stable bdk-dart release and also collects feedback from real integrations about what they consider production-ready. Items here are release criteria for bdk-dart itself, not necessarily blockers for downstream apps shipping on the current 2.3.x line.

Feel free to add anything you think is required:

## Open Items

- [ ] First tagged bdk-dart release targets bdk-ffi 3.x
- [x] `main` is on `bdk-ffi` `v3.0.0` via #70
- [x] first RC tag is cut from that baseline
- [ ] stable `1.0.0` tag is cut after RC validation
- [ ] publish library to pub.dev

## Open Questions
- [ ] Track web target support strategy and feasibility (#40)

## Active work
- [ ] Improve example app to MVP-level developer reference (#5)
- [ ] Prebuilt binaries path with verification and fallback (`auto | always | never`) (#20)

## Done
- [x] Baseline CI workflow exists (format/analyze/test/demo analyze) (#10)
- [x] Fix example resource-disposal bug(s) (#14)
- [x] Define and document supported platform/architecture matrix (#24)
- [x] Pub.dev readiness (metadata, publishing steps, release checklist) (#28)
- [x] Add CI compatibility checks against upstream `bdk-ffi` changes (#30)
- [x] Add integration test harness for network-based client tests (#31)
- [x] Add missing CI coverage for target matrix builds (#25)
- [x] Add integration tests for Electrum sync/apply/persist flow (#26)
- [x] Add integration tests for Esplora sync/apply/persist flow (#27)
- [x] Track and move to `bdk-ffi` 2.3 release tags when available (#18)
- [x] API ergonomics improvements (named-argument-friendly surface) (#21)
- [x] `UniFfi::UnexpectedEnumCase` uniffi-dart (#46)
- [x] Execute pub.dev release metadata + dry-run checklist (#43)