The ewk epic's acceptance criteria (and archie-core-cbk's, by inheritance) require: "Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output." That identifier does not exist. internal/infrastructure/configuration/validate.go defines only an unexported validate(cfg *config.Config) error, called from one place: loader.go:178 inside Loader.Load's own decode-then-validate sequence. There is no way for code outside the configuration package -- e.g. archied setup after it builds a config.Config in memory but before writing it to disk -- to run the same validation.
Discovered while implementing archie-core-rs9 (TOML write strategy). Not fixed there: rs9's scope was the text-patching mechanism, not wiring setup's actual validation step, and exporting validate() is really part of cbk's job (the thing that needs to call it).
Acceptance Criteria
configuration package exposes a callable that runs the same checks as the current unexported validate() against a config.Config value in memory (either export validate itself, or add a thin Validate(cfg *config.Config) error wrapper -- whichever fits the package's existing exported-surface conventions). Loader.Load continues to use it internally with no behavior change. A test outside the package (e.g. in cbk's setup tests) can call it directly without going through file I/O.
Imported from beads archie-core-1786637498978-348-c221a031 · GitHub #369 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08
The ewk epic's acceptance criteria (and archie-core-cbk's, by inheritance) require: "Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output." That identifier does not exist. internal/infrastructure/configuration/validate.go defines only an unexported validate(cfg *config.Config) error, called from one place: loader.go:178 inside Loader.Load's own decode-then-validate sequence. There is no way for code outside the configuration package -- e.g. `archied setup` after it builds a config.Config in memory but before writing it to disk -- to run the same validation.
Discovered while implementing archie-core-rs9 (TOML write strategy). Not fixed there: rs9's scope was the text-patching mechanism, not wiring setup's actual validation step, and exporting validate() is really part of cbk's job (the thing that needs to call it).
### Acceptance Criteria
configuration package exposes a callable that runs the same checks as the current unexported validate() against a config.Config value in memory (either export validate itself, or add a thin Validate(cfg *config.Config) error wrapper -- whichever fits the package's existing exported-surface conventions). Loader.Load continues to use it internally with no behavior change. A test outside the package (e.g. in cbk's setup tests) can call it directly without going through file I/O.
---
_Imported from beads `archie-core-1786637498978-348-c221a031` · GitHub #369 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumtask labels 2026-10-27 13:38:08 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The ewk epic's acceptance criteria (and archie-core-cbk's, by inheritance) require: "Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output." That identifier does not exist. internal/infrastructure/configuration/validate.go defines only an unexported validate(cfg *config.Config) error, called from one place: loader.go:178 inside Loader.Load's own decode-then-validate sequence. There is no way for code outside the configuration package -- e.g.
archied setupafter it builds a config.Config in memory but before writing it to disk -- to run the same validation.Discovered while implementing archie-core-rs9 (TOML write strategy). Not fixed there: rs9's scope was the text-patching mechanism, not wiring setup's actual validation step, and exporting validate() is really part of cbk's job (the thing that needs to call it).
Acceptance Criteria
configuration package exposes a callable that runs the same checks as the current unexported validate() against a config.Config value in memory (either export validate itself, or add a thin Validate(cfg *config.Config) error wrapper -- whichever fits the package's existing exported-surface conventions). Loader.Load continues to use it internally with no behavior change. A test outside the package (e.g. in cbk's setup tests) can call it directly without going through file I/O.
Imported from beads
archie-core-1786637498978-348-c221a031· GitHub #369 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08