Run validation in the selected module
This commit is contained in:
@@ -371,6 +371,18 @@ suite and reused discovery in an unchanged validation/build operation; changing
|
||||
environment inputs through an additional callback triggers fresh settings.
|
||||
Run Go-tool, validation, and candidate coordination tests.
|
||||
|
||||
**Completed:** Go validation commands now run from the captured module
|
||||
directory. Candidate checks and publication share a lazy operation-local Go
|
||||
settings owner with their later build callbacks; standalone and managed delivery
|
||||
builds acquire separate owners. The owner reuses discovery while the inherited
|
||||
environment and selected `GOENV` file stay unchanged, and refreshes after
|
||||
consumer callbacks when either changes. Nested-module fixtures now include
|
||||
packages for selected-module validation. Verified one suite and shared discovery
|
||||
through candidate build coordination, environment and persistent-file refresh,
|
||||
nested-suite failure and sibling isolation, selected vet/compile command
|
||||
directories and compile baseline, `go test ./...`, and
|
||||
`go run ./internal/apicheck`.
|
||||
|
||||
## Stage 7: Build the selected module and bind output evidence
|
||||
|
||||
**Outcome:** Standalone and composite builds use the correct declaration source,
|
||||
|
||||
Reference in New Issue
Block a user