feat(logging): implement structured JSON logging with pino and multi-module context

[Bilalishaq7]

…dule context, and redactions

Closes #110

Summary

Upgraded the logging infrastructure from standard text-based console outputs to highly efficient, structured JSON telemetry using pino. This establishes a robust, production-grade observability foundation that makes log data easily parseable and searchable while maintaining high execution performance.

Changes

• Centralized Logger Engine (src/utils/logger.ts): Built the core configuration utilizing pino for production JSON outputs and pino-pretty for clean local development console logs, controlled dynamically via NODE_ENV.
• Security Redaction Filters: Configured automated path-based redactions for security-critical keys (*.token, *.secret, *.apiKey, *.password) to prevent credential leakage in log aggregation systems.
• Dynamic Agent Contexts (src/agents/base/BaseAgent.ts): Retrofitted the abstract base class with a protected child logger. All specialized sub-agents now automatically inherit and attach runtime metadata (module, agentClass, agentId, capability) to every log line without code duplication.
• Workflow Traceability (src/coordinator/index.ts & src/index.ts): Injected context-scoped child loggers into the core application server entry point and the deterministic DAG task decomposition engine to cleanly map task allocations.

Testing

• Verified end-to-end type safety and configuration constraints with a clean TypeScript compilation output via npm run build.

Related Issue

Fixes the lack of structured observability and production-ready trace formats in the backend architecture.

Checklist

• Tests pass
• Lint is clean
• Documentation updated if needed

[vercel]

@Bilalishaq7 is attempting to deploy a commit to the Jaja's projects Team on Vercel.

A member of the Team first needs to authorize it.

[devJaja]

Nice Implementation @Bilalishaq7
Resolve the conflicts

[Bilalishaq7]

Nice Implementation @Bilalishaq7 Resolve the conflicts

Thanks @devJaja! The backend CI checks are all green, but the Vercel check is waiting on team authorization since this PR is submitted from an external fork. Whenever you get a chance to authorize the Vercel build or merge, it's all ready on my end!

[devJaja]

@Bilalishaq7 Resolve the conflicts

[devJaja]

Nice Implementation @Bilalishaq7 Resolve the conflicts

Thanks @devJaja! The backend CI checks are all green, but the Vercel check is waiting on team authorization since this PR is submitted from an external fork. Whenever you get a chance to authorize the Vercel build or merge, it's all ready on my end!

I'm aware, I mean your should resolve the conflicts on your branch