refactor(api): buses only in services, atomic commands, @Prop schemas

- Mongo read models are @Schema/@Prop classes (SchemaFactory), still
  loose: the props declared are the indexed or shaped ones.
- CommandBus and QueryBus are used by the application services alone.
  Duplicating a ticket, bulk updates, CSV imports, proposals and
  emptying the trash chain several commands, so they are service
  methods now and their composite commands are gone; every command
  handler is atomic. No forwardRef is needed.
- The due-date and trash timers are entry points: they live in the
  presenters and call the services. The automations event handler has
  its own file and calls AutomationsService.
- The tracker's user directory asks IdentityService; the composition
  root hands the identity application module to the tracker
  infrastructure (withIdentity), with no global module.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

libs/api/tracker/application/src/lib/automations.service.ts

@@ -5,6 +5,7 @@ import {
   CreateAutomationCommand,
   DeleteAutomationCommand,
   GetAutomationsQuery,
+  RunAutomationCommand,
   UpdateAutomationCommand,
 } from './automations/automations';
 import { Automation } from './ports/automations.repository';
@@ -41,6 +42,13 @@ export class AutomationsService {
     );
   }
 
+  /** Runs a rule on a ticket; the error, if any, as text. */
+  run(automation: Automation, issueId: string): Promise<string | null> {
+    return this.commandBus.execute(
+      new RunAutomationCommand(automation, issueId),
+    );
+  }
+
   delete(actorId: string, automationId: string): Promise<void> {
     return this.commandBus.execute(
       new DeleteAutomationCommand(actorId, automationId),