eric/ReleaseKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Complete shared validation foundation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 18:41:29 +00:00
parent 89c5b2c1fd
commit f53354be5f
4 changed files with 39 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/roadmap/implementation.md
View File

@@ -1,6 +1,7 @@
# Validation model implementation plan
Status: In progress; shared execution, candidate inspection, facade diagnostics, and CLI mapping are complete.
Status: Foundation complete; individual v0.2.0 validation capabilities and
their settings remain future work.
This plan implements the enabling work in [model.md](model.md), guided by
[ADR 0003](../adr/0003-declarative-validation.md). It is written for a Luna
@@ -545,6 +546,11 @@ outside this implementation plan.
## Stage 8: Verify and document the completed foundation
**Completion:** Complete. `Check` and `Publish` now use one shared conversion
from the facade request into candidate validation. The full Go suite and public
API/dependency check pass, and the roadmap distinguishes the completed
foundation from the optional capabilities still to come.
**Outcome:** The enabling refactor is complete, its current boundary is clear,
and later feature implementation can proceed through the shared model.

20
docs/roadmap/model.md
View File

@@ -1,7 +1,7 @@
# Validation API and profile model
Status: Agreed direction for v0.2.0; the staged plan records the API design
and agreed incremental rollout.
Status: Shared validation foundation implemented; optional v0.2.0 capabilities
and their public/profile settings remain future work.
This roadmap describes the shared model that enables the optional validation
capabilities in the [v0.2.0 roadmap](v0.2.0.md). It owns their common API,
@@ -124,11 +124,17 @@ failure-stopping behavior of the candidate workflow.
## Implementation
The [implementation plan](implementation.md) defines the enabling sequence,
proposed declarations and diagnostics, inspection primitives, verification,
and documentation work. Individual capabilities supply their behavioral
coverage as they are implemented. The target state above describes the complete
model across those capabilities.
The [implementation plan](implementation.md) records the completed foundation:
shared execution, internal diagnostics, captured candidate-tree inspection and
destination resolution, facade diagnostics, and consistent CLI presentation.
The public `ReleaseRequest.Validation` field and profile `validation` object are
not yet available; each setting will be introduced with its first working
capability. Individual checkers, module-selected CI tooling, and the publication
endpoint expectation remain future work in the [v0.2.0 roadmap](v0.2.0.md).
The target state above describes the complete model across those capabilities.
Foundation completion establishes their shared owners and conversion boundaries,
but does not mean the optional checks are implemented or that v0.2.0 is complete.
## Adoption evidence