#504 examples/plugin-audit-sink: prove the sink fires through the real emit_to_sinks() path

[Anonymous]

Originally created by: fu351

The tutorial's tests (examples/plugin-audit-sink/tests/test_example_sink.py) call sink.emit(...) directly, so a wiring break in core's fan-out (src/doberman/storage/sinks.py::emit_to_sinks, ~lines 394-421) would not be caught. Add one test that registers an ExampleAuditSink the way core would after discovery and routes a record through emit_to_sinks(), asserting one JSON line lands in the sink file. The guardrail tutorial has the equivalent, test_plugin_fires_inside_objective_guardrail in examples/plugin-guardrail/tests/test_example_rule.py. Do not install the package in the core suite; [#501] shows the sys.path pattern.

[Anonymous]

Originally posted by: hugosmoreira

Hi, I'd like to claim this issue. I'll add a focused test that registers ExampleAuditSink through the same discovery path used by core, routes a record through emit_to_sinks(), and verifies that exactly one unchanged JSON line is written. I'll run the example tests and the repository's complete Windows-compatible verification gates before opening a PR.

[Anonymous]

Originally posted by: hugosmoreira

I'm stepping back from this issue so it is available for someone else. My current contribution focus is Windows-specific bugs, and I won't be opening a PR for this item. Thanks for the opportunity, and apologies for the change of plans.