MONITORING UPDATE - existing TradingLab deployment

No SQL import, database reset, configuration change, or terminal commands.

1. Temporarily disable the TradingLab cron in your hosting panel so it cannot read a partially uploaded set of PHP files.
2. Extract this package into the existing TradingLab folder, overwriting the included files and retaining the lib/ and assets/ directories.
3. Re-enable the same cron and refresh runner.php. Monitoring records appear after the next worker cycle.

Included files: bootstrap.php, view.php, assets/app.js, lib/Engine.php, lib/Report.php, lib/Monitor.php.

This exact monitoring-only upgrade accepts the immediately preceding corrected Store.php release while preserving its experiment, balances and trading settings. Other code or settings differences still block new entries and appear as a warning. Do not reset your database to clear such a warning.

The account count is now read from the actual database. Scanner state, market regime and breadth, clock offset, candidate coverage, scan blockers, signal values and thresholds, pending orders and execution outcomes are visible on both pages. Position-check timestamps are visible on Overview.

Decision counts measure evaluations since this update, not unique trades. The live dashboard retains up to 100 recent decisions per market and displays the newest 100 combined. Full new decision records are also saved in the compressed market audit files. Historical skipped signals cannot be reconstructed from this update. Old order evidence remains available when previously recorded.

Validated with 41 PHP checks (including 1800 signal-explanation comparisons), PHP/JavaScript syntax checks, and a dashboard rendering smoke test. VPS operation and browser layout require confirmation after upload.
