@futdevpro/nts-dynamo 1.15.157 → 1.15.160

package/src/_modules/mcp/_services/dynts-mcp.adapter.ts

@@ -1,168 +0,0 @@
-// A `@modelcontextprotocol/sdk` ESM-only csomag; a deep subpath-importjai (server/index, server/stdio,
-// types) KÖTELEZŐEN `.js`-suffixet igényelnek (az SDK `exports`-map így oldja fel) — ezért a `no-js-import`
-// szabály ITT indokoltan kikapcsolva (C2, FAM-REV bedrock-fix). Suffix-strip → resolve-hiba.
-/* eslint-disable @futdevpro/dynamo/no-js-import */
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
-import { CallToolRequestSchema, CallToolResult, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js';
-/* eslint-enable @futdevpro/dynamo/no-js-import */
-
-import { DyFM_Error } from '@futdevpro/fsm-dynamo';
-
-import {
-  DyNTS_Mcp_CallResult,
-  DyNTS_Mcp_ServerInfo,
-  DyNTS_Mcp_ToolDefinition,
-  DyNTS_Mcp_ToolOutcome
-} from '../_models/interfaces/dynts-mcp.interface';
-
-/**
- * `DyNTS_Mcp_Adapter` (BFR-AM-003) — a hivatalos `@modelcontextprotocol/sdk` köré épített **vékony
- * adaptor-réteg**. EZ az EGYETLEN hely a `/mcp` submodule-ban, ahol a SDK-típusok megjelennek — a
- * `DyNTS_Mcp_Server_ServiceBase` + a consumer tool-jai SDK-mentesek, így egy jövőbeli transport-/SDK-csere
- * NON-breaking (csak ez az osztály cserélődik).
- *
- * Felelősség (3 dolog, semmi domain-logika):
- *   1. EGY `registerTool` choke-pont (a tool-name → def map),
- *   2. a `tools/list` + `tools/call` JSON-RPC handler bekötése a SDK-szerverre,
- *   3. egységes hiba-fordítás: a tool-handler dobott hibája (vagy `isError:true` outcome-ja)
- *      strukturált `CallToolResult { isError:true }`-tá fordul — SOHA nem néma, SOHA nem crash.
- *
- * **stdio-konvenció:** a stdout a JSON-RPC csatorna — az adaptor maga SEMMIT nem ír a stdout-ra a
- * transport-payload-on kívül (minden log/diag a hívó App felelőssége, stderr-re).
- */
-export class DyNTS_Mcp_Adapter {
-
-  /** A SDK MCP-szerver (a transport-agnosztikus protocol-réteg). */
-  private readonly server: Server;
-
-  /** A regisztrált tool-definíciók `name` → def map-je (a `tools/call` dispatch-hez). */
-  private readonly tools: Map<string, DyNTS_Mcp_ToolDefinition> =
-    new Map<string, DyNTS_Mcp_ToolDefinition>();
-
-  constructor(set: DyNTS_Mcp_ServerInfo) {
-    this.server = new Server(
-      { name: set.name, version: set.version },
-      { capabilities: { tools: {} } },
-    );
-    this.installHandlers();
-  }
-
-  /**
-     * Az EGYETLEN tool-regisztrációs choke-pont. A regisztrált tool-ok hirdetődnek a `tools/list`-ben
-     * és dispatch-elhetők a `tools/call`-on. Az azonos nevű ismételt regisztráció felülír (last-wins).
-     */
-  public registerTool(definition: DyNTS_Mcp_ToolDefinition): void {
-    this.tools.set(definition.name, definition);
-  }
-
-  /** A hirdetett (regisztrált) tool-nevek (a contract/diszjunkció-teszthez). */
-  public getAdvertisedToolNames(): string[] {
-    return Array.from(this.tools.keys());
-  }
-
-  /**
-     * A stdio transport csatlakoztatása + a szerver indítása. A `connect` után a `tools/list` a
-     * regisztrált tool-okat hirdeti. A boot-üzenetek a stderr-en (a hívó App felel).
-     */
-  public async startStdio(): Promise<void> {
-    const transport: StdioServerTransport = new StdioServerTransport();
-
-    await this.server.connect(transport);
-  }
-
-  /** A szerver leállítása (graceful close — teszt-/shutdown-úthoz). */
-  public async close(): Promise<void> {
-    await this.server.close();
-  }
-
-  /**
-     * Egy tool-hívás KÖZVETLEN dispatch-elése (a transport-megkerülésével) — a contract/registry-teszt
-     * ezt hívja a stdio-szerver indítása nélkül. Ugyanaz a logika fut, mint a SDK `tools/call`-on:
-     * ismeretlen tool → strukturált hiba; handler-hiba → `isError:true` fordítás.
-     */
-  public async dispatchToolCall(set: { name: string; arguments?: unknown }): Promise<DyNTS_Mcp_CallResult> {
-    const definition: DyNTS_Mcp_ToolDefinition | undefined = this.tools.get(set.name);
-
-    if (!definition) {
-      return this.errorResult(`Unknown tool: '${set.name}'. Advertised tools: `
-                + `${this.getAdvertisedToolNames().join(', ')}.`);
-    }
-    try {
-      const outcome: DyNTS_Mcp_ToolOutcome = await definition.handler(set.arguments);
-
-      return this.toCallResult(outcome);
-    } catch (error) {
-      return this.errorResult(this.describeError(error), error);
-    }
-  }
-
-  // =========================================================================
-  // SDK request-handler bekötés (tools/list + tools/call)
-  // =========================================================================
-
-  /** A `tools/list` és a `tools/call` JSON-RPC handler bekötése a SDK-szerverre. */
-  private installHandlers(): void {
-    // tools/list — PONTOSAN a regisztrált (advertised) tool-okat hirdeti.
-    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
-      tools: Array.from(this.tools.values()).map((definition) => ({
-        name: definition.name,
-        description: definition.description,
-        inputSchema: definition.inputSchema,
-      })),
-    }));
-
-    // tools/call — a megfelelő handler futtatása + egységes hiba-fordítás (a közös dispatch-en át).
-    // A `DyNTS_Mcp_CallResult` a SDK `CallToolResult` egy al-shape-je (text-content + isError) — a
-    // SDK-cast KIZÁRÓLAG itt, az adaptor-boundary-n él (a SDK izolálva marad).
-    this.server.setRequestHandler(CallToolRequestSchema, async (request): Promise<CallToolResult> =>
-            (await this.dispatchToolCall({
-              name: request.params.name,
-              arguments: request.params.arguments,
-            })) as CallToolResult);
-  }
-
-  // =========================================================================
-  // CallToolResult fordítás (a transport-payload — text-JSON; egységes hiba-fordítás)
-  // =========================================================================
-
-  /** Egy sikeres (vagy strukturált-hiba) handler-outcome → `CallToolResult` (text-JSON content). */
-  private toCallResult(outcome: DyNTS_Mcp_ToolOutcome): DyNTS_Mcp_CallResult {
-    return {
-      content: [{ type: 'text', text: this.stringify(outcome.data) }],
-      isError: outcome.isError === true,
-    };
-  }
-
-  /** Egy hiba → `CallToolResult { isError:true }` strukturált hiba-payload-dal (soha nem néma). */
-  private errorResult(message: string, error?: unknown): DyNTS_Mcp_CallResult {
-    const errorCode: string | undefined = error instanceof DyFM_Error
-      ? DyFM_Error.getErrorCode(error)
-      : undefined;
-    const payload: object = { ok: false, error: { errorCode: errorCode, message: message } };
-
-    return { content: [{ type: 'text', text: this.stringify(payload) }], isError: true };
-  }
-
-  /** Egy hiba ember-olvasható üzenete (DyFM_Error → message; Error → message; egyéb → fallback). */
-  private describeError(error: unknown): string {
-    if (error instanceof DyFM_Error) {
-      return DyFM_Error.getErrorMessage(error) || 'Unknown DyFM error.';
-    }
-
-    if (error instanceof Error) {
-      return error.message;
-    }
-
-    return 'Unknown error during tool execution.';
-  }
-
-  /** JSON-stringify (a transport text-content payload-ja); szerializálás-hiba → strukturált hiba. */
-  private stringify(data: unknown): string {
-    try {
-      return JSON.stringify(data);
-    } catch {
-      return JSON.stringify({ ok: false, error: { message: 'The response is not JSON-serializable.' } });
-    }
-  }
-}

