debug

To debug software issues, you investigate logs, database state, and git history without modifying files. This approach diagnoses problems encountered during manual testing or implementation by inspecting runtime state and recent code changes.

The best way to troubleshoot is inspecting daemon and WUI logs for errors while querying the SQLite database for session and event information. This read-only investigation pinpoints causes of unexpected errors during testing without altering files.

Yes, this troubleshooting method works with SQLite and git command-line tools. It requires access to log files, SQLite databases, and git command-line tools to perform state inspection and diagnose issues during implementation phases.

Yes, you can diagnose errors during manual testing without modifying files. The process examines current git branches, recent commits, and uncommitted changes alongside logs and database state to understand issues without consuming primary context.

Examining git history and uncommitted changes when debugging helps correlate recent code modifications with runtime errors. Reviewing current branches and recent commits alongside logs and database state isolates the root cause of unexpected behavior.

A limitation of debugging through log and database inspection is its read-only scope; it diagnoses issues without modifying files or executing fixes. It is constrained to analyzing existing SQLite databases, daemon logs, and git state.