Add reliable Unity operation workflow - #13
Draft
niqibiao 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
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.
What changed - add
cs doctor, operation diagnosis, and target-awarecs wait-ready- protect mutating CLI requests with exact-byte invocation bindings and a strict machine-local outbox - make ambiguous responses return a recovery ID instead of creating a second dispatch - bind refresh waits to the accepted operation id and generation, including safe resume after timeout - auto-detect the Editor port from the durable Library refresh state with legacy fallback - keep compact diagnostic output focused while preserving full evidence behind--verbose## Why A transport timeout can occur after Unity has begun a mutation. The previous client could not reliably distinguish that case from a request that never started, and readiness polling could accept stale or wrong-project state after reload. ## Impact Uncertain operations fail closed and remain diagnosable, refresh readiness is tied to the exact accepted lifecycle, and long polling workflows avoid repeatedly carrying bulky health evidence. This reduces duplicate side effects as well as token and context growth in composed workflows. ## Validation - local uncommitted CLI suite: 50/51 on the final stacked head; only PR #12's existing command-reference context-budget assertion fails, while reliability tests pass; test/eval files remain uncommitted - Unity 2022 live validation: automatic 14501 discovery, full/targeted refresh, bound wait resume, malformed refresh rejection without state mutation, Play Mode exit/resume, and uncertain-command recovery - final operation diagnosis matrix:completedreports ready, orphaned or timed-out work reports exit 4outcome_unknownwith do-not-retry remediation, and an unknown UUID reportsnot_found;wait-readyreturned immediately only for the matching ready target - exact-byte live fault matrix covered concurrent same-ID execution, replay, conflict, client timeout, server outcome-unknown, journal failure, service-epoch orphan recovery, and protection expiry without creating a replacement operation inside the protection window -py_compileandgit diff --checkThis is a stacked PR based on #12 (codex/command-routing-optimization). It requires the package-side branchniqibiao/unity-csharpconsole:codex/at-most-once-protocol; no test, eval, report, or CONTEXT files are included.