FleekDash front-end code does not rely on scattered raw console.* calls. Release 2.6.1 makes client-side debug logging a first-class developer workflow: one module, consistent prefixes, and controls so instrumentation stays useful in DevTools without drowning everyday users.
This is engineering telemetry inside the browser, separate from the Unified Error surface and Send Report flows. Those paths stay focused on customer-visible failures and one-shot reports. debugLog, debugInfo, debugWarn, and debugError from @/utils/debug are what you use while building, integrating, or triaging behavior in a technical session.
What's New
Canonical helpers: import debugLog, debugInfo, debugWarn, and debugError from @/utils/debug instead of sprinkling console.log across features. Each call takes a category string (for example MAIN, API, AUTH, SETTINGS) so output is grep-friendly and easy to filter in DevTools.
Structured console shape: messages render with clear prefixes such as [DEBUG:API] or [ERROR:AUTH], plus optional structured context objects for faster diagnosis.
Intelligent debugger core: configuration covers a global enable flag, log level (from verbose debug through error), per-category rate limits so hot paths cannot spam the console, and optional logic that eases noise when DevTools is open.
Production-sensible defaults: in typical production bundles, verbose categorized logging stays off unless you run development builds or intentionally enable deeper debugging. debugError paths still favor surfacing real failures over silent drops.
Project categories: follow shared conventions such as MAIN, API, AUTH, ANALYTICS, DASHBOARD, WIDGETS, SETTINGS, INTEGRATIONS so support can say “filter API” and everyone means the same thing.
Clear boundary vs user tooling: categorized debug* logging complements, and does not replace, Unified Error, Send Report, or ?debug / window.debugReact style production diagnostics when you need broader bundles of browser tooling.
What's Improved
Onboarding for contributors: new code can align with ESLint and logging standards by default instead of fighting ad hoc console usage.
Safer operational hygiene: messages stay in English, categories stay short, and secrets stay out of logs by design.
