V3.6.2 - ExChek Enterprise Plugin
Late connections still count.
The transaction-sync credentials gate is now re-evaluated at every milestone instead of once at flow start. A real session connected the /mcp/pro connector mid-conversation (to unlock the paid PDF) and ended with zero events on the dashboard — the start-of-flow check had silently disabled sync for the whole engagement.
- When an authenticated connection appears mid-session, the skill asks the sync consent question at the next milestone and, on a yes, records the milestones already passed (the server replaces same-type events per transaction, so late recording is idempotent).
exchek-classify's render step handles the common case explicitly — connector added to unlock the PDF → ask consent there, backfill jurisdiction/classify/screen events.- The license / jurisdiction / export-docs / red-flag sync sections carry the same re-check rule.
Full details in CHANGELOG.md.