logging

Structured logging captures plugin activity in machine-readable JSONL format. Initialize a logger with `createPluginLogger()` at startup, define subsystem loggers for different code paths, and logs automatically write to ~/.<plugin-name>/logs with correlation IDs for tracing operations end-to-end.

JSONL (JSON Lines) logging stores each log entry as a single JSON object per line, making logs machine-readable and easier to parse, filter, and analyze programmatically compared to unstructured text logs.

Correlation IDs are unique identifiers attached to each operation that propagate through all related log entries. This lets you trace a single request or workflow across multiple subsystems and log files to pinpoint where issues occur.

Yes. This Skill supports log rotation and retention settings configured during logger initialization, preventing logs from consuming excessive disk space while maintaining recent entries for debugging.

Yes. @sidequest/core is a required dependency that provides `createPluginLogger()` and `initLogger()` functions to set up structured logging with subsystem support and correlation ID propagation.

Log levels control verbosity and performance impact. Production plugins typically use INFO or WARN to capture important events without excessive overhead, with DEBUG reserved for development and troubleshooting workflows.