[david-debest]

Summary

Closes #72.

knowledge_mapper's package __init__.py attaches its own StreamHandler (with its own formatter) to the knowledge_mapper logger so output looks reasonable without any setup by the host application. It did not, however, set propagate = False.

When a host application also configures the root logger (e.g. via logging.basicConfig(), as seen in the reported KB scripts), every record emitted by a knowledge_mapper.* logger was handled twice:

1. Once by knowledge_mapper's own handler/formatter.
2. Once more after bubbling up to the root logger's handler (with a different, host-configured format) — this is exactly what's shown in the issue's log excerpt, where each line appears twice in two different formats.

Fix

Set propagate = False on the knowledge_mapper logger, so records handled by its own handler stop there and are not forwarded to ancestor loggers (e.g. root). No other behavior changes.

Documented the behavior (and how to opt out, for host apps that want full control) in CONTEXT.md.

Testing

Added tests/test_logging.py:

• Asserts propagate is False on the package logger.
• Simulates a host app that attaches a handler to the root logger, then logs via a knowledge_mapper.* child logger, and asserts the host's root handler never receives the record (i.e. no duplicate emission).

Full test suite and ruff check/ruff format --check pass.