Maurice ad312cdd43 Give day notes a domain of their own ...

days/ carried two fachlichkeiten with a full file set each: days.controller,
days.service, days.mcp, days.rpc, days.dto next to the five day-notes ones.
The note files move out unchanged; because the new directory sits at the same
depth, not one import path inside them changed.

The two modules deliberately do not reference each other in either direction:
dayExists is raw SQL on the days table in the note service, and DaysService
reads day_notes the same way, so a module edge would buy nothing and cost a
cycle.

DayNotesModule has to be registered in PluginsRuntimeModule as well as
AppModule - DayNotesRpc owns four of the 113 wire methods and the registry
boots with requireTotalCoverage, so leaving it out would stop every test app
that assembles the plugin runtime.

The days e2e container assembles both modules now: the note routes still nest
under the days prefix, and a container that builds only DaysModule would 404
on them while production served them fine.

2026-08-10 13:38:26 +02:00

..

day-notes.rpc.test.ts

Give day notes a domain of their own

2026-08-10 13:38:26 +02:00

days-itinerary.rpc.test.ts

Split PluginsModule into four, and gate coverage per domain

2026-08-09 18:44:59 +02:00