Harden Eclipse runtime proof initialization#43
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.
Summary
progressreceipts to one client log line per configs/progress batch while keepingconfigs receivedvisible.1.3.16.AGENTS.mdagent-guide commit in this branch.Runtime proof receipts
Preserved locally, not staged as source:
.codex\runs\20260517-202509\vshare-eclipse-runtime-proof.codex\runs\bepinex-plugin-set\vshare-eclipse-bloodcraft-runtime-proof\client\20260517-202445The proof receipts showed the client received and accepted the VShare offer, downloaded
Eclipse.dll, hotloaded Eclipse, registered the Emberglass bridge, received configs/progress, sent Eclipse registration, and had zero Eclipse exceptions. Server receipts showed the shared-mod request, transfer offer/accept, transfer dispatch complete, and Bloodcraft receiving Eclipse registration.Known non-blocker remains unchanged:
TargetInfoPanel(Clone) ... not a descendantcan still appear while Eclipse UI initialization succeeds.Verification
git diff --checkdotnet restore Eclipse.csprojdotnet build Eclipse.csproj --configuration Release -p:DeployToClient=false --no-restore