tunelisted

# squirrel-mode tuning /squirrel:tune edits one field of the existing profile at `~/.squirrel/profile.md`. It never re-runs the seven-question interview. ## Procedure 1. Read `~/.squirrel/profile.md`. If it does not exist, say so in one line, tell the user to run `/squirrel:init` first, and stop there. 2. Show the current value of all 11 fields as one compact block: `language`, `answer_position`, `step_style`, `max_list_items`, `code_style`, `explanation_budget`, `options_per_answer`, `confirm_topic_switch`, `progress_recap`, `extras_section`, `tone`. If the file exists but a given field's line is missing entirely, or is malformed - not in the exact `field: value` shape, or carrying a value outside that field's allowed values - show that field as unset (for example, `tone: (unset)`) rather than guessing a value, and treat it as the `rules/base-rules.md` default for that field until the user sets it explicitly through this command. Do not write that default into the file on your own initiative; showing it is not setting it. 3. Ask exactly one question: which field to change, and to what. Offer field-name options as multiple-choice when 4 or fewer are the likely candidates from context; otherwise ask the user to name the field directly. 4. Any of the 11 fields can be changed this way, one at a time, including the four that `/squirrel:init` question 2 set together as a bundle (`step_style`, `explanation_budget`, `extras_section`, `tone`). Each of the four is independently edi