test(jest): resolve package-style core imports

[rafaelscosta]

Summary\n- Add Jest moduleNameMapper support for package-style aiox-core/... imports.\n- Add a regression test resolving a real framework module through the new alias.\n\n## Validation\n- node -c jest.config.js\n- node -c tests/config/jest-module-mapper.test.js\n- npm test -- tests/config/jest-module-mapper.test.js --runInBand\n- npm run generate:manifest + npm run validate:manifest\n- git diff --check\n- npm run lint — pass, 0 errors / 114 baseline warnings\n- npm run typecheck\n- node scripts/validate-package-completeness.js — 34/34 passed\n- node bin/utils/validate-publish.js — pass, 4199 files\n- npm test -- --runInBand --forceExit — 331 suites passed, 11 skipped; 8352 tests passed, 149 skipped\n\nPart of #621.

Summary by CodeRabbit

• Tests

  • Added test suite to verify framework module imports are correctly resolved by the test framework.

• Chores

  • Enhanced Jest configuration with module name mapping to ensure consistent and reliable import resolution during testing.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aiox-core	Ready	Preview, Comment	May 8, 2026 7:08am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 73451bae-c168-4803-b673-4c0e85fdeb39

📥 Commits

Reviewing files that changed from the base of the PR and between 19a012f and 6136775.

📒 Files selected for processing (2)

• jest.config.js
• tests/config/jest-module-mapper.test.js

---

Walkthrough

This PR adds a Jest module name mapper for aiox-core imports and includes a test to verify the mapping works. The configuration resolves aiox-core/* paths to the local /.aiox-core/* directory, and the test confirms that a package-style import correctly resolves to a framework module.

Changes

Jest Module Mapper Configuration

Layer / File(s)	Summary
Module Path Mapping jest.config.js	Jest moduleNameMapper is configured to map '^aiox-core/(.*)$' to '<rootDir>/.aiox-core/$1', enabling package-style import resolution.
Mapper Validation Test tests/config/jest-module-mapper.test.js	Test suite verifies that the moduleNameMapper correctly resolves aiox-core/core/synapse/layers/layer-processor imports to a module exported as the LayerProcessor function.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

type: test, area: core, area: devops

Suggested reviewers

• oalanicolas
• Pedrovaleriolopez

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adding Jest moduleNameMapper support for package-style aiox-core imports with a regression test.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch devops/issue-621-jest-aiox-core-alias-20260508

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

📊 Coverage Report

Coverage report not available

📈 Full coverage report available in Codecov

---

Generated by PR Automation (Story 6.1)