Repository navigation
forgelm purge --check-policy --config requires a complete ForgeConfig; a file with only a retention block exits 1 #1054
Description
Summary
forgelm purge --check-policy --config PATH loads the file as a complete ForgeConfig, so a YAML file that holds only a retention: block exits 1 with four "Field required" validation errors (model, lora, training, data). The help text says --config "supplies the retention: horizons", which suggests that the block is all the command needs.
Evidence
$ cat retention-only.yaml
retention:
ephemeral_artefact_retention_days: 30
$ forgelm purge --check-policy --config retention-only.yaml --output-dir . --output-format json
{"success": false, "error": "--check-policy could not load --config: Configuration validation failed:\n4 validation errors for ForgeConfig\nmodel\n Field required ...
The exit code is 1 (EXIT_CONFIG_ERROR), which is the documented behaviour for an unloadable config, so nothing is silently wrong; the friction is that a scheduled retention report needs a full training config next to it.
Acceptance criteria
- Decide and record one behaviour: accept a file that holds only
retention:(validate that block withRetentionConfig), or keep requiring a full config and say so in the--confighelp, the purge reference (EN/TR), the GDPR guide and the user manual. - A test covers the chosen behaviour, including the exit code for an invalid
retention:block.
Context
Found while correcting the retention documentation for #101. Related: #554 (module sweep: purge / reverse-pii; --check-policy without --config).
Activity
fix(docs): align GDPR, erasure, retention and PII documentation with …
cemililik commentedon Oct 22, 2026
Triage (2026-10-22): accepted. Low · Wave 4 · parent #875 (Wave 4 · Module sweep).
Reproduced on
developmentat 735a02f: a file holding onlyretention:exits 1 with four "Field required" errors (model,lora,training,data). Without--configthe command prints "Noretention:block in the loaded config" and exits 0.--helpsays--config"supplies theretention:horizons".Do this together with #554 CR-A10-015 (refuse
--check-policywithout--config). Both decide how--check-policyloads its config, and one pull request keeps the rule consistent. Not blocked: CR-A10-015 is not one of Phase 16 S9's units (S9 owns CR-A10-021 and CR-A10-037 in #554).fix(purge): validate a retention-only --check-policy config strictly (H…
docs(changelog): say that only an invalid full config exits 1 (HodeTe…
fix(purge): accept retention-only config file for --check-policy (#1054…