v5.3.0: .aiox-core/package.json dropped ajv-formats but 4 modules still require it — breaks standalone installs

[batistasrj]

Summary

In v5.3.0, .aiox-core/package.json removed the ajv-formats dependency (present in 5.2.x), but four framework modules still require('ajv-formats'):

• .aiox-core/quality/metrics-collector.js (line 15)
• .aiox-core/core/config/config-resolver.js
• .aiox-core/core/registry/validate-registry.js
• .aiox-core/product/templates/engine/validator.js

Why CI doesn't catch it

The monorepo root package.json still declares ajv-formats@^3.0.1, so in the repo the module resolves via hoisting and all tests pass. The break only manifests in standalone installs (e.g. a project that vendored .aiox-core/ and syncs via scripts/update-aiox.sh), where npm install inside .aiox-core/ prunes the package.

Repro

# in a project with vendored .aiox-core at v5.3.0
cd .aiox-core && npm install   # prunes ajv-formats (not in package.json)
cd .. && node .aiox-core/cli/index.js --help
# Error: Cannot find module 'ajv-formats'
#   at .aiox-core/quality/metrics-collector.js
#   via cli/commands/metrics → cli/index.js  (CLI fully unusable)

Suggested fix

Re-add "ajv-formats": "^3.0.1" to .aiox-core/package.json (it still ships ajv ^8.17.1, which is the peer these call sites pair with).

Workaround (what we did)

cd .aiox-core && npm install ajv-formats@^3.0.1 — but any subsequent update-aiox.sh run overwrites package.json (upstream-wins) and re-breaks the CLI until the dep is reinstalled.

Environment

• aiox-core v5.3.0 (synced via .aiox-core/scripts/update-aiox.sh from 5.2.9)
• Node.js v24.14.0, Linux
• Standalone/vendored install (no monorepo root package.json)

[github-actions]

Welcome to aiox-core! Thanks for opening your first issue.

What happens next?

• A maintainer will triage this and add appropriate labels
• We'll respond as soon as possible
• Feel free to join Community Discussions

Helpful Resources:

• Contributing Guide
• Documentation

Looking to contribute? Check issues labeled community: good first issue.

[github-actions]

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed in 7 days if no further activity occurs.

If this issue is still relevant, please leave a comment to keep it open.