Repository navigation
fix: redact malformed registration acknowledgment diagnostics - #146
Merged
RobLe3 merged 1 commit intoNov 5, 2026
Merged
Conversation
5 tasks done
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.
Correction
Replace arbitrary response-body rendering in the missing registration token exception with a fixed message. Successful registration, existing credential retention and SDK-specific primary/alias selection are unchanged.
Closes #145. Related historical Rust correction: RobLe3/iicp-client-rust#185.
Validation
b23f10d2c476317e266b1cd9f0dca69e037b5306(review SHA-256e2483bac7d3f057356c7d1620eabf4e91eaace2567af85207bc1325a625c80b0). Required hosted CI remains a separate merge gate.Boundaries
Synthetic fixtures only; no private captures. No workflow, dependency, version, qualification ledger, candidate or certificate changes. This is a development correction, not successor qualification or package publication. Local development skips are not qualification waivers. Architecture-rule checking is unavailable because neither SDK defines Sentrux rules; no replacement rules were introduced.