engine-behavior-reporting

What problem does it solve?

It helps keep Citum’s engine behavior coverage report synchronized with the actual integration tests, so reviewers can trust what’s covered and understand what changed without reading all the Rust code.

Core Features & Use Cases

• Scenario-to-report alignment: convert crates/citum-engine/tests/*.rs integration suites into behavior-oriented scenarios while keeping the published report in sync.
• Human-first summaries: refine announce_behavior(...) descriptions so the report communicates observable behavior rather than implementation details.
• Controlled publication workflow: regenerate the Markdown/HTML behavior report via the existing reporting pipeline without inflating normal PR CI time.
• Traceable source references: ensure the report emits concise, repo-relative references like crates/citum-engine/tests/foo.rs:120-128 for auditing.

Quick Start

Use the engine-behavior-reporting skill to convert an added citum-engine integration test suite into readable behavior scenarios and regenerate the corresponding published behavior report.