Add Konsist rule to ensure TransactionManager rollback on Either.Left

[kamiazya]

Context

Currently, TransactionManagerAdapter delegates blindly to the platform TransactionManager. When a transactional block returns Either.Left (indicating an error), the transaction is not automatically rolled back.

Problem

This can lead to partial commits when operations fail, violating transactional consistency.

Suggested Solution

1. Update TransactionManagerAdapter to mark transactions for rollback when the block returns Either.Left:

override suspend fun <E, T> inTransaction(block: suspend () -> Either<E, T>): Either<E, T> =
    platformTransactionManager.inTransaction {
        val result = block()
        if (result.isLeft()) markForRollback()
        result
    }

2. Add a Konsist test to ensure all TransactionManager implementations follow this pattern

3. Add integration tests to verify rollback behavior

Benefits

• Ensures transactional consistency
• Prevents partial commits on errors
• Makes error handling more predictable

Related

• PR feat: implement Context View functionality for filtered scope management #165 (Context View feature)
• TransactionManagementTest.kt
• Suggested by AI review

[kamiazya]

Current status: The TransactionManager interface properly documents rollback behavior, and Konsist tests exist for transaction management patterns. However, there's no specific architectural rule enforcing rollback on Either.Left. The interface documentation at lines 23-24 describes the expected behavior, but automated enforcement through Konsist rules is still needed.