tracy-debugginglisted

## Tracy Debugging Tracy is enabled automatically in debug mode. In debug mode, Tracy displays errors in the browser; in production mode, errors are logged to the `log/` directory and the user sees a generic error page. **Requires Tracy ≥ 2.12** for the markdown-to-console output described below. With older versions, only the visual HTML BlueScreen and Tracy Bar are available — you will need to scrape HTML instead. ### Enabling Debug Mode Debug mode is controlled in `app/Bootstrap.php`: ```php // Auto-detect: debug on localhost, production elsewhere $this->configurator->setDebugMode('secret@23.75.345.200'); // Force debug mode (development only!) $this->configurator->setDebugMode(true); // Enable Tracy with log directory $this->configurator->enableTracy($this->rootDir . '/log'); ``` In production, Tracy logs exceptions to `log/exception-*.html` files (full BlueScreen snapshots) and errors to `log/error.log`. Tracy ≥ 2.12 additionally writes a `.md` sibling next to every `.html` exception — see [Batch reading production exceptions](#batch-reading-production-exceptions) below. ### How Tracy detects an agent The markdown-to-console output is **conditional** — it activates only when Tracy thinks an AI/automation agent is reading the page. Detection works in two stages: 1. **JavaScript stage.** The Tracy Bar's own JavaScript checks `navigator.webdriver`. When `true` (which Chrome and Firefox set automatically under WebDriver, Chrome DevTools Protocol, Playwright, Puppet