Repository navigation
Bind surgery consent and operations to character sessions - #30
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to Surgery consent offers and operations are now tied to each participant's character session, with cleanup when a session ends. No confirmed defect remains at the current head. One open question remains: whether the shared character library always signals the end of a session when a player disconnects. Confirm this during the planned live server validation.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
An offer or operation now belongs to both participants' exact character sessions. Switching Alice → Bob → Alice, reconnecting, or losing the identity provider cannot reuse old consent, consume tools for an old operation, or complete surgery on a replacement character.
Validation: Java 21
mvn clean verifypassed all 162 tests with 100% coverage of 1,251 executable lines. Restoring the old tool-handler guard reproduced the replacement-state overwrite in the new regression; the fix passes. Runtime JAR metadata and docs checks passed. Independent Astra review found the reentrancy issue, then approved the corrected implementation. Live Paper validation remains part of the full pinned-release lab; nothing has been deployed.Docs: TF-Minecraft/Docs#165