Hide outcome row until a game outcome exists (player-vs-bot and player-vs-player)

[Copilot]

The Outcome field in the player-vs-bot game info box was always shown, even while a game was in progress with no outcome yet (displaying a placeholder --). This mirrors the behavior already implemented for player-vs-player.

Changes

• player_vs_bot.html: Added id="info-outcome-row" and style="display: none" to the Outcome <tr>, hiding it by default (consistent with the page's variant row).
• player-vs-bot-page.js: #updateOutcomeLabel() now tracks whether a real outcome exists (canceled, win, loss, or draw) and toggles the row visibility. As this runs on game load and every outcome update, the row appears reactively once the game finishes.
• player_vs_player_game.html: Defined the outcome row's hidden default inline via style="display: none", consistent with the player-vs-bot row.
• player-vs-player.css: Removed the now-redundant tr#outcome-row rule, since the hidden default is defined in the template. The existing JS toggle continues to show the row only once an outcome is known.
• changelog.html: Added an entry for this change.

this.#infoOutcomeLabel.innerText = label;
this.#infoOutcomeRow.style.display = hasOutcome ? '' : 'none';

[benckx]

@copilot same for player_vs_player games

[Copilot]

@copilot same for player_vs_player games

Done in 0f5b869's follow-up commit. The pvp outcome row now defines its hidden default inline in player_vs_player_game.html (matching the pvb row) instead of relying on the shared CSS rule; the existing JS already shows it only once an outcome is known.

[benckx]

@copilot should the display none be in the css?

[Copilot]

The player_vs_bot.html page doesn't load a dedicated CSS stylesheet, and it already uses inline style="display: none" for the analogous info-variant-row (line 53) and the actions box (line 68). So keeping it inline here is consistent with the existing page convention. I left it as-is, but happy to introduce a player-vs-bot.css (mirroring player-vs-player.css) and move these rules there if you'd prefer the CSS approach.