From 3f867f723482d088df6e53e226515347deff9578 Mon Sep 17 00:00:00 2001 From: David Montero Crespo Date: Wed, 29 Jul 2026 20:33:36 +0200 Subject: [PATCH] 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. --- frontend/src/store/useSimulatorStore.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/frontend/src/store/useSimulatorStore.ts b/frontend/src/store/useSimulatorStore.ts index ffe0e914..eee8effe 100644 --- a/frontend/src/store/useSimulatorStore.ts +++ b/frontend/src/store/useSimulatorStore.ts @@ -1930,6 +1930,13 @@ export const useSimulatorStore = create((set, get) => { // booting a Linux guest (a backend process + ~90 s). The detector // lives in the overlay; `enginePinned` lets the user override it. 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 // button restarts the board directly, and without this the flag // kept whatever the previous run left, so the UI showed Stop for