🧹 [code health improvement] Use proper logging for Undo/Redo failures

[google-labs-jules]

🎯 What: Replaced raw console.warn statements with GlobalOutputChannel?.appendLine for 'No entry found' failures in the undo and redo handlers within src/databaseModel.ts.
💡 Why: Using the proper extension logging channel rather than console.warn improves code health by ensuring consistent logging practices, making logs visible to users without requiring the developer tools, and avoiding cluttering the debug console.
✅ Verification: Verified the code changes by successfully running npm run test -- tests/unit/databaseModel.test.ts to ensure no tests were broken.
✨ Result: Undo and redo tracker failures are now correctly logged into the standard VS Code 'SQLite Explorer' output channel, maintaining behavior while adhering to the proper logging mechanism.

---

PR created automatically by Jules for task 14447991930474313493 started by @zknpr

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sq-lite-explorer	Ready	Preview, Comment	Jun 8, 2026 12:23pm