Closes the decision #1143 asked for. plugin_dir, module_dir, secret_engine_dir
and skills_dir keep their no-op validator, and the comment at that validator
now says so on purpose, with the two rules considered and refused:
- "must exist": all four consumers read a missing directory as an empty one by
design (plugin.LoadDir and secret.Registry.LoadDir return no entries and no
error on os.IsNotExist, loadModules skips an absent kind file, playbook.Load
returns an empty store, and internal/secret's TestLoadDirNonexistent pins the
no-error half), so the rule would turn deliberate emptiness into a failed
startup.
- "must be absolute" / "skills_dir under plugin_dir": no directory setting in
the repository is validated for shape, so a rule for these four alone is
arbitrary, and a boot-path validator over a stored document fails closed on
values the store already holds.
Deliberately no code change to either layer: configuration.validateDatabaseOwned
still has no say over the four, and the resource validator stays the single
no-op function with one obvious home for a rule.
Refs #1143