…oss all modules

why: Structured `extra` keys (tmux_session, tmux_window, tmux_pane,
tmux_config_path) enable filtering, aggregation, and test assertions
on log records rather than string matching.
what:
- Add structured DEBUG/INFO/WARNING/ERROR log calls to workspace, CLI,
  and utility modules with appropriate extra keys
- Route all raw print() calls through tmuxp_echo() in CLI commands
- Fix get_pane() exception catch type to match sibling methods
- Change before_script failure log from DEBUG to ERROR
- Remove catch-log-reraise in plugin version check

why: Verify structured extra keys on log records using caplog.records,
per AGENTS.md guidelines — assert on attributes, not string matching.
what:
- Add caplog tests for builder, freezer, finders, loader, validation,
  importers, and plugin version_check
- Add log-level filtering test for --log-file
- Add ANSI-free assertions to JSON/NDJSON output tests (ls, search)
- Add non-TTY stderr ANSI-free test for load command

why: colorama wraps fixed ANSI escape string constants the stdlib can
provide directly. Removing it shrinks the dependency tree.
what:
- Replace all colorama Fore/Style references in log.py with raw ANSI
  escapes via _ansi_colors from tmuxp._internal.colors
- Remove colorama and types-colorama from pyproject.toml

….format_rule

why: ls and debug-info bypassed OutputFormatter with raw sys.stdout.write,
breaking the 2-channel output architecture for machine-readable output.
what:
- Add OutputFormatter.emit_object() for single top-level JSON objects
- Route ls --json/--ndjson and debug-info --json through emit_object()
- Add Colors.format_rule() for Unicode box-drawing horizontal rules
- Add unit tests for emit_object in JSON, NDJSON, and HUMAN modes

why: Developers need guidance on the 2-channel output architecture
(logger for diagnostics, tmuxp_echo/OutputFormatter for user output).
what:
- Add "Output channels" section with diagnostics vs user-facing rules
- Document print() prohibition in command/business logic
- Expand "Avoid" entry for print() with structured extra guidance

why: logger.exception() dumps tracebacks at ERROR level (visible at
default WARNING) alongside tmuxp_echo() user-friendly messages, causing
users to see double output.
what:
- Change plugin load failed from exception to debug with exc_info
- Change plugin import failed from exception to debug with exc_info
- Change workspace build failed from exception to debug with exc_info

why: The structured logging migration removed the user-visible [Loading]
message that shows which workspace file is being loaded.
what:
- Add tmuxp_echo with [Loading] and privacy-masked workspace path
- Uses PrivatePath (already imported) and cli_colors (already available)

why: Inlining tmux stdout in the log message string defeats structured
log aggregation and filtering.
what:
- Move display-message output from format arg to extra tmux_stdout key

why: All functions must have working doctests per project conventions.
what:
- Add Examples section with string and integer pass-through tests

why: The bare error message loses the script path, making it harder to
diagnose which before_script failed in structured log systems.
what:
- Add tmux_config_path extra with the before_script path to error log

why: The assertion checked for "Loading" or "Loaded" but the restored
user-facing message now uses "[Loading]" format.
what:
- Update assertion to match the restored [Loading] message format