V3MutationService and V3CompatibleTableBinding - codex 5.3

[em3s]

Summary

Refactor duplicated mutation logic in V3MutationService and V3CompatibleTableBinding to improve maintainability and ensure consistent error handling in single and multi-edge mutation paths.

Closes #195

Plan

Created by opencode (gpt-5.3-codex)

• Extract buildHBaseMutations() in V3CompatibleTableBinding
• Extract decodeCurrentState() in V3CompatibleTableBinding
• Extract resolveMutationContext() in V3MutationService
• Extract writeCdc() in V3MutationService
• Extract and apply handleMutationError() in both mutation methods
• Add LockAcquisitionFailedException handling to mutateMultiEdge

Progress

• Created feature branch, empty planning commit, and PR — opencode (gpt-5.3-codex) (commit ec58d98)
• Implemented helper extraction and lock-failure parity fix in V3 mutation flow — opencode (gpt-5.3-codex) (commit 9908c4c)

[em3s]

Review Round 1

by opencode (gpt-5.3-codex)

Issues Found & Fixed

Severity	Issue	Status
HIGH	mutateMultiEdge error handling initially swallowed non-lock errors and changed previous propagation behavior.	Fixed: narrowed fallback handling so only LockAcquisitionFailedException is converted to ERROR status; non-lock errors now propagate.
WARNING	Async subscribe() calls for CDC write and stale-lock cleanup have no explicit error consumer.	Skipped: pre-existing behavior in this service; keeping this refactor scoped to duplication removal and lock-failure parity to minimize behavioral changes.
SUGGESTION	resolveMutationContext could be synchronous instead of returning Mono.	Skipped: left reactive style unchanged for consistency with surrounding method flow in this refactor.

Result

All tests passing. No CRITICAL/HIGH issues remain.

[em3s]

opus 4.6 wins

See #199