package/src/_modules/mcp/index.ts

@@ -1,13 +0,0 @@
-
-
-// MCP MODULE (BFR-AM-003) — domain-agnosztikus Model Context Protocol szerver-base + transport +
-// tool-registry, a hivatalos `@modelcontextprotocol/sdk` köré izolált adaptorral. A consumer
-// leszármazik a `DyNTS_Mcp_Server_ServiceBase`-ből + a SAJÁT tool-jait regisztrálja (a bedrock NEM definiál
-// domain-tool-t). A SDK KIZÁRÓLAG a `DyNTS_Mcp_Adapter` mögött él (transport-csere NON-breaking).
-
-// INTERFACES
-export * from './_models/interfaces/dynts-mcp.interface';
-
-// SERVICES
-export * from './_services/dynts-mcp.adapter';
-export * from './_services/dynts-mcp-server.service-base';

package/src/_modules/messaging/README.md

@@ -1,354 +0,0 @@
-# Dynamo NTS Messaging Module [DyNTS-MSG]
-
-TODO: The Entire Messaging system is AI generated, therefore we need to clean it up, and remove the unnecessary elements
-
-## Overview
-
-The DyNTS Messaging module provides the **backend implementation** for the unified messaging system. It handles all server-side operations including data persistence, business logic, real-time events, and API endpoints. The module integrates with bot and assistant modules to provide AI-powered messaging capabilities.
-
-## Import
-
-```typescript
-import * from '@futdevpro/dynamo-nts/messaging';
-```
-
-## Key Features
-
-- **Data Services**: CRUD operations for messages and conversations
-- **Control Services**: Business logic orchestration and validation
-- **Event Handling**: Real-time socket communication
-- **API Endpoints**: RESTful HTTP endpoints for all messaging operations
-- **Bot Integration**: Seamless integration with AI bot modules
-- **Assistant Integration**: Support for AI assistant workflows
-- **Authentication**: User authentication and authorization
-- **Error Handling**: Comprehensive error handling and logging
-- **Real-time Events**: Socket-based live updates
-- **Agent Process Tracking**: AI reasoning and tool usage recording
-
-## Architecture
-
-The messaging module follows a layered architecture:
-
-```
-┌─────────────────────────────────────┐
-│     HTTP Controller (API)          │
-└────────────────┬──────────────────┘
-                 │
-┌────────────────▼──────────────────┐
-│     Control Services             │
-│  • Main Control                  │
-│  • Integration Control           │
-│  • Events Service                │
-└────────────────┬──────────────────┘
-                 │
-┌────────────────▼──────────────────┐
-│     Data Services                │
-│  • Message Data Service          │
-│  • Conversation Data Service     │
-└────────────────┬──────────────────┘
-                 │
-┌────────────────▼──────────────────┐
-│     Database Layer               │
-└─────────────────────────────────┘
-```
-
-## Services
-
-### Data Services
-
-#### `DyNTS_Msg_Message_DataService`
-
-Handles all message data operations:
-
-```typescript
-class DyNTS_Msg_Message_DataService {
-  async saveData(message: DyFM_Msg_Message): Promise<void>;
-  async getDataById(messageId: string): Promise<DyFM_Msg_Message>;
-  async markAsRead(messageId: string, userId: string): Promise<void>;
-  async deleteData(messageId: string): Promise<void>;
-}
-```
-
-**Usage Example:**
-```typescript
-const messageService = new DyNTS_Msg_Message_DataService({
-  issuer: 'user-id',
-});
-
-const message = await messageService.getDataById('msg-123');
-await messageService.markAsRead('msg-123', 'user-id');
-```
-
-#### `DyNTS_Msg_Conversation_DataService`
-
-Handles all conversation data operations:
-
-```typescript
-class DyNTS_Msg_Conversation_DataService {
-  async saveData(conversation: DyFM_Msg_Conversation): Promise<void>;
-  async getDataById(conversationId: string): Promise<DyFM_Msg_Conversation>;
-  async updateLastMessage(conversationId: string, messageId: string, content: string): Promise<void>;
-  async addParticipant(conversationId: string, participant: DyFM_Msg_Participant): Promise<void>;
-  async removeParticipant(conversationId: string, userId: string): Promise<void>;
-}
-```
-
-### Control Services
-
-#### `DyNTS_Msg_Main_ControlService`
-
-Singleton service for orchestration and business logic:
-
-```typescript
-class DyNTS_Msg_Main_ControlService extends DyNTS_SingletonService {
-  static getInstance(): DyNTS_Msg_Main_ControlService;
-  
-  // Messages
-  async sendMessage(conversationId: string, messageData: Partial<DyFM_Msg_Message>, senderId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  async editMessage(messageId: string, content: string, userId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  async deleteMessage(messageId: string, userId: string, issuer: string): Promise<void>;
-  async markMessagesAsRead(messageIds: string[], userId: string, issuer: string): Promise<{ success: boolean; count: number }>;
-  
-  // Reactions
-  async addReaction(messageId: string, emoji: string, userId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  async removeReaction(messageId: string, emoji: string, userId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  
-  // Conversations
-  async createConversation(conversationData: Partial<DyFM_Msg_Conversation>, creatorId: string, issuer: string): Promise<DyFM_Msg_Conversation>;
-  async updateConversation(conversationId: string, updateData: Partial<DyFM_Msg_Conversation>, userId: string, issuer: string): Promise<DyFM_Msg_Conversation>;
-  async deleteConversation(conversationId: string, userId: string, issuer: string): Promise<void>;
-  
-  // Participants
-  async addParticipant(conversationId: string, newUserId: string, role: DyFM_Msg_ParticipantRole, requesterId: string, issuer: string): Promise<void>;
-  async removeParticipant(conversationId: string, userIdToRemove: string, requesterId: string, issuer: string): Promise<void>;
-}
-```
-
-**Usage Example:**
-```typescript
-const controlService = DyNTS_Msg_Main_ControlService.getInstance();
-
-// Send a message
-const message = await controlService.sendMessage(
-  'conv-123',
-  { content: 'Hello!' },
-  'user-456',
-  'user-456'
-);
-
-// Add reaction
-await controlService.addReaction(
-  'msg-789',
-  '👍',
-  'user-456',
-  'user-456'
-);
-```
-
-#### `DyNTS_Msg_Integration_ControlService`
-
-Handles integration with bot and assistant modules:
-
-```typescript
-class DyNTS_Msg_Integration_ControlService extends DyNTS_SingletonService {
-  static getInstance(): DyNTS_Msg_Integration_ControlService;
-  
-  // Bot integration
-  async syncBotMessage<T>(botMessage: DyNTS_Bot_MessageWrapper<T>, conversationId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  
-  // Assistant integration
-  async syncAssistantMessage(content: string, conversationId: string, aiProvider: string, aiModel: string, senderId: string, issuer: string): Promise<DyFM_Msg_Message>;
-  
-  // Find or create bot conversation
-  async findOrCreateBotConversation(channelId: string, platformSource: string, issuer: string): Promise<DyFM_Msg_Conversation>;
-}
-```
-
-#### `DyNTS_Msg_Events_Service`
-
-Handles real-time socket events:
-
-```typescript
-class DyNTS_Msg_Events_Service extends DyNTS_SingletonService {
-  static getInstance(): DyNTS_Msg_Events_Service;
-  
-  // Event emission
-  emitMessageSent(message: DyFM_Msg_Message, conversationId: string): void;
-  emitMessageUpdated(message: DyFM_Msg_Message, conversationId: string): void;
-  emitMessageDeleted(messageId: string, conversationId: string): void;
-  emitMessageRead(messageId: string, userId: string, conversationId: string): void;
-  emitTypingIndicator(userId: string, conversationId: string, isTyping: boolean): void;
-  emitConversationCreated(conversation: DyFM_Msg_Conversation, participantIds: string[]): void;
-  emitConversationUpdated(conversation: DyFM_Msg_Conversation): void;
-  emitConversationDeleted(conversationId: string): void;
-  emitParticipantAdded(conversationId: string, userId: string): void;
-  emitParticipantRemoved(conversationId: string, userId: string): void;
-  emitReactionAdded(messageId: string, reaction: DyFM_Msg_Reaction): void;
-  emitReactionRemoved(messageId: string, userId: string, emoji: string): void;
-}
-```
-
-### Controllers
-
-#### `DyNTS_Msg_Controller`
-
-HTTP API controller for messaging endpoints:
-
-**Endpoints:**
-- `POST /api/messaging/messages` - Send a message
-- `PUT /api/messaging/messages/:id` - Edit a message
-- `DELETE /api/messaging/messages/:id` - Delete a message
-- `POST /api/messaging/messages/:id/read` - Mark messages as read
-- `POST /api/messaging/messages/:id/reactions` - Add reaction
-- `DELETE /api/messaging/messages/:id/reactions` - Remove reaction
-- `GET /api/messaging/conversations` - Get conversations
-- `POST /api/messaging/conversations` - Create conversation
-- `PUT /api/messaging/conversations/:id` - Update conversation
-- `DELETE /api/messaging/conversations/:id` - Delete conversation
-- `POST /api/messaging/conversations/:id/participants` - Add participant
-- `DELETE /api/messaging/conversations/:id/participants/:userId` - Remove participant
-
-## Configuration
-
-### Global Settings
-
-Configure messaging settings in your global configuration:
-
-```typescript
-export const DyNTS_global_settings = {
-  messaging_settings: {
-    enableRealtimeEvents: true,
-    maxMessagesPerLoad: 50,
-    enableThreading: true,
-    enableReactions: true,
-    enableAttachments: true,
-    enableMentions: true,
-    enableReadReceipts: true,
-    enableTypingIndicators: true,
-    retry: {
-      maxRetries: 3,
-      retryDelay: 1000
-    }
-  }
-};
-```
-
-## Routing
-
-Add the messaging routing module to your application:
-
-```typescript
-import { DyNTS_getMessagingRoutingModule } from '@futdevpro/dynamo-nts/messaging';
-
-const messagingRoutes = DyNTS_getMessagingRoutingModule(
-  DyNTS_RouteSecurity.authenticated
-);
-
-// Add to your routing configuration
-```
-
-## Integration
-
-### Bot Integration
-
-The messaging system integrates with the bot module to sync messages:
-
-```typescript
-import { DyNTS_Msg_Integration_ControlService } from '@futdevpro/dynamo-nts/messaging';
-import { DyNTS_Bot_MessageWrapper } from '@futdevpro/dynamo-nts/bot';
-
-const integrationService = DyNTS_Msg_Integration_ControlService.getInstance();
-
-// Sync bot message to messaging system
-const message = await integrationService.syncBotMessage(
-  botMessage,
-  conversationId,
-  'bot-service'
-);
-```
-
-### Assistant Integration
-
-Sync AI assistant responses:
-
-```typescript
-// Sync AI assistant message
-const aiMessage = await integrationService.syncAssistantMessage(
-  'AI response text',
-  'conv-123',
-  'openai',
-  'gpt-4',
-  'ai-assistant-id',
-  'ai-service'
-);
-```
-
-## Usage Examples
-
-### Sending a Message
-
-```typescript
-import { DyNTS_Msg_Main_ControlService } from '@futdevpro/dynamo-nts/messaging';
-
-const controlService = DyNTS_Msg_Main_ControlService.getInstance();
-
-const message = await controlService.sendMessage(
-  'conv-123',
-  {
-    content: 'Hello from the backend!',
-    type: DyFM_Msg_Type.text
-  },
-  'user-456',
-  'backend-service'
-);
-```
-
-### Creating a Conversation
-
-```typescript
-const conversation = await controlService.createConversation(
-  {
-    type: DyFM_Msg_ConversationType.direct,
-    participants: [
-      { userId: 'user-123', role: DyFM_Msg_ParticipantRole.member, joinedAt: new Date() },
-      { userId: 'user-456', role: DyFM_Msg_ParticipantRole.member, joinedAt: new Date() }
-    ]
-  },
-  'user-123',
-  'backend-service'
-);
-```
-
-### Adding a Reaction
-
-```typescript
-const message = await controlService.addReaction(
-  'msg-123',
-  '👍',
-  'user-456',
-  'user-456'
-);
-```
-
-## Error Handling
-
-The module uses comprehensive error handling:
-
-```typescript
-try {
-  await controlService.sendMessage(...);
-} catch (error) {
-  if (error instanceof DyFM_Error) {
-    console.error('Error code:', error.errorCode);
-    console.error('User message:', error.userMessage);
-    console.error('Technical message:', error.technicalMessage);
-  }
-}
-```
-
-## Related Documentation
-
-- [Dynamo FSM Messaging Module](../dynamo-fsm/messaging/README.md)
-- [Dynamo NGX Messaging Module](../dynamo-ngx/messaging/README.md)
-- [Bot Module Integration](./bot/README.md)
-- [Assistant Module Integration](./assistant/README.md)

