Separate Rider discovery from readiness
This commit is contained in:
parent
7d691e2247
commit
53e5246896
6 changed files with 19 additions and 8 deletions
|
|
@ -1480,3 +1480,10 @@ only for a matching completed receipt, `attention` for an inconsistent pair,
|
|||
when neither exists. The operator snapshot readback likewise reports `loaded`,
|
||||
not `ready`, when a snapshot is merely present. Cache lookup owns retrieval;
|
||||
the joined lifecycle evidence owns lifecycle status.
|
||||
|
||||
## Tool discovery is not operational readiness
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -564,3 +564,7 @@ an older latest completion. Its statuses are lifecycle facts (`missing`,
|
|||
Negative unit coverage proves intent presence is only requested and mismatched
|
||||
receipt identity cannot close it. Both native smokes, 259 library tests, focused
|
||||
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.
|
||||
|
|
|
|||
Reference in a new issue