* fix(reconciliation): server-side confidence floor for unattended auto-apply
runReconciliation applied every greedy match, including auto_fuzzy at
confidence 0.75, with no server-side threshold. The UI is checkbox-gated,
but the unattended callers (enable-banking nightly sync cron, the
extension's post-sync sweep, and the v1 run endpoint) had no guardrail.
- Add ReconciliationOptions.confidenceThreshold (0..1, clamped): the
apply loop skips matches below it. Skipped matches stay in the result's
matches array and are counted in the new skippedBelowThreshold field,
so they are reported for review rather than silently dropped. Dry runs
are unaffected; omitting the threshold preserves current behavior.
- Both enable-banking sync callers now pass
DEFAULT_UNATTENDED_CONFIDENCE_THRESHOLD (0.9, mirroring the
gnubok_auto_match_period MCP default), so unattended runs never commit
fuzzy (0.75) or date-range (0.85) matches.
- v1 POST /reconciliation/bank/run accepts confidence_threshold
(optional, 0..1, mirroring the MCP tool naming) and returns
skipped_below_threshold; registry docs/pitfalls updated.
Closes#880
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(reconciliation): surface skippedBelowThreshold in unattended sync logs
Review finding on the first pass: the floor's 'reported, not silently
dropped' guarantee never reached the two unattended callers, which
discarded or under-logged the result. Also logs the DECISIONS.md line
for the deliberate no-default choice on the v1 route.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Jakob Wennberg
9b126d22b9