Repository navigation
feat: add redacted cleanup notification context and warning status - #12
Merged
Merged
Conversation
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.
Cleanup notifications now support success, failure and cleanup-only warning with a complete bounded input snapshot. All 14 input names are present when a snapshot is provided; the four authentication values must literally equal
[REDACTED]. Optional validation/truncation flags, protected/blocked counts and safe issues extend the existing event. Build/Deploy status semantics and ccv2-client remain unchanged.Validation: full
pnpm qualitypassed 312 tests in nine files; notification-contract coverage is 100% statements/functions/lines and 99.3% branches. Packed public ESM/schema/declaration/export checks, public scan and full audit passed. The exact PR head and merged main passed CI, all three platform jobs and CodeQL. Main analysis 2169530355 has empty error/warning fields and no open CodeQL alerts.Merged main:
7cc2e8e6af46e7438064cc6205b22f4f7154eb94.Registry version 0.0.5 was independently read back. Its SHA256 is
9c3b9910dc51be697c3aa4e44620c3cd87d3cdd132f9a5431e85f9cb5f712dec; integrity issha512-SMcyyWaeHdtlztt99xtWlJycSAspSTGvCaWJH7M2+u+on77JHwo8boTBOc9UUC0BQHDPo/VHmOj4gpt/XIbqmw==. These match the source-candidate artifact tested before publication; the packaged README records that earlier candidate stage. Consumers must now pin the actual published 0.0.5 and rebuild their normal bundles before adopting cleanup warning events.No new package, duplicated OAuth/transport, provider delivery, deployment, provider send, or real SAP operation. Production cleanup remains blocked by unresolved SAP eligibility evidence and separate owner authorization.
Companions: Notify #18, cleanup #7.