You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The node registration missing-token failure renders the complete successful HTTP response body into an exception. Arbitrary acknowledgment fields can therefore enter caller diagnostics. Synthetic-only regression controls reproduce this on current development source and the original qualified source. No actual private payload is included here.
Narrow correction
Use a fixed missing-token message without changing credential selection, rejection, existing-token retention or successful registration. Add positive and negative regression controls. Related historical correction: RobLe3/iicp-client-rust#185. Existing stabilization owner: #119.
Acceptance
Original failure reproduced with synthetic markers.
Response contents excluded from missing-token exception text.
Existing primary/alias behavior and prior credential retained.
Focused regressions, component checks, independent exact-head review and required CI pass.
Development correction merged with exact revision recorded.
Qualification boundary
This is a development correction, not a replacement qualification result. Original candidate, receipts and certificates remain unchanged. Required successor qualification stays under existing root governance; no old credit is carried forward automatically. No package publication or workload execution is part of this issue.
Verified development disposition, 5 November 2026
Merged through #146 at 6504a6001003cf3a95c16614101da94fe8adcb50. Exact reviewed and merged Git trees match. Required SDK quality CI passed at reviewed head b23f10d2c476317e266b1cd9f0dca69e037b5306. Original qualified candidate and accepted receipts remain unchanged; successor qualification remains outstanding.
Activity