From 3974a4686a1e7842246950dba1dd5f6609e5475e Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Wed, 7 Oct 2026 20:29:53 +0000 Subject: [PATCH] Keep future validation behavior in the roadmap --- docs/internal/validation.md | 20 +++++++------------- docs/roadmap/remediation.md | 7 ++++++- 2 files changed, 13 insertions(+), 14 deletions(-) diff --git a/docs/internal/validation.md b/docs/internal/validation.md index f73c6c7..e57c9d0 100644 --- a/docs/internal/validation.md +++ b/docs/internal/validation.md @@ -62,15 +62,11 @@ Do not add a public validator registration interface. The public specification selects ReleaseKit-owned checks; `AdditionalChecks` remains the extension point for product behavior. -## Prospective Go command recipe +## Go command environment reuse -The complete planned procedure uses one test invocation. Race selection -modifies that command. When a separate full vet pass is selected, run tests with -vet disabled and then run native `go vet`. Selected package-compilation targets -run after test and vet with the static Go environment, including -`CGO_ENABLED=0`. Keep these compatibility checks independent of executable -artifact declarations. These selections become operational as their checkers -are implemented. +The current executor uses the [shared Go command environment](gotool.md) for +its offline suite. The [roadmap coordination design](../roadmap/implementation.md#execution-and-ownership) +owns the proposed test, vet, and package-compilation procedure. Reuse `internal/gotool` for native and static environments and target handling. Keep toolchain and module-cache discovery in `gotool`; do not reproduce its @@ -91,8 +87,6 @@ symlink expansion detects cycles, and traversal honors cancellation. Absolute destinations and symlink targets within the repository directory map back to candidate-relative paths; existence still comes from committed entries. -The Markdown capability will use PromptKit's current parser and anchor -conventions as its starting evidence. Supported link syntax, anchors, -diagnostics, and boundary policy belong to that feature's roadmap and -implementation prompt. This foundation provides only the committed-file and -destination-resolution primitives. +The [Markdown roadmap](../roadmap/v0.2.0.md#8-offer-offline-markdown-link-validation) +owns proposed link syntax, anchors, diagnostics, and boundary policy. This +foundation provides committed-file and destination-resolution primitives. diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index 9b380e8..59e48f0 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -1,6 +1,6 @@ # Shared validation foundation remediation -Status: Remediation in progress; findings 1–5 addressed, finding 6 pending. +Status: All six findings addressed. Reviewed committed implementation `f53354b`, covering the eight foundation commits after `0c7129a`, against the [implementation plan](implementation.md), @@ -211,6 +211,11 @@ committed entries for existence; neighboring files remain irrelevant. ## 6. P3: Future Go command behavior appears in implemented internal documentation +**Resolution:** Addressed. The internal guide describes current environment +reuse and links to the roadmap for proposed command coordination and Markdown +behavior. Its implemented executor, candidate-file mechanics, and checker +integration guidance remain in place. Local links and fragments were checked. + **Owner:** [shared validation guide](../internal/validation.md), `Prospective Go command recipe`.