feat(group-chat): add mixed-runtime participants - #2226
Open
wtj-0527 wants to merge 34 commits into
Open
Conversation
wtj-0527
force-pushed
the
feat/group-chat-mixed-runtime-participants
branch
from
July 26, 2026 04:31
7093869 to
5dd15d5
Compare
added 17 commits
July 27, 2026 18:37
wtj-0527
force-pushed
the
feat/group-chat-mixed-runtime-participants
branch
from
July 27, 2026 10:39
f202e73 to
2a243f8
Compare
added 7 commits
July 28, 2026 09:54
# Conflicts: # packages/server/src/controllers/auth.ts
wtj-0527
marked this pull request as ready for review
July 29, 2026 13:01
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.
Summary
This Draft PR adds mixed-runtime Hermes Studio Group Chat participants while preserving participant identity, runtime isolation, fixed-chain request provenance, and fail-closed lifecycle behavior.
Runtime and identity
chain_requestdata while keeping predecessor output as separate untrusted context.Lifecycle hardening
token + roomId + actorId + kind='participant'inside the destructive transaction and rolls back when exactly one fence is not consumed.finallyblocks even when runtime finalizers fail.Exact candidate identity
76efd3e5a0db496b07600b3b11b4f1b14daf4e118455627d974f92ddc1e047afb33a94572b895be4bf6af797710d65d98e4d41732d60ffcfb744dbd70770d33da5552838325e5908Local verification
All commands below were run against the exact candidate bytes before push:
tsc --noEmit): PASSvue-tsc -b): PASSnpm run harness:check): PASSnpm run build): PASSgit diff --check: PASSThe broad repository suite has a known non-green baseline and is not represented here as green. The focused candidate gates above are the authoritative local evidence.
Current delivery state
76efd3e5a0db496b07600b3b11b4f1b14daf4e11; checks from earlier heads are superseded.