validate-codex-config

Validate codex config files by running a read-only check for syntax errors, broken file references, and schema compliance. This process inspects governance artifacts and schema definitions to catch inconsistencies early before deployment.

Auditing .afi-codex.json metadata involves verifying its accuracy and consistency against actual repository contents. A read-only validation check ensures the file metadata correctly reflects the repository's current capabilities and structure.

Schema compliance and test execution for governance artifacts are checked by running validation commands like `npm run validate` and `npm test`. This confirms structural integrity and successful execution before you merge configuration changes.

Config validation performs read-only validation only, meaning it does not modify your repository files. It safely checks for syntax errors, broken references, and schema compliance without altering the original configuration artifacts.

Validating governance artifacts and schema definitions before deployment prevents errors and inconsistencies in critical configuration files. It ensures structural integrity and metadata accuracy, avoiding failures caused by broken references or syntax errors.

Validation of afi-config codex and governance files is limited to read-only checks for syntax, references, and schema compliance. It does not auto-fix errors or execute write operations, requiring manual intervention to resolve detected issues.