#3656 [TUI] launch overwrites the config's "log" on every run, so each model/context gets its own log file under %LOCALAPPDATA% with no index and no rotation

Description

### Area

[TUI]

### Desktop app, Terminal or source?

Terminal (the `strata` command)

### What happened

The model config used to name one log, `M:\Strata\strata-iq3_xxs.log`, which every start appended to ([serve/server.py:995](#L995), `open(log, "a")`; nothing in `serve/` rotates or caps it). After `launch`, the engine log for this model is `C:\Users\njcr\AppData\Local\Strata\launch\iq3_xxs-240k.engine.log`, and each profile also writes `runtime\<profile>.server.log` and `runtime\<profile>.host.log`. A `log` key the person set in their own config is overwritten on every launch. The history I had built across 135 sessions in one file (3.2 MB) is now split across per-profile files and not preserved, which makes archaeology when things go wrong harder.

There are now also two copies of the same run config — the install folder's `strata-iq3_xxs.json` and `%LOCALAPPDATA%\Strata\launch\iq3_xxs-240k.json` — and the profile points at the second (`"source_config": "C:\\Users\\njcr\\AppData\\Local\\Strata\\launch\\iq3_xxs-240k.json"`). They had drifted apart: the install copy still named the single log, the AppData copy named the per-profile one. Nothing in either file says which is authoritative.

### Smallest steps or command that reproduce it

Set `"log": "M:\\Strata\\strata-iq3_xxs.log"` in a model config, run `launch`, and read the file that `launch` wrote: `log` names `…\Strata\launch\<name>.engine.log`.

### Reproduction status

Reproduced locally.

### Strata version

Strata 0.2.2 · engine 0.1.47

### Graphics card, memory and system

RTX 4070 Ti SUPER 16 GB · 63 GB RAM · Windows 11 x64

### Additional Thoughts

Print the log paths in the launch summary, and mention `strata logs --follow` ([strata_cli/monitor_commands.py:63-72](#L63-L72)) or the monitor's Logs view as the way to watch a managed instance. `strata serve` keeps the config's own log and streams the server into the terminal, which is what the per-model `.bat` used in the 0.1.x days.