Danijel Martinek f3182537c1 fix(boundaries): allow feature-to-feature imports of public exports ...

turbo.json's boundary config already allows `feature -> feature`, and
the cross-feature event system depends on it — a consumer must import
the publisher's event contract from `@repo/<publisher>`. But the ESLint
boundaries config, ADR-010, and AGENTS.md still declared
`feature -> [core, tooling]`, contradicting turbo.json and the shipped
code (marketing-pages imports @repo/auth).

Align all three to turbo.json: a feature may import another feature's
published public exports. Internals stay sealed by the `exports` map,
and cross-feature behaviour still flows through IEventBus.

2026-05-21 14:30:37 +02:00

..

rules

feat(core-eslint): add entity-must-have-test and no-relative-parent-import rules

2026-05-21 11:49:45 +02:00

AGENTS.md

docs: reflect tooling-package rename + Turbo boundaries enforcement

2026-05-05 12:24:04 +02:00

anchors.test.js

feat(core-eslint): anchor for events rules splice

2026-05-09 13:52:23 +02:00

base.js

fix(boundaries): allow feature-to-feature imports of public exports

2026-05-21 14:30:37 +02:00

eslint.config.js

refactor: rename eslint-config + typescript-config to core-eslint + core-typescript

2026-05-05 10:37:07 +02:00

next.js

refactor: rename eslint-config + typescript-config to core-eslint + core-typescript

2026-05-05 10:37:07 +02:00

package.json

feat(core-eslint): conformance plugin module + ./plugin export

2026-05-12 23:23:20 +02:00

plugin.js

feat(core-eslint): add entity-must-have-test and no-relative-parent-import rules

2026-05-21 11:49:45 +02:00

react-internal.js

refactor: rename eslint-config + typescript-config to core-eslint + core-typescript

2026-05-05 10:37:07 +02:00

turbo.json

build(turbo): add boundaries enforcement matching ESLint dependency graph

2026-05-05 11:59:44 +02:00

vitest.config.js

feat(core-eslint): rule no-direct-socket-io

2026-05-08 21:59:52 +02:00