finetuning

# Prerequisites Before starting this workflow, verify: 1. A `use_case_spec.md` file exists - If missing: Activate the `use-case-specification` skill first, then resume - DON'T EVER offer to create a use case spec without activating the use-case-specification skill. 2. A fine-tuning technique (SFT, DPO, or RLVR) and base model have already been selected - If missing: Activate the `finetuning-setup` skill to collect what's missing, then resume - Don't make recommendations on the spot. You MUST activate the finetuning-setup skill. 3. A base model name available on SageMakerHub has been identified - If missing: Activate the `finetuning-setup` skill to get it - **Important:** Only use the model name that `finetuning-setup` retrieves, as it may differ from other commonly used names for the same model # Critical Rules ## Code Generation Rules - ✅ Use EXACTLY the imports shown in each cell template - ❌ Do NOT add additional imports even if they seem helpful - ❌ Do NOT create variables before they're needed in that cell - 📋 Copy the code structure precisely - no improvisation - 🎯 Follow the minimal code principle strictly - ✅ When writing a notebook cell, make sure the indentation and f strings are correct ## User Communication Rules - ❌ NEVER offer to run the notebook for the user (you don't have the tools) - ❌ NEVER offer to move on to a downstream skill while training is in progress (logically impossible) - ❌ NEVER set ACCEPT_EULA to True yourself (user...