Harden DSM WNN telemetry enforcement and close rollback edge-case faults#24
Merged
Conversation
Agent-Logs-Url: https://github.com/dfeen87/HLV-RAPS/sessions/5cc1e5af-f700-41a0-b6a3-5ecf30bece8e Co-authored-by: dfeen87 <158860247+dfeen87@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dfeen87/HLV-RAPS/sessions/5cc1e5af-f700-41a0-b6a3-5ecf30bece8e Co-authored-by: dfeen87 <158860247+dfeen87@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dfeen87/HLV-RAPS/sessions/5cc1e5af-f700-41a0-b6a3-5ecf30bece8e Co-authored-by: dfeen87 <158860247+dfeen87@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
dfeen87
May 7, 2026 11:48
View session
There was a problem hiding this comment.
Pull request overview
This PR hardens the DSM WNN telemetry enforcement and the WNN-triggered rollback path to fail safely on malformed telemetry and rollback-store edge cases, while preserving auditable ITL logging.
Changes:
- Added explicit non-finite (
NaN/Inf) detection for WNN telemetry and unified safing behavior for invalid inputs vs threshold breaches. - Sanitized non-finite WNN telemetry before ITL logging using a named sentinel value.
- Guarded WNN rollback execution against
nullptrrollback stores and zero rollback counts, with SIL regression tests covering both cases.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/sil/test_rollback_execution.cpp | Adds SIL regression tests for trigger_wnn_immediate_rollback when rollback storage is nullptr or empty. |
| src/raps/rollback_execution.hpp | Adds a nullptr guard to prevent unsafe dereference in WNN-triggered rollback execution. |
| include/raps/safety/deterministic_safety_monitor.hpp | Adds WNN telemetry validity checks, threshold helper, ITL logging sanitization, and clearer DSM diagnostics for WNN rollback safing. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WNN telemetry enforcement in the DSM could accept invalid numeric inputs and had brittle rollback-path assumptions. This update hardens the WNN-to-DSM safing path so malformed telemetry and rollback-store edge cases fail safe and remain auditable.
WNN telemetry validation and safing behavior
NaN/Inf) detection forWnnTelemetryfields before threshold evaluation.ITL logging hardening for invalid telemetry
DSM_Config::INVALID_TELEMETRY_SENTINEL) to avoid ambiguous raw invalid values in the log stream.Rollback-path safety guards
trigger_wnn_immediate_rollback(...)to return safely when rollback storage is unavailable (nullptr) or empty (rollback_count == 0), avoiding unsafe dereference assumptions in WNN-triggered rollback flow.SIL coverage for regression boundaries