feat(logging): enhance logging output controls and verbosity settings

Author: stefaniuk

.github/prompts/dev.implement-cli-args-parsing.prompt.md

@@ -77,6 +77,7 @@ Use it for context and evaluate each CLI against the CLI Contract Baseline:
 - Support repeatable flags for multiple values and document ordering, de-duplication, and limits.
 - Reject unknown flags and surplus positional arguments with exit code `2`.
 - Follow standard conventions for `-h/--help`, `-v/--version`, `--verbose`, and `--quiet`. These are must-have arguments for every CLI.
+- Support env var equivalents for CLI flags (for example `LOG_FILE` for `--log-file`), with precedence: CLI flags > env vars > config file > defaults.
 - Provide `--yes` or `--no-input` for non-interactive operation and make prompts opt-in.
 
 ### Modern parser defaults 🧱
@@ -124,13 +125,18 @@ Use it for context and evaluate each CLI against the CLI Contract Baseline:
 - Offer `--dry-run` when the command mutates resources.
 - Keep interactive prompts opt-in and always provide a non-interactive equivalent.
 
+### Logging output controls 🧾
+
+- Default to no logging output unless explicitly enabled.
+- Provide options for structured log file (`--log-json-file`), human-readable log file (`--log-file`), console logging (`--log-console`), and pretty/colour console output (`--log-console-pretty`).
+- Console logs must go to stderr and never mix with stdout payloads.
+
 ### Logging verbosity controls 🔊
 
 - `--verbose` raises verbosity one step; allow `-v`, `-vv`, `-vvv` to increment levels (for example INFO → DEBUG → TRACE).
 - `--quiet` lowers verbosity one step; allow `-q`, `-qq` similarly.
 - Document the exact mapping from flags to log levels in `--help`.
 - Provide `--log-level <level>` for explicit control; flags are convenience.
-- Support an environment variable for verbosity (for example `LOG_LEVEL` or `VERBOSITY`), with precedence: CLI flags > env vars > config file > defaults.
 - Keep diagnostics on `stderr` and keep outputs deterministic.
 
 ### Wrappers and shared libraries 📦
@@ -170,12 +176,13 @@ Use it for context and evaluate each CLI against the CLI Contract Baseline:
    - [ ] Validation and errors
    - [ ] Stdout and stderr semantics
    - [ ] Developer ergonomics
+   - [ ] Logging output controls
    - [ ] Logging verbosity controls
    - [ ] Wrappers and shared libraries
    - [ ] Cloud and serverless workloads
    - [ ] Testing expectations
 
 ---
 
-> **Version**: 1.0.2
+> **Version**: 1.0.3
 > **Last Amended**: 2026-02-08

.github/prompts/dev.implement-logging.prompt.md

@@ -74,6 +74,21 @@ Use it for context and evaluate each runtime that emits structured logs against
 - **Timing information**: log duration for slow or critical operations (or emit metrics instead).
 - **Avoid noise**: do not add "started/finished" logs to trivial or idempotent methods.
 
+### Output destinations and defaults 🎯
+
+- **No logs by default**: logging output is disabled unless explicitly enabled by configuration or CLI flags.
+- **Structured log file option**: provide a CLI argument or configuration option for the structured log file name/path (for example `--log-json-file` or `LOG_JSON_FILE`). When set, emit structured logs in NDJSON.
+- **Human-readable log file option**: provide a CLI argument or configuration option for the human-readable log file name/path (for example `--log-file` or `LOG_FILE`). When set, emit human-readable logs.
+- **Console logging toggle**: provide a CLI argument or configuration option to enable logging to the console (for example `--log-console` or `LOG_CONSOLE=true`).
+- **Pretty/colour console toggle**: provide a CLI argument or configuration option for pretty, colourised console output (for example `--log-console-pretty` or `LOG_CONSOLE_PRETTY=true`).
+- **Separate streams**: console logs must go to stderr and never mix with stdout payloads.
+
+### Logging verbosity controls 🔊
+
+- Provide `--log-level <level>` for explicit control.
+- Support verbosity flags (`--verbose` with `-v`, `-vv`, `-vvv`, and `--quiet` with `-q`, `-qq`) and document the mapping in `--help`.
+- Support an environment variable for verbosity (for example `LOG_LEVEL`) with precedence: CLI flags > env vars > config file > defaults.
+
 ### Log levels 🎚️
 
 | Level | Purpose                                   |
@@ -102,6 +117,7 @@ Flag any misuse (e.g., logging an error condition at INFO).
 - **No-colour mode**: auto-disable colour when stdout is not a TTY; honour `NO_COLOR` or similar environment variables.
 - **Level tags and icons**: use short, consistent tags (INFO, WARN, ERROR) with an optional single icon per level.
 - **Bounded output**: truncate or wrap large fields; never allow unbounded blobs to break layout.
+- **Stdout separation**: console logs must never be written to stdout; keep stdout for primary results only.
 
 ### Performance ⚡
 
@@ -120,12 +136,14 @@ Flag any misuse (e.g., logging an error condition at INFO).
    - [ ] Project-level logger configuration
    - [ ] Class-level logging
    - [ ] Method-level logging
+   - [ ] Output destinations and defaults
+   - [ ] Logging verbosity controls
    - [ ] Log levels
    - [ ] Content
    - [ ] Console visualisation
    - [ ] Performance
 
 ---
 
-> **Version**: 1.1.4
+> **Version**: 1.1.5
 > **Last Amended**: 2026-02-08