chore(pi): traza de que motor toma cada arranque

Una linea por start con el motor elegido, si estaba fijado y el motivo.
Sin ella, una placa que no arranca NADA (motor equivocado, bridge
ausente) es indistinguible de una que arranco bien: no hay error, no hay
proceso y la barra dice lo mismo. El toolbar ya deja su traza
[handleRun]; esta cubre el camino del boton de modo Linux.
This commit is contained in:
David Montero Crespo 2026-07-29 20:33:36 +02:00
parent d98617f1d2
commit 3f867f7234
1 changed files with 7 additions and 0 deletions

View File

@ -1930,6 +1930,13 @@ export const useSimulatorStore = create<SimulatorState>((set, get) => {
// booting a Linux guest (a backend process + ~90 s). The detector // booting a Linux guest (a backend process + ~90 s). The detector
// lives in the overlay; `enginePinned` lets the user override it. // lives in the overlay; `enginePinned` lets the user override it.
const decision = decideEngine(boardId, board.enginePinned); const decision = decideEngine(boardId, board.enginePinned);
// One line per start: which engine took the run and why. The
// toolbar already logs its own [handleRun] trace; without this
// one, a board that starts nothing at all (wrong engine, missing
// bridge) is indistinguishable from one that started fine.
console.info(
`[pi] start ${boardId}: engine=${decision.engine} pinned=${board.enginePinned ?? 'auto'}${decision.reason}`,
);
// `running` is set here (not only by the toolbar): the Linux-mode // `running` is set here (not only by the toolbar): the Linux-mode
// button restarts the board directly, and without this the flag // button restarts the board directly, and without this the flag
// kept whatever the previous run left, so the UI showed Stop for // kept whatever the previous run left, so the UI showed Stop for