package/src/_modules/messaging/_collections/get-messaging-routing-module.util.ts

@@ -1,26 +0,0 @@
-import { DyFM_msgModule_settings } from '@futdevpro/fsm-dynamo/messaging';
-import { DyNTS_RouteSecurity } from '../../../_enums/route-security.enum';
-import {
-  DyNTS_RoutingModule_Settings
-} from '../../../_models/interfaces/routing-module-settings.interface';
-import { DyNTS_RoutingModule } from '../../../_services/route/routing-module.service';
-import { DyNTS_Msg_Controller } from '../_services/msg.controller';
-
-/**
- * Get messaging routing module
- * Creates and configures the messaging module routes
- */
-export function DyNTS_getMessagingRoutingModule(
-  securityOverride?: DyNTS_RouteSecurity
-): DyNTS_RoutingModule {
-  const set: DyNTS_RoutingModule_Settings = {
-    route: DyFM_msgModule_settings.mainRoute,
-    controllers: [DyNTS_Msg_Controller.getInstance()],
-  };
-  
-  if (securityOverride) {
-    set.securityOverride = securityOverride;
-  }
-  
-  return new DyNTS_RoutingModule(set);
-}

package/src/_modules/messaging/_collections/msg-global-settings.const.ts

@@ -1,22 +0,0 @@
-import { megabyte, second } from '@futdevpro/fsm-dynamo';
-import { DyNTS_Msg_Global_Settings } from '../_models/msg-global-settings.interface';
-
-/**
- * Default messaging module settings
- */
-export const DyNTS_Msg_global_settings: DyNTS_Msg_Global_Settings = {
-  enableRealtimeEvents: true,
-  maxMessagesPerLoad: 50,
-  enableThreading: true,
-  enableReactions: true,
-  enableAttachments: true,
-  maxAttachmentSize: 10 * megabyte, // 10MB
-  enableMentions: true,
-  enableReadReceipts: true,
-  enableTypingIndicators: true,
-  
-  retry: {
-    maxRetries: 3,
-    retryDelay: second, // 1 second
-  },
-};