[codex] Reset scoped unit of work after rollback

[SadPossum]

What changed

• add the optional, provider-neutral IRollbackResettableUnitOfWork contract;
• reset transactional command state after rollback for failed results and exceptions, even when rollback itself fails;
• clear EF Core change tracking so abandoned mutations and domain events cannot leak into a later command in the same dependency-injection scope;
• preserve the original operation exception while retaining rollback/reset failures as diagnostic data;
• document the contract and add same-scope regression coverage.

Why

Rolling back a database transaction does not clear EF Core tracking. A failed handler could leave modified aggregates and queued domain events in a scoped DbContext, allowing an unrelated later command in that same scope to persist work that had already failed.

The capability is optional, so custom unit-of-work implementations remain source-compatible. EF-backed implementations opt in through the shared base class.

Consolidation

This branch is rebased on current dev, which already contains the framework solution synchronization and patched SSH.NET test-harness dependency. Redundant drafts #23 and #25 are closed; this is the only active Framework PR.

Validation

• full warning-as-error solution build
• focused rollback/reset regression tests
• full non-Docker Framework test suite
• solution synchronization and source-package checks
• repository security and release checks
• direct/transitive vulnerability audit
• hosted validate, provider, owned-source, and Trivy jobs

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.