Separate Unity resolution from operability
This commit is contained in:
parent
53e5246896
commit
b2edd1f276
6 changed files with 33 additions and 19 deletions
|
|
@ -1487,3 +1487,12 @@ The Rider bridge called a discovered executable path, solution file, and Git
|
|||
branch `ready` without executing or validating any of them. These projections
|
||||
now report `discovered`, `found`, and `gitDetected`. Discovery owns topology;
|
||||
only an actual launch receipt may later claim operability.
|
||||
|
||||
## Editor resolution is not editor operability
|
||||
|
||||
Unity inspection called a parsed project version and an existing exact-editor
|
||||
path `ready`; its smoke proved that state with a fake text file named as the
|
||||
editor executable. The project version is now `pinned`, the editor path is
|
||||
`resolved`, and editor-bridge package existence is explicitly `present`.
|
||||
Commands may use resolution to choose what to execute, but only `runStatus`
|
||||
records planned, completed, failed, or blocked execution consequence.
|
||||
|
|
|
|||
|
|
@ -568,3 +568,8 @@ binary tests, and the all-bin check pass.
|
|||
Rider bridge topology no longer claims readiness from path existence. Rider is
|
||||
`discovered`, solutions are `found`, and repository topology is `gitDetected`;
|
||||
the native bridge smoke passes with the renamed evidence states.
|
||||
|
||||
Unity bridge uses the same boundary: project version parsing is `pinned`, exact
|
||||
editor path discovery is `resolved`, and the editor package predicate is named
|
||||
`present`. Operability belongs to the subsequent `runStatus` receipt. The
|
||||
native Unity bridge smoke, 259 library tests, and all-bin check pass.
|
||||
|
|
|
|||
Reference in a new issue