v4-readiness

To audit fork v4 readiness, validate your aeon.yml, skills.json, and MEMORY.md files against the v4 change manifest to generate a per-fork checklist surfacing Safe, Review, Custom, and Action items. This cross-reference process identifies configuration gaps without mutating the repository.

A v4 readiness checklist is a per-fork validation report that compares your current aeon.yml, skills.json, and MEMORY.md configurations against the v4 change manifest. It categorizes fork state into Safe, Review, Custom, and Action-items to guide your upgrade process.

Yes, you can survey remote forks for v4 readiness via the GitHub API. The audit reads core inputs from remote repositories and cross-references them with the embedded manifest to surface readiness gaps before, during, and after the v4 release.

No, the v4 readiness audit does not mutate your fork or trigger external actions. It strictly reads core inputs and writes an article at articles/v4-readiness-${today}.md plus a memory log to report actionable gaps safely.

Generate a v4 readiness report by dispatching the audit against your local fork. It reads your aeon.yml, skills.json, and MEMORY.md, cross-references the state with the v4 manifest, and writes the readiness article and memory logs to notify the operator of gaps.

You need to run a v4 fork audit before the v4 release, during the upgrade, and for post-upgrade reconciliation. It validates your chain definitions and model overrides against the manifest to ensure your fork remains compatible.