v4-readiness

To assess fork readiness for the Aeon v4 upgrade, an audit inspects your aeon.yml, skills.json, MEMORY.md, and skills directory. It generates a structured report classifying Safe, Review, and Custom items to guide your upgrade planning.

A v4 readiness audit evaluates your local worktree or remote fork by reading aeon.yml, skills.json, and MEMORY.md against the v4 change manifest. It produces a decision surface classifying items as Safe, Review, or Custom to prevent deployment surprises.

Yes, you can audit a remote fork without modifying it. The v4 readiness check enforces read-only behavior by inspecting remote aeon.yml and skills data, producing an article and memory log without auto-pulling upstream or altering the fork.

You should audit configuration files for a v4 upgrade before official announcements or during upgrade windows. This process surfaces breaking changes in aeon.yml, skills.json, and MEMORY.md ahead of deployment, reducing downtime and unexpected surprises.

During an Aeon v4 readiness check, the system inspects aeon.yml, skills.json, MEMORY.md, and the on-disk or remote skills directory. These files are mapped against the v4 change manifest to build Safe, Review, and Custom readiness items.

A key limitation of the fork audit is its read-only behavior; it produces an article and memory log but does not modify the fork or auto-pull upstream changes. Users must manually resolve any Review or Custom items surfaced in the readiness report.