What should the Tuner learn next?

[MTSistemi]

The Tuner is where the board actually gets configured: presets, CPU frequency and
undervolt, GPU clock and voltage, the governor, VRAM split, Compute Units and CPU cores
live, fan control, and the two "find my max" wizards.

Two things are already planned — a fan curve editor (today it is a single manual
percentage or the automatic curve, nothing in between) and a configurable HUD that
builds itself from the sensors actually present instead of being hard-wired for the BC-250.

Beyond those, what is missing for you? Some directions we have thought about and not
decided:

• Per-game profiles — apply an overclock when a specific game launches, drop back after.
• A power budget slider instead of separate clock and voltage controls: "quiet",
  "balanced", "everything you have", worked out from measurements rather than guesses.
• Logging what actually happened — clocks, temperature and throttling over a session,
  so a "this crashed" report comes with evidence.
• Importing someone else's profile — the silicon database exists; sharing settings that
  worked on a similar chip does not.

If you use the board daily, what do you keep doing by hand that the Tuner should be doing?