Skip to content

Add reliable Unity operation workflow - #13

Draft
niqibiao wants to merge 1 commit into
codex/command-routing-optimizationfrom
codex/reliability-workflow
Draft

Add reliable Unity operation workflow#13
niqibiao wants to merge 1 commit into
codex/command-routing-optimizationfrom
codex/reliability-workflow

Conversation

@niqibiao

@niqibiao niqibiao commented Jul 24, 2026

Copy link
Copy Markdown
Owner

What changed - add cs doctor, operation diagnosis, and target-aware cs 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: completed reports ready, orphaned or timed-out work reports exit 4 outcome_unknown with do-not-retry remediation, and an unknown UUID reports not_found; wait-ready returned 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_compile and git diff --check This is a stacked PR based on #12 (codex/command-routing-optimization). It requires the package-side branch niqibiao/unity-csharpconsole:codex/at-most-once-protocol; no test, eval, report, or CONTEXT files are included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant