## QA PASSED See QA report document: 4fbe1105-3965-49af-a22c-4f88f5f7a048 All hypotheses tested. Fix verified working. **Testing Summary:** - Move command now correctly displays the canonical identifier (DOCS-3284, DOCS-3285) - Database and server identifiers match the displayed output - Consecutive moves increment correctly **Note:** The installed trckr binary was outdated during initial testing. After reinstalling from source with `make install`, all tests passed.

## Fix Applied **Problem:** The issue move command was displaying the locally-generated identifier before sync completed, causing it to show stale values like "DOCS-1" when the server might assign a different identifier (e.g., "DOCS-3278"). **Root Cause:** The original code flow was: 1. Update issue with new identifier locally 2. Display issue with echo_record() and output message 3. Call try_sync_on_change() to sync This meant the output was shown before sync could update the identifier with the server's canonical value. **Fix (trckr.py lines 1612-1621):** - Moved try_sync_on_change() BEFORE output - Re-read issue from store after sync to get canonical identifier - Added fallback to use original updated issue if re-read fails **Verification:** - All 148 tests pass including 7 issue move tests - The fix re-reads the issue from the store after sync to get the potentially updated canonical_identifier