events dashboard baseline: jurisdictions + lib/client refactor + send-loop - #90
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
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.
Summary
setup-c.shaddsUSjurisdiction to the council after creating it;setup-pp.shclaimsUYin the join envelope. The provider view shows both flags merged.e2e/intolib/client/so non-test callers can reuse it. Docker-compose mounts + cp updates fore2e/otel/lifecycle../send-loop.shhelper fires N Alice→Bob privacy-channel bundles through the running PP (default 5, 1s apart) so the events tail in provider-console can be exercised manually.Test plan
./test.sh e2e otel governance lifecycle pos-instant invite-gate playwright— all green against this branch./send-loop.shagainstup.shstack — 5 bundles emit events end-to-end and the provider-console live tail renders them