Logging

There is no server to tail. PHP runs inside the app, so a log line has to leave
the WebView to be useful. NativeBlade::log() and every PHP warning or error
go to three places:

NativeBlade::log('Exporting stats', ['user' => auth()->id()]);
NativeBlade::log('Retrying', ['attempt' => 3], 'warn');
NativeBlade::log('Payment failed', ['error' => $e->getMessage()], 'error');

Each entry is one line: timestamp, level, message and the context as JSON.
PHP errors appear with the php:error tag. The file is rotated at 1 MB; the
previous file is kept as nativeblade.log.1.

Reading the log

php artisan nativeblade:logs                       # desktop app on this machine
php artisan nativeblade:logs --platform=android    # phone or emulator over adb
php artisan nativeblade:logs --lines=500
php artisan nativeblade:logs --path                # only print the location

The file is written through the fs plugin, which needs $APPLOG in the
fs:scope of src-tauri/capabilities/default.json. New apps have it; an app
created earlier gets it the next time nativeblade:config runs (nativeblade:dev
and nativeblade:build run it). When the write is refused the WebView console
says so once and the other destinations keep working.

Desktop: the file lives in the OS log directory for the app identifier
(~/Library/Logs/<identifier>/ on macOS, %LOCALAPPDATA%\<identifier>\logs\
on Windows, ~/.local/share/<identifier>/logs/ on Linux).

Android: read through adb shell run-as, which only works for debuggable
builds, so the dev client or a debug APK. A store build keeps its files
private.

iOS: the sandbox has no adb equivalent. Download the app container from Xcode
(Devices and Simulators) and open Library/Logs/nativeblade.log. During
development the dev server terminal already shows every entry.

Development mode

While the app is served by nativeblade:dev (on the desktop or through the dev
client on a phone), errors also appear on screen in a red banner at the top of
the app, with a Dismiss button. A store build never shows the banner; the same
entries still go to the log file. NativeBlade::isDev() tells PHP which mode
it is in. APP_DEBUG is not a substitute: the runtime forces it on inside the
app so exceptions always render.

The banner shows every NativeBlade::log(..., 'error') call, every PHP warning
or fatal, and the problems the shell detects on its own: