Characterize new-format webhook handling#10
Draft
camdroid wants to merge 1 commit into
Draft
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
1 participant
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.
Extends the legacy characterization suite (asmbly-makerspace#100) to the new (post 2026-05-09)
Neon webhook format.
Green — current behavior:
OpenPath as a string (id-type divergence from legacy noted inline).
xfail(strict) — target behavior for the unification refactor:
Both fail today (flat enrollType/status aren't recognized, so new joins are
silently dropped) and will XPASS — failing CI — once the refactor routes new
joins through handle_joins, signaling the markers can be removed.
Note: new createMembership uses an ASSUMED shape (no real sample in the logs),
inferred from the new updateMembership shape.