What's Changed

• docs: record the refilled newcomer backlog by @sepehr-safari in #178
• feat(scenarios): add status-transitions-legal scenario by @YANGCHUNHONG3000 in #180
• feat: added a new test scenario: boot-outside-repeat-window by @michal-skraburski in #179
• chore: version packages by @github-actions[bot] in #181

New Contributors

• @michal-skraburski made their first contribution in #179

Full Changelog: v0.4.7...v0.4.8

Patch Changes

• 15c9837: added a new scenario: boot-outside-repeat-window
• c32cfa7: Add a status-transitions-legal scenario to ensure a fully legal OCPP 1.6 status path reports no failure.

What's Changed

• docs: move the Current Version paragraph to 0.4.6 by @sepehr-safari in #168
• feat(scenarios): add meter-value-zero scenario by @YANGCHUNHONG3000 in #169
• feat(scenarios): add repeated-boot-notification scenario by @MayurK-cmd in #170
• docs: record complete rule coverage and the corpus reaching 21 by @sepehr-safari in #172
• chore: version packages by @github-actions[bot] in #171

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.6...v0.4.7

Patch Changes

• ca2bb0e: Add a meter-value-zero scenario to ensure a flat zero meter register does not report a failure.
• 49bc07e: Add repeated-boot-notification scenario covering the REPEATED_BOOT_NOTIFICATION detection rule. The synthetic trace reboots a station three times in three minutes (one BootNotification per minute) followed by a single Heartbeat, exercising the 5 minute window used by the rule.

What's Changed

• feat(scenarios): add heartbeat-timeout scenario for TIMEOUT_NO_HEARTBEAT by @MayurK-cmd in #161
• docs: bring CURRENT_STATE forward after #161 and fix the stale ID allocation by @sepehr-safari in #165
• chore: version packages by @github-actions[bot] in #162

New Contributors

• @MayurK-cmd made their first contribution in #161

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.5...v0.4.6

Patch Changes

• dc2a77c: Add heartbeat-timeout scenario covering the TIMEOUT_NO_HEARTBEAT detection rule. The synthetic trace boots a station with interval=300, then sends a StatusNotification past the 2× interval threshold (06:12:00.000Z) with no Heartbeat anywhere in the trace.

What's Changed

• docs: bring CURRENT_STATE up to date with 0.4.4 and today's work by @sepehr-safari in #150
• chore(ci): keep CURRENT_STATE current from the release workflow by @sepehr-safari in #152
• docs: record the release log automation in CURRENT_STATE by @sepehr-safari in #153
• fix(core): match FIRMWARE_UPDATE_FAILURE to the OCPP 1.6 status enum by @sepehr-safari in #157
• fix(core): transcribe the section 4.9 status transition table by @sepehr-safari in #158
• fix(core): report every refusing AuthorizationStatus, not just Invalid by @sepehr-safari in #159
• chore: version packages by @github-actions[bot] in #160

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.4...v0.4.5

What's Changed

• docs: bring CURRENT_STATE up to date with 0.4.3 and the scenario corpus work by @sepehr-safari in #146
• docs: require a scenario for every detection rule by @sepehr-safari in #148
• feat(scenarios): add firmware-update-failure scenario by @YANGCHUNHONG3000 in #147
• chore: version packages by @github-actions[bot] in #149

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.3...v0.4.4

Patch Changes

• d1c4382: Report every refusing AuthorizationStatus in FAILED_AUTHORIZATION, not just Invalid (#156). The OCPP 1.6 enumeration (edition 2, section 7.2) has five values and only Accepted permits charging, so Blocked, Expired and ConcurrentTx end a driver's session exactly as Invalid does. The rule fired on Invalid alone, which meant a blocked or expired token produced a clean report, and silence from a detector reads as "this is not the problem". All four refusals now report under the existing code, with the status named in the description, and the suggested steps mention the ConcurrentTx case. Adds a refused-authorization scenario covering the three newly reported statuses, bringing the corpus to 18.
• 8527e9f: Match FIRMWARE_UPDATE_FAILURE to the OCPP 1.6 FirmwareStatus enumeration (#154, edition 2 section 7.25). The rule matched DownloadPaused, InstallFailed and InstallRebootingFailed, none of which are 1.6 status values, and did not match InstallationFailed, which is one of the two failure values the enumeration defines. A conformant station reporting a failed installation, the more consequential of the two firmware outcomes, went undetected. The rule now matches exactly DownloadFailed and InstallationFailed, and the firmware-update-failure scenario reports InstallationFailed instead of the non-spec InstallFailed it used before.
• d687e53: Transcribe the STATUS_TRANSITION_VIOLATION matrix from the OCPP 1.6 status transition table (#155, edition 2 section 4.9). The matrix disagreed with the table in both directions: it flagged 22 transitions the table permits and permitted 2 it does not list. The false positives were concentrated in the recovery rows, where the table allows a connector to return from Faulted to any pre-fault state and from Unavailable straight into an operative state, so any station that faulted mid-session and resumed charging, or that took a scheduled availability change during a session (Charging -> Unavailable and its siblings), produced a spurious warning. Preparing -> Unavailable and Finishing -> Reserved are absent from the table and are now flagged. The rule's matrix is now the table cell by cell, with the spec's own cell labels alongside it, and a test transcribes the table independently so the two have to agree.

Patch Changes

• 8fe2185: feat(scenarios): add firmware-update-failure scenario