Finalize the ConfigKit roadmap and implementation plan
This commit is contained in:
@@ -29,6 +29,15 @@ Use focused fuzzing for parser boundaries and semantic/filesystem path handling;
|
||||
keep deterministic seed regressions in the ordinary suite. Extended fuzz runs
|
||||
need a documented bounded invocation when introduced.
|
||||
|
||||
Secret bootstrap tests must cover existing variables including empty values,
|
||||
preflight without writes, partial apply failures, and safe blocked-file reporting.
|
||||
Use controlled environment names and restore state; process-mutating tests must
|
||||
not run in parallel. Keep real filesystem coverage and use narrow private seams
|
||||
for deterministic environment/write failures. Verify full input precedence and
|
||||
safe historical values, including removed and replaced secrets, at their owning
|
||||
boundaries. No credential bytes may appear in inspection or failure fixtures'
|
||||
expected output; use disposable canaries to prove non-disclosure.
|
||||
|
||||
Baseline commands belong in the [development guide](../development.md). Release
|
||||
gates belong in the [release policy](release.md) and its eventual runbook. This
|
||||
policy does not imply that those tools or tests already exist.
|
||||
|
||||
Reference in New Issue
Block a user