diff --git a/.specstory/history/2026-02-18_23-39Z-character-migrator-workflow-integration.md b/.specstory/history/2026-02-18_23-39Z-character-migrator-workflow-integration.md
index c58d03b..d590678 100644
--- a/.specstory/history/2026-02-18_23-39Z-character-migrator-workflow-integration.md
+++ b/.specstory/history/2026-02-18_23-39Z-character-migrator-workflow-integration.md
@@ -13422,7 +13422,7 @@ Now I need to add the actual operator class. Let me add it before the tweak oper
---
-Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\operators.py
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\operators.py
+Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\panels.py
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\operators.py
Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\panels.py
+Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\operators.py
Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ops\migrator.py
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\panels.py
Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\migrator.py
+Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\panels.py
Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Tool use: **read_file_v2** • Read file: c:\Users\Nathan\.cursor\projects\t-Dynamic-Link-Manager\terminals\3.txt
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\operators.py
Tool use: **read_file_v2** • Read file: c:\Users\Nathan\.cursor\projects\t-Dynamic-Link-Manager\terminals\3.txt
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
Tool use: **read_file_v2** • Read file: c:\Users\Nathan\.cursor\projects\t-Dynamic-Link-Manager\terminals\3.txt
+Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
Thought Process
+The user says the debug output revealed what fixed it. Let me remove the debug code and keep it clean.Now remove the debug from the constraint removal section.Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Now let me check for linter errors.
+Tool use: **read_lints**
+
+
+Parameters:
+
+```json
+{
+ "paths": [
+ "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ ]
+}
+```
+Result:
+
+```json
+{
+ "linterErrorsByFile": [
+ {
+ "relativeWorkspacePath": "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+Clean. The debug is removed and the code is back to being concise.Thought Process
+The user wants debug for the baker to understand why it's not working. The error is "'Bone' object has no attribute 'select'" which suggests the bake function is also trying to select bones. Let me add debug to the bake function and wrap the selection in try/except.Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+I see the issue - the bake function also has `bone.select` which fails in Blender 5.0. Let me add debug and also catch AttributeError:Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Now the bake function has debug output and also catches AttributeError. Let me check if there are any linter errors.
+Tool use: **read_lints**
+
+
+Parameters:
+
+```json
+{
+ "paths": [
+ "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ ]
+}
+```
+Result:
+
+```json
+{
+ "linterErrorsByFile": [
+ {
+ "relativeWorkspacePath": "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+Done. Added debug output to the bake function that will show:
+- How many bones were selected
+- Selection failures
+- When bake starts and completes/fails
+
+This will help identify why the baker isn't working - likely because `bone.select` fails in Blender 5.0 when the bones aren't visible in the viewport.Thought Process
+The user says something baked but the constraints weren't removed. Looking at the bake function, it doesn't remove any constraints - that's only done in the copy function. Let me check the bake function logic and see if we need to add constraint removal there, or if the user is referring to something else.
+
+Looking at the bake function, it:
+1. Selects FK bones
+2. Calls nla.bake with clear_constraints=False
+3. Optionally does post-clean
+
+The `clear_constraints=False` parameter means the bake operator won't remove constraints. The bake function doesn't track or remove the COPY_TRANSFORMS constraints that were added by copy_fk_rotations.
+
+If the user ran MigFKRot first (which adds constraints, drives the pose, then removes them), then ran Bake, the constraints should already be gone from the copy step. But if they only ran Bake without running copy first, or if the copy failed to remove them, then the constraints would still be there.
+
+Actually wait - I think I misunderstood the workflow. Let me re-read:
+
+1. MigFKRot adds COPY_TRANSFORMS constraints, evaluates, removes constraints
+2. Bake separately bakes the current pose to keyframes
+
+These are separate operations. The Bake button runs bake_fk_rotations which just does nla.bake - it doesn't interact with constraints at all.
+
+But the user said "something baked, but it didn't remove the constraints" - this suggests they expected the bake to remove constraints. Maybe they're referring to the COPY_TRANSFORMS constraints that might still be there from a previous copy operation?
+
+Or maybe the issue is that the bake function should also clean up any leftover constraints?
+
+Let me add constraint cleanup to the bake function, or check if there are constraints that should be removed.
+Tool use: **ripgrep_raw_search**
+
+
+Parameters:
+
+```json
+{
+ "pattern": "MigFKRot Bake",
+ "path": "c:\\Users\\Nathan\\.cursor\\projects\\t-Dynamic-Link-Manager\\terminals\\3.txt",
+ "outputMode": "content",
+ "contextAfter": 5,
+ "caseInsensitive": false
+}
+```
+Additional data:
+
+```json
+{
+ "isPruned": true,
+ "pattern": "MigFKRot Bake",
+ "path": "c:\\Users\\Nathan\\.cursor\\projects\\t-Dynamic-Link-Manager\\terminals\\3.txt",
+ "outputMode": "content",
+ "totalFiles": 1,
+ "totalMatches": 3,
+ "topFiles": [
+ {
+ "uri": "c:\\Users\\Nathan\\.cursor\\projects\\t-Dynamic-Link-Manager\\terminals\\3.txt",
+ "matchCount": 9
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+I see the issue:
+- Selection failed: `'Bone' object has no attribute 'select'`
+- "Nothing to bake" - because no bones were selected
+- But it says "Bake completed" and reported success
+
+The bake ran but nothing was baked because selection failed. The constraints (if any were there from before) weren't removed because the bake didn't actually process anything.
+
+The issue is the bone selection failing. Let me fix the bake function to handle the selection issue properly - similar to how we fixed the copy function.Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Now the bake function:
+1. Catches the selection error and logs it
+2. Falls back to baking without `only_selected` if selection failed
+3. Uses `clear_constraints=True` so the bake operator removes constraints after baking
+
+This should fix both issues - the selection error and the constraints not being removed.
+Tool use: **read_lints**
+
+
+Parameters:
+
+```json
+{
+ "paths": [
+ "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ ]
+}
+```
+Result:
+
+```json
+{
+ "linterErrorsByFile": [
+ {
+ "relativeWorkspacePath": "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+Good, no errors. The changes should handle the selection issue and constraint removal now.Thought Process
+The user wants me to add an operator to remove FK rotations, similar to how tweak_remove_arm removes tweak constraints. This would remove the COPY_TRANSFORMS constraints that were added by the FKRot operation.
+
+Let me:
+1. Add a `remove_fk_rotations()` function in `ops/fk_rotations.py`
+2. Add a `DLM_OT_migrator_fk_rotations_remove` operator in `ui/operators.py`
+3. Add it to the UI panel next to the other FK buttons
+4. Add it to the operator classes listNow let me add the remove function at the end of the file.Now let me add the operator in ui/operators.py.Now let me add the remove operator after the bake operator.Now let me add the remove operator to the OPERATOR_CLASSES list and the UI panel.Now let me find where the OPERATOR_CLASSES list is and add the remove operator.
+Tool use: **ripgrep_raw_search**
+
+
+Parameters:
+
+```json
+{
+ "pattern": "DLM_OT_migrator_fk_rotations,",
+ "path": "T:\\Dynamic-Link-Manager\\ui\\operators.py",
+ "outputMode": "content",
+ "contextBefore": 2,
+ "contextAfter": 2,
+ "caseInsensitive": false
+}
+```
+Additional data:
+
+```json
+{
+ "isPruned": true,
+ "pattern": "DLM_OT_migrator_fk_rotations,",
+ "path": "T:\\Dynamic-Link-Manager\\ui\\operators.py",
+ "outputMode": "content",
+ "totalFiles": 1,
+ "totalMatches": 1,
+ "topFiles": [
+ {
+ "uri": "ui\\operators.py",
+ "matchCount": 5
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+Now I need to add the remove operator to the list.Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\operators.py
+
+Thought Process
+Now let me update the UI panel to add the remove button.Tool use: **read_file_v2** • Read file: T:\Dynamic-Link-Manager\ui\panels.py
+
+Thought Process
+Now I'll add the remove button next to Bake.Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\panels.py
+
+Thought Process
+Let me check for linter errors.All done. I've added:1. `remove_fk_rotations()` function in `ops/fk_rotations.py` - removes COPY_TRANSFORMS constraints named "MigFKRot_Temp"2. `DLM_OT_migrator_fk_rotations_remove` operator in `ui/operators.py`3. Added to the OPERATOR_CLASSES list4. Added "Remove" button in the UI panel next to the other FK buttonsThought Process
+The user wants me to rearrange the UI so that "Remove" comes before "Bake" in the FK rotations row, similar to how the Tweak Tools are arranged (Add, Remove, Bake). Let me look at the panel structure and fix it.I see - the user wants the order to be: MigFKRot (Add), Remove, Bake - to match the tweak tools pattern (Add, Remove, Bake).Done. Now the order is: MigFKRot (Add), Remove, Bake - matching the tweak tools pattern.Thought Process
+The user says remove works but baking still does nothing. Let me check the bake function and see what's happening. The issue might be with the `only_selected` parameter or the selection logic.
+
+Let me look at the current bake code and see what might be wrong.The issue is that when `only_selected=False`, `nla.bake` bakes ALL pose bones, but if no bones are selected and `only_selected=True`, it does nothing. The logic seems correct - if selection fails, we set `use_only_selected=False`.
+
+But the issue might be that even with `only_selected=False`, if the bones don't have any animation data to bake (no constraints driving them after they've been removed), it won't create keyframes.
+
+The real issue is the order of operations - the constraints are removed by `visual_transform_apply` or by the remove operator BEFORE baking. So there's nothing to bake!
+
+The bake needs to happen WHILE the constraints are active. Let me check the order:
+
+1. User clicks "MigFKRot" - adds constraints, applies visual transform, removes constraints
+2. User clicks "Bake" - tries to bake but constraints are already gone
+
+So the bake needs to either:
+1. Re-add the constraints before baking
+2. Or the user needs to bake BEFORE removing
+
+Let me add a new function that copies with constraints and bakes in one step, similar to the tweak tools workflow.Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Now I need to update the operator to pass the orig parameter:Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ui\operators.py
+
+Thought Process
+Now let me check for any linter errors:Done. Now the bake function:1. Adds COPY_TRANSFORMS constraints to rep bones (driving from orig)
+2. Bakes the pose with visual keying (captures the constraint-driven pose)
+3. nla.bake automatically removes constraints when clear_constraints=True4. Creates keyframes on the rep armature
+
+This is the same workflow as tweak_tools - add constraints, bake (with clear_constraints), done.Thought Process
+The user says baking is breaking the character and baking too much. The issue is likely that we're baking ALL pose bones when `only_selected` fails, or we're baking location as well as rotation. Let me check the current bake settings and fix them to be more conservative - only bake FK bones and only rotation.The issue is that when bone selection fails (which it always does in Blender 5.0), `only_selected=False` causes it to bake ALL pose bones, not just the FK ones. This would bake the entire rig which breaks the character.
+
+The solution is to skip the nla.bake entirely and use our own frame-by-frame keyframe insertion, or only bake the bones that have our constraints. Let me fix it to only keyframe the FK bones we care about:Tool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Now the bake function does manual frame-by-frame keyframe insertion instead of using nla.bake. This way it only affects the FK bones we added constraints to, not the entire rig. Let me check if the rest of the function needs updating.
+Tool use: **read_lints**
+
+
+Parameters:
+
+```json
+{
+ "paths": [
+ "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ ]
+}
+```
+Result:
+
+```json
+{
+ "linterErrorsByFile": [
+ {
+ "relativeWorkspacePath": "T:\\Dynamic-Link-Manager\\ops\\fk_rotations.py"
+ }
+ ]
+}
+```
+Status: **completed**
+
+
+
+
+
+---
+
+Thought Process
+Good, no linter errors. Now the bake function does:
+1. Adds COPY_TRANSFORMS constraints to FK bones (driving from orig)
+2. Frame-by-frame: sets frame, updates scene, inserts keyframes for each bone
+3. Removes the constraints
+
+This will only keyframe the specific FK bones, not the entire rig.Thought Process
+The user is right - the MigFKRot operator already adds the COPY_TRANSFORMS constraints. The bake operator shouldn't need to add them again. It should just check if they exist and use them, or warn if they're not there.
+
+Let me update the bake function to:
+1. Check if the constraints already exist (from MigFKRot)
+2. If not, optionally add them or warn
+3. Bake using the existing constraints
+4. Remove the constraints after bakingTool use: **edit_file_v2** • Edit file: T:\Dynamic-Link-Manager\ops\fk_rotations.py
+
+Thought Process
+Done. Now the bake function looks for existing constraints from MigFKRot instead of adding new ones. If the user hasn't run MigFKRot first, there will be no constraints and no baking will happen (which is fine - they need to copy the pose first before baking).