@burgan-tech/morph-touch-runtime 0.0.4 → 0.0.6

package/morph-touch/doc/morph-touch-domain.en.md

@@ -0,0 +1,328 @@
+# Morph-touch domain — technical overview
+
+This document summarizes appointment (rezervation), absence, chat room, notification, and transfer flows in the `morph-touch` domain, based on workflow definitions and task mapping behaviour. API examples align with the [postman_collection.json](../../postman_collection.json) collection.
+
+Turkish version: [morph-touch-domain.md](morph-touch-domain.md).
+
+---
+
+## 1. Overview and terminology
+
+- **Domain:** `morph-touch`
+- **Workflow instance:** vNext instance model with `key`, `flow` (`sys-flows`), `domain`, and `version`; started over HTTP at `.../workflows/{flowKey}/instances/...`, transitions at `.../transitions/{transitionKey}`.
+- **Integrations:**
+  - **DAPR / application API:** `api/v{version}/{domain}/...` (paths such as `functions/state`, `functions/data` in mappings).
+  - **Matrix:** `MatrixBaseUrl` (secret); room creation, join, invite, kick, history visibility.
+  - **MessagingGateway:** SMS and push notifications ([notification-sender](../Workflows/notification-sender.json)).
+
+### High-level relationships
+
+```mermaid
+flowchart LR
+  subgraph absence [absence-entry]
+    A1[complete]
+    A2[complete-with-transfer]
+  end
+  subgraph rez [rezervation]
+    R1[validating]
+    R2[appointment-form]
+    R3[active]
+    R4[in-meet]
+  end
+  subgraph transfer [rezervation-transfer]
+    T1[awaiting-assignment]
+  end
+  subgraph notify [notification-sender]
+    N1[pending to complete]
+  end
+  subgraph room [chat-room]
+    C1[permanent or reservation room]
+  end
+  R1 --> R2 --> R3
+  R3 --> N1
+  R3 --> absence
+  R3 --> R4
+  R4 --> room
+  A1 -->|start-transfer personal-leave| transfer
+  startChat[start-chat] --> room
+  resStart[rezervation-start] --> room
+  resStart --> R4
+```
+
+---
+
+## 2. absence-entry
+
+**File:** [Workflows/absence-entry.json](../Workflows/absence-entry.json)
+
+### Purpose
+
+- **Absence** records such as personal leave, customer meeting, etc.
+- **Public holiday** (`public-holiday`).
+- **Company working hours** and **advisor-specific working hours** (`working-hours-change` — with or without advisor for company-wide scope).
+
+Records are usually kept in `complete`; updated via `update`, moved to `cancelled` via `cancel`.
+
+### Link to appointment transfer
+
+- Transition **`start-transfer`** is evaluated only when `absenceType == "personal-leave"` (`CanStartTransferMapping` — [Workflows/src/CanStartTransferMapping.csx](../Workflows/src/CanStartTransferMapping.csx)).
+- When conditions hold, task `start-transfer-from-absence-entry` starts the **`rezervation-transfer`** subflow (`StartTransferFromAbsenceEntryMapping`).
+  - If **`endDateTime` is set**, transfer type is **annual leave** (`annual-leave`).
+  - If **`endDateTime` is empty**, type is **termination** (`termination`).
+  - Instance data must include **`advisor`**, **`advisorType`**, and **`startDateTime`**; otherwise the transfer task is skipped (`skipped` + reason).
+
+Final state: `complete-with-transfer` (transfer started).
+
+---
+
+## 3. rezervation-transfer
+
+**File:** [Workflows/rezervation-transfer.json](../Workflows/rezervation-transfer.json)
+
+### Purpose
+
+Move the source advisor’s appointments in a date range to suitable target advisors; run required Matrix operations on permanent chat rooms (per transfer vs update plan).
+
+### Initial tasks (summary)
+
+1. **Transfer type:** Without `endDate`, `termination` and a default far end date; with `endDate`, `annual-leave`.
+2. **Source appointments:** `get-rezervations`-style query (`FetchRezervationsForTransferMapping`).
+3. **Advisor list:** Active instances, workflow key resolution from `advisorType` / source id (`FetchAdvisorsForTransferMapping`).
+4. **Absence records:** Completed `public-holiday`, `working-hours-change`, `personal-leave` (`FetchAbsenceEntriesForTransferMapping`).
+5. **Enrichment:** All active appointments + slot validity (holiday, working hours, personal leave, conflicts) — `EnrichRezervationsForTransferMapping`.
+
+### Key checks
+
+- **`confirm-transfer`:** `validate-transfer-availability` — ensures the target advisor has no conflicting **active / in-meet** reservation in that slot; produces `validationResult.allValid` / `details`.
+- **`transferPlan`:** Postman example: each row has `rezervationKey` + `targetAdvisor` ([postman_collection.json](../../postman_collection.json) — “Confirm Transfer”).
+- Steps for permanent rooms using **`permanentRoomPlan`** (room `roomId` + `newAdvisorId`) are described in the collection notes.
+
+---
+
+## 4. rezervation
+
+**File:** [Workflows/rezervation.json](../Workflows/rezervation.json)
+
+### State outline
+
+`validating` → `appointment-form` or `slot-unavailable` → `active` → `in-meet` → `meet-completed`  
+Cancellations: `user-cancelled`, `advisor-cancelled`, `timeout`, etc.
+
+### Controls
+
+| Topic | Source | Description |
+|------|--------|-------------|
+| At most 2 reservations | `check-duplicate-rezervation` | For the same user, in certain confirmed states, at most **2** active reservations; **no overlapping** slots. |
+| Slot validity | `validate-slot-for-rezervation` | If the chosen range is missing from `get-available-slots` output → `slot-unavailable`; **`appointment-form-retry`** resubmits new date/time for re-validation. |
+| Date | `validate-date-for-rezervation` | Past or invalid dates are rejected. |
+| User | `set-user-from-headers-for-rezervation` | Request **`sub`** header is written to the instance. |
+| Confirm → active | `create-appointment` / confirmation chain | Order in workflow: previous advisor info, user info (`get-user-info-for-rezervation`), start **`notification-sender`**, create **`absence-entry`** (reservation record). |
+
+### Notification (when appointment is created)
+
+The `notification-sender` subflow starts during reservation confirmation. **Advisor** SMS/push body (summary):
+
+`Sayın " + (advisorName ?? "Danisman") + ", " + formattedDate + " tarihli randevunuz olusturulmustur."`
+
+**Customer** uses different copy (`SendSmsNotificationMapping` / `SendPushNotificationMapping` — [Workflows/src/SendSmsNotificationMapping.csx](../Workflows/src/SendSmsNotificationMapping.csx), [Workflows/src/SendPushNotificationMapping.csx](../Workflows/src/SendPushNotificationMapping.csx)). For channel selection and state transitions, see the **notification-sender** section (section 5 in this document).
+
+### Shared transitions
+
+- **`user-cancel` / `advisor-cancel` (active):** Triggers `cancel` on the related **`absence-entry`**; advisor cancel also sends a **cancellation notification**.
+- **`add-invited-participant`**, **`video-call-url-update`:** Merge invited-user list and video URL list.
+
+---
+
+## 5. notification-sender
+
+**File:** [Workflows/notification-sender.json](../Workflows/notification-sender.json)
+
+Subflow: started synchronously from reservation confirmation and other triggers. SMS (`/Messaging/sms/message/string`) and push (`/Messaging/push-notification/message`) calls are built in mappings against the `MessagingBaseUrl` secret.
+
+### States and automatic transitions
+
+| Source | Transition | Target | Condition (summary) |
+|--------|------------|--------|----------------------|
+| `pending` | `to-sms-sending` | `sms-sending` | `channels.sms == true` |
+| `pending` | `to-push-sending-from-pending` | `push-sending` | SMS not requested, `channels.push == true`, `hasRegisteredDevice == true` |
+| `pending` | `to-complete-from-pending` | `complete` | No applicable channel (push requested but no device, or no channel) |
+| `sms-sending` | (onEntry) | — | `send-sms-notification` task; `recipient.phone` (countryCode, prefix, number) required |
+| `sms-sending` | `to-push-sending-from-sms` | `push-sending` | `channels.push == true` and `hasRegisteredDevice == true` |
+| `sms-sending` | `to-complete-from-sms` | `complete` | Push not requested or no registered device |
+| `push-sending` | (onEntry) | — | `send-push-notification`; `recipient` uses `citizenshipNo` / `customerNo` |
+| `push-sending` | `to-complete-from-push` | `complete` | Always after push |
+
+**Copy:** `userType == "advisor"` uses advisor SMS/push text; `user` uses customer text (mapping summaries in the CSX files above).
+
+Postman: folder **Notification Sender Subprocess** — SMS only, push only, no channel, no device scenarios.
+
+---
+
+## 6. rezervation-start
+
+**File:** [Workflows/rezervation-start.json](../Workflows/rezervation-start.json)
+
+Both customer and advisor can start the meeting; the **first starter** takes the path that creates the reservation room; the other **joins**.
+
+### Requirements / checks
+
+- **`randevuKey`** required; state and data read via DAPR (`GetRezervationStateMapping`, `GetRezervationDataMapping`).
+- **Invited:** If `participantType == "invited"` and `invitedUserId` is not in the reservation `invitedUser` list → **`not-allowed`**.
+- If reservation state is not **`active`** or **`in-meet`** → **`meet-not-active`**.
+- **Time window (`check-randevu-time`):** Start allowed at most **15 minutes** before appointment start (script compares with `UtcNow + 3`); otherwise an error like `MEET_NOT_STARTED`.
+- **Invited and not yet in-meet:** `meet-not-started` branch.
+
+### Room and in-meet
+
+- If state is **`active`:** **`create-room-and-trigger`** — starts **`chat-room`** synchronously (`roomType: rezervation`), loads room data, fires **`to-in-meet`** on the main **`rezervation`**.
+- If state is already **`in-meet`:** **`join-room`** — Matrix `join`, `x-matrix-user` by participant type (user / advisor / invited).
+
+### End
+
+In `end` state, **`start-video-call`** subflow runs (LiveKit, etc.).
+
+---
+
+## 7. chat-room
+
+**File:** [Workflows/chat-room.json](../Workflows/chat-room.json)
+
+### Purpose
+
+- **Permanent room** (`roomType: permanent`): Matrix room keyed by user + advisor type + advisor.
+- **Reservation room** (`roomType: rezervation`): Process room tied to reservation key.
+
+### Behaviour summary
+
+- Creation: Matrix `createRoom`, invite, `join-user-to-room`.
+- **`activated`:** add member (`update`), remove member (`remove`), advisor **`transfer`** (kick + invite + join).
+- **`deactivate` / `activate`** states.
+- Second room creation blocked for same **user + advisorType + activated** on permanent rooms (`ALREADY_COMPLETED`).
+
+### Domain functions (via workflow)
+
+`get-chat-rooms`, `get-room-messages`, `send-room-message`, `get-matrix-sync` ([chat-room.json](../Workflows/chat-room.json) `attributes.functions`).
+
+---
+
+## 8. start-chat
+
+**File:** [Workflows/start-chat.json](../Workflows/start-chat.json)
+
+### Purpose
+
+Open permanent advisor chat: create room if missing, otherwise go straight to chat.
+
+### Flow
+
+1. **`check-existing-permanent-chat-room`:** Whether the user already has a permanent room for the same `advisorType`; `advisorId` match kept in a separate flag.
+2. **Existing room + same advisor** → **`in-chat`** (`open-existing-room`).
+3. **Existing room + different advisor** → **`to-change-advisor`:** fire **`transfer`** on `chat-room`, then **`in-chat`**.
+4. **No room** → **`start-permanent-chat-room`** starts **`chat-room`** synchronously, then **`in-chat`**.
+
+---
+
+## 9. add-participant-to-rezervation
+
+**File:** [Workflows/add-participant-to-rezervation.json](../Workflows/add-participant-to-rezervation.json)
+
+### Prerequisite
+
+Reservation state **`active`** or **`in-meet`**; otherwise **`state-not-valid`**.
+
+### Branches
+
+- **`in-meet`:** **update** on `chat-room` (new member) + **`add-invited-participant`** on `rezervation` + **`start-video-call`** subflow (invited customer path).
+- **`active`:** **`update-invited`** → **`end`** (invited update only).
+
+`newUserId` / `randevuKey` are required in task mappings.
+
+---
+
+## 10. Domain functions (summary)
+
+| Function | File | Purpose / notes |
+|----------|------|------------------|
+| `check-livekit-room-access` | [Functions/check-livekit-room-access.1.0.0.json](../Functions/check-livekit-room-access.1.0.0.json) | Query `access_token` (JWT or `prefix:roomName:participantName`). Participant validation on a single matching **active/in-meet** reservation; error on multiple matches. |
+| `get-absence-entry` | [Functions/get-absence-entry.1.0.0.json](../Functions/get-absence-entry.1.0.0.json) | Required `absenceType`: `public-holiday`, `personal-leave`, `working-hours-change`, `rezervation`. Optional `advisor`, `startDate`, `endDate`, `pageSize`. |
+| `get-advisor-stats` | [Functions/get-advisor-stats.1.0.0.json](../Functions/get-advisor-stats.1.0.0.json) | Advisor presence (Matrix: online, offline, busy, away). |
+| `get-available-slots` | [Functions/get-available-slots.1.0.0.json](../Functions/get-available-slots.1.0.0.json) | `advisorId`, `date`, optional `duration` (minutes). |
+| `get-chat-rooms` | [Functions/get-chat-rooms.1.0.0.json](../Functions/get-chat-rooms.1.0.0.json) | **`user` OR `advisor`** (mutually exclusive). |
+| `get-customer-info` | [Functions/get-customer-info.1.0.0.json](../Functions/get-customer-info.1.0.0.json) | Customer profile. |
+| `get-matrix-sync` | [Functions/get-matrix-sync.1.0.0.json](../Functions/get-matrix-sync.1.0.0.json) | Matrix sync payload. |
+| `get-rezervations` | [Functions/get-rezervations.1.0.0.json](../Functions/get-rezervations.1.0.0.json) | Filtered reservation list. |
+| `get-room-messages` | [Functions/get-room-messages.1.0.0.json](../Functions/get-room-messages.1.0.0.json) | Room messages. |
+| `send-room-message` | [Functions/send-room-message.1.0.0.json](../Functions/send-room-message.1.0.0.json) | Send message to Matrix. |
+
+See [Functions/get-room-messages.http](../Functions/get-room-messages.http) for detailed HTTP examples.
+
+---
+
+## 11. Postman collection
+
+**File:** [postman_collection.json](../../postman_collection.json) (workspace root)  
+**Collection name:** vNext Touch Domain
+
+### Shared variables (defaults)
+
+| Variable | Example value |
+|----------|----------------|
+| `baseUrl` | `http://localhost:4201` |
+| `apiVersion` | `1` |
+| `domain` | `morph-touch` |
+| `instanceKey` / `user` | `core.user.user-001` |
+| `advisor` / `advisorId` | `morph-touch.portfolio-manager.pm-001` |
+
+### Workflow API templates
+
+- **Start instance:**  
+  `POST {{baseUrl}}/api/v{{apiVersion}}/{{domain}}/workflows/{flowKey}/instances/start?sync=true`  
+  Examples: `rezervation`, `absence-entry`, `rezervation-start`, `chat-room`, `start-chat`, `rezervation-transfer`, `notification-sender` (subflow).
+- **Get instance:**  
+  `GET .../workflows/{flowKey}/instances/{{instanceId}}`
+- **Transition:**  
+  `PATCH .../workflows/{flowKey}/instances/{{instanceId}}/transitions/{transitionKey}?sync=true`  
+  Body is usually `{ "attributes": { ... } }`.
+
+### Sample requests (collection folders)
+
+| Folder / request | Method | Notes |
+|------------------|--------|-------|
+| **Reservation Workflow → Start Rezervation** | POST | `sub` header; body: `user`, `advisor`, `startDateTime`, `endDateTime`. |
+| **Confirm Selection** | PATCH | `transitions/confirm-selection` — slot validation step. |
+| **Appointment Form Retry** | PATCH | `appointment-form-retry` + new `startDateTime` / `endDateTime`. |
+| **Create Appointment** | PATCH | `create-appointment` → `active`. |
+| **Rezervation Start Workflow** | POST | `randevuKey`, `participantType` (advisor / customer / invited). |
+| **Chat Room Workflow** | POST / PATCH | Permanent PM/IA start; `update`, `remove`, `transfer`. |
+| **Start Chat Workflow** | POST | Creates permanent room if missing, else `in-chat`. |
+| **Rezervation Transfer** | POST + PATCH | `startDate`/`endDate`; `confirm-transfer` with `transferPlan`. |
+| **Get Absence Entry Function** | GET | `.../functions/get-absence-entry?absenceType=...` |
+| **Get Available Slots** | GET | `advisorId`, `date`, `duration`. |
+| **Get Chat Rooms** | GET | `user=...` or `advisor=...` |
+| **Matrix Synapse API** | various | `http://localhost:9080/...` — presence, createRoom (manual test). |
+| **Notification Sender Subprocess** | POST | `workflows/notification-sender/instances/start` — channel flags and recipient shape examples. |
+
+Collection descriptions reference [vNext documentation](https://github.com/burgan-tech/vnext-runtime/tree/main/doc/en) for instance filtering and task types.
+
+---
+
+## 12. Extra checks and edge cases
+
+- **Reservation cancel:** Triggers `absence-entry` cancel; on older instances without `absenceEntryKey`, cancel may no-op.
+- **Multiple invitees / video URLs:** List merge via `merge-invited-user`, `merge-video-call-urls`.
+- **check-livekit-room-access:** Token format JWT or `room:participant`; multiple matches yield an unusable result.
+- **notification-sender:** SMS requires phone structure; push uses `citizenshipNo` / `customerNo` and registered-device flag.
+- **chat-room:** Matrix `M_ROOM_IN_USE`; history visibility limited to allowed values (`shared`, `invited`, `joined`, `world_readable`) in mappings.
+
+---
+
+## 13. Related source files
+
+- Workflow JSON: [Workflows/](../Workflows/)
+- C# mappings: [Workflows/src/](../Workflows/src/)
+- Function definitions: [Functions/](../Functions/)
+- Project rules: [.cursorrules](../../.cursorrules)
+
+---
+
+*This document is derived from code and workflow definitions; runtime URLs and auth may vary by environment.*

package/morph-touch/doc/morph-touch-domain.md

@@ -0,0 +1,328 @@
+# Morph-touch domain — teknik özet
+
+Bu doküman, `morph-touch` domain’indeki randevu (rezervation), yokluk/absence, sohbet odası, bildirim ve transfer akışlarını; workflow tanımları ve görev mapping’lerindeki davranışa dayanarak özetler. API örnekleri [postman_collection.json](../../postman_collection.json) koleksiyonu ile uyumludur.
+
+İngilizce sürüm: [morph-touch-domain.en.md](morph-touch-domain.en.md).
+
+---
+
+## 1. Genel bakış ve terminoloji
+
+- **Domain:** `morph-touch`
+- **Workflow instance:** `key`, `flow` (`sys-flows`), `domain`, `version` ile tanımlı vNext instance modeli; HTTP üzerinden `.../workflows/{flowKey}/instances/...` ile başlatılır ve geçişler `.../transitions/{transitionKey}` ile tetiklenir.
+- **Entegrasyonlar:**
+  - **DAPR / uygulama API:** `api/v{version}/{domain}/...` (mapping’lerde geçen `functions/state`, `functions/data` yolları).
+  - **Matrix:** `MatrixBaseUrl` (secret); oda oluşturma, join, invite, kick, history visibility.
+  - **MessagingGateway:** SMS ve push bildirimleri ([notification-sender](../Workflows/notification-sender.json)).
+
+### Yüksek seviye ilişki
+
+```mermaid
+flowchart LR
+  subgraph absence [absence-entry]
+    A1[complete]
+    A2[complete-with-transfer]
+  end
+  subgraph rez [rezervation]
+    R1[validating]
+    R2[appointment-form]
+    R3[active]
+    R4[in-meet]
+  end
+  subgraph transfer [rezervation-transfer]
+    T1[awaiting-assignment]
+  end
+  subgraph notify [notification-sender]
+    N1[pending to complete]
+  end
+  subgraph room [chat-room]
+    C1[permanent or reservation room]
+  end
+  R1 --> R2 --> R3
+  R3 --> N1
+  R3 --> absence
+  R3 --> R4
+  R4 --> room
+  A1 -->|start-transfer personal-leave| transfer
+  startChat[start-chat] --> room
+  resStart[rezervation-start] --> room
+  resStart --> R4
+```
+
+---
+
+## 2. absence-entry
+
+**Dosya:** [Workflows/absence-entry.json](../Workflows/absence-entry.json)
+
+### Amaç
+
+- Kişisel izin, müşteri toplantısı vb. **yokluk** kayıtları.
+- **Resmi tatil** (`public-holiday`).
+- **Şirket çalışma saatleri** ve **danışmana özel çalışma saati** (`working-hours-change` — advisor’lı veya şirket geneli).
+
+Kayıtlar çoğunlukla `complete` durumunda tutulur; `update` ile güncellenir, `cancel` ile `cancelled` olur.
+
+### Randevu transferi ile bağlantı
+
+- Geçiş **`start-transfer`** yalnızca `absenceType == "personal-leave"` iken değerlendirilir (`CanStartTransferMapping` — [Workflows/src/CanStartTransferMapping.csx](../Workflows/src/CanStartTransferMapping.csx)).
+- Koşullar sağlanırsa `start-transfer-from-absence-entry` görevi **`rezervation-transfer`** alt akışını başlatır (`StartTransferFromAbsenceEntryMapping`).
+  - `endDateTime` **dolu** ise transfer tipi **yıllık izin** (`annual-leave`).
+  - `endDateTime` **boş** ise **işten çıkış / termination** (`termination`).
+  - Instance verisinde **`advisor`**, **`advisorType`**, **`startDateTime`** zorunludur; aksi halde transfer görevi atlanır (`skipped` + reason).
+
+Son durum: `complete-with-transfer` (transfer başlatıldı).
+
+---
+
+## 3. rezervation-transfer
+
+**Dosya:** [Workflows/rezervation-transfer.json](../Workflows/rezervation-transfer.json)
+
+### Amaç
+
+Kaynak danışmanın belirli tarih aralığındaki randevularını, uygun hedef danışmanlara aktarmak; kalıcı sohbet odalarında gerekli Matrix işlemlerini (transfer / update planına göre) yürütmek.
+
+### Başlangıç görevleri (özet)
+
+1. **Transfer tipi:** `endDate` yoksa `termination` ve varsayılan uzun uç tarih; varsa `annual-leave`.
+2. **Kaynak rezervasyonlar:** `get-rezervations` benzeri sorgu (`FetchRezervationsForTransferMapping`).
+3. **Danışman listesi:** Aktif instance’lar, `advisorType` / kaynak id ile workflow anahtarı çözümü (`FetchAdvisorsForTransferMapping`).
+4. **Absence kayıtları:** Tamamlanmış `public-holiday`, `working-hours-change`, `personal-leave` (`FetchAbsenceEntriesForTransferMapping`).
+5. **Zenginleştirme:** Tüm aktif randevular + slot uygunluğu (tatil, çalışma saati, kişisel izin, çakışma) — `EnrichRezervationsForTransferMapping`.
+
+### Önemli kontroller
+
+- **`confirm-transfer`:** `validate-transfer-availability` — hedef danışmanın ilgili rezervasyon zamanında başka **active / in-meet** çakışması var mı diye kontrol edilir; `validationResult.allValid` / `details` üretilir.
+- **`transferPlan`:** Postman’da örnek: her satırda `rezervationKey` + `targetAdvisor` ([postman_collection.json](../../postman_collection.json) — “Confirm Transfer”).
+- Kalıcı odalar için **`permanentRoomPlan`** (oda `roomId` + `newAdvisorId`) ile devam eden adımlar koleksiyon açıklamasında anlatılır.
+
+---
+
+## 4. rezervation
+
+**Dosya:** [Workflows/rezervation.json](../Workflows/rezervation.json)
+
+### Durum özeti (ana hat)
+
+`validating` → `appointment-form` veya `slot-unavailable` → `active` → `in-meet` → `meet-completed`  
+İptaller: `user-cancelled`, `advisor-cancelled`, `timeout` vb.
+
+### Kontroller
+
+| Konu | Kaynak | Açıklama |
+|------|--------|----------|
+| En fazla 2 rezervasyon | `check-duplicate-rezervation` | Aynı kullanıcı için belirli onaylı durumlarda en fazla **2** aktif rezervasyon; **zaman çakışması** yok. |
+| Slot uygunluğu | `validate-slot-for-rezervation` | `get-available-slots` çıktısında seçilen aralık yoksa `slot-unavailable`; **`appointment-form-retry`** ile yeni tarih/saat gönderilip tekrar doğrulanır. |
+| Tarih | `validate-date-for-rezervation` | Geçmiş veya geçersiz tarih reddedilir. |
+| Kullanıcı | `set-user-from-headers-for-rezervation` | İstek **`sub`** header’ından kullanıcıyı instance’a yazar. |
+| Onay → active | `create-appointment` / onay zinciri | Önceki danışman bilgisi, kullanıcı bilgisi (`get-user-info-for-rezervation`), **`notification-sender`** başlatma, **`absence-entry`** (rezervasyon kaydı) oluşturma sırası workflow’ta tanımlıdır. |
+
+### Bildirim (randevu oluşunca)
+
+`notification-sender` alt akışı, rezervasyon onayı sırasında başlatılır. **Danışman** için SMS/push içeriği (özet):
+
+`Sayın " + (advisorName ?? "Danisman") + ", " + formattedDate + " tarihli randevunuz olusturulmustur."`
+
+**Müşteri** için farklı metin kullanılır (`SendSmsNotificationMapping` / `SendPushNotificationMapping` — [Workflows/src/SendSmsNotificationMapping.csx](../Workflows/src/SendSmsNotificationMapping.csx), [Workflows/src/SendPushNotificationMapping.csx](../Workflows/src/SendPushNotificationMapping.csx)). Kanal seçimi ve durum geçişleri için **notification-sender** bölümüne (bu dokümanda 5) bakın.
+
+### Paylaşımlı geçişler
+
+- **`user-cancel` / `advisor-cancel` (active):** İlgili **`absence-entry`** üzerinde `cancel` tetiklenir; danışman iptalinde ek olarak **iptal bildirimi** gönderilir.
+- **`add-invited-participant`**, **`video-call-url-update`:** Davetli listesi ve video URL listesi birleştirme.
+
+---
+
+## 5. notification-sender
+
+**Dosya:** [Workflows/notification-sender.json](../Workflows/notification-sender.json)
+
+Alt süreç (subflow): randevu onayı ve diğer tetikleyicilerden senkron başlatılır. **MessagingGateway** üzerinden SMS (`/Messaging/sms/message/string`) ve push (`/Messaging/push-notification/message`) çağrıları mapping’lerde `MessagingBaseUrl` secret’ına göre kurulur.
+
+### Durumlar ve otomatik geçişler
+
+| Kaynak | Geçiş | Hedef | Koşul (özet) |
+|--------|--------|-------|----------------|
+| `pending` | `to-sms-sending` | `sms-sending` | `channels.sms == true` |
+| `pending` | `to-push-sending-from-pending` | `push-sending` | SMS istenmiyor, `channels.push == true`, `hasRegisteredDevice == true` |
+| `pending` | `to-complete-from-pending` | `complete` | Uygulanabilir kanal yok (push istenmiş ama cihaz yok, veya hiç kanal yok) |
+| `sms-sending` | (onEntry) | — | `send-sms-notification` görevi; `recipient.phone` (countryCode, prefix, number) zorunlu |
+| `sms-sending` | `to-push-sending-from-sms` | `push-sending` | `channels.push == true` ve `hasRegisteredDevice == true` |
+| `sms-sending` | `to-complete-from-sms` | `complete` | Push istenmiyor veya kayıtlı cihaz yok |
+| `push-sending` | (onEntry) | — | `send-push-notification`; `recipient` içinde `citizenshipNo` / `customerNo` kullanımı |
+| `push-sending` | `to-complete-from-push` | `complete` | Push sonrası her zaman |
+
+**İçerik:** `userType == "advisor"` için danışman SMS/push metni; `user` için müşteri metni (mapping özetleri yukarıdaki CSX dosyalarında).
+
+Postman: klasör **Notification Sender Subprocess** — SMS only, push only, kanal yok, cihaz yok senaryoları.
+
+---
+
+## 6. rezervation-start
+
+**Dosya:** [Workflows/rezervation-start.json](../Workflows/rezervation-start.json)
+
+Hem müşteri hem danışman görüşmeyi başlatabilir; **ilk başlatan** rezervasyon odasını oluşturma yoluna girer, diğer taraf **join** eder.
+
+### Zorunlu / kontroller
+
+- **`randevuKey`** zorunlu; state ve data DAPR üzerinden okunur (`GetRezervationStateMapping`, `GetRezervationDataMapping`).
+- **Davetli:** `participantType == "invited"` ve `invitedUserId`, rezervasyondaki `invitedUser` listesinde değilse → **`not-allowed`**.
+- Rezervasyon state **`active`** veya **`in-meet`** değilse → **`meet-not-active`**.
+- **Zaman penceresi (`check-randevu-time`):** Randevu başlangıcına en fazla **15 dakika** kala başlatılabilir (script’te saat dilimi `UtcNow + 3` ile karşılaştırma); aksi halde `MEET_NOT_STARTED` benzeri hata.
+- **Davetli ve henüz in-meet değilse:** `meet-not-started` dalı.
+
+### Oda ve in-meet
+
+- State **`active`** ise: **`create-room-and-trigger`** — senkron **`chat-room`** başlatılır (`roomType: rezervation`), oda verisi alınır, ana **`rezervation`** üzerinde **`to-in-meet`** tetiklenir.
+- State zaten **`in-meet`** ise: **`join-room`** — Matrix `join`, `x-matrix-user` katılımcı tipine göre (user / advisor / invited).
+
+### Bitiş
+
+`end` state’inde **`start-video-call`** alt akışı (LiveKit vb.) çalışır.
+
+---
+
+## 7. chat-room
+
+**Dosya:** [Workflows/chat-room.json](../Workflows/chat-room.json)
+
+### Amaç
+
+- **Kalıcı oda** (`roomType: permanent`): kullanıcı + danışman tipi + danışman ile tekilleştirilmiş Matrix odası.
+- **Randevu odası** (`roomType: rezervation`): rezervasyon anahtarı ile ilişkili geçici süreç odası.
+
+### Davranış özeti
+
+- Oluşturma: Matrix `createRoom`, davet, `join-user-to-room`.
+- **`activated`:** üye ekleme (`update`), üye çıkarma (`remove`), danışman **`transfer`** (kick + invite + join).
+- **`deactivate` / `activate`** durumları.
+- Kalıcı oda için aynı **user + advisorType + activated** ile ikinci oda oluşturma engeli (`ALREADY_COMPLETED`).
+
+### Domain fonksiyonları (workflow üzerinden)
+
+`get-chat-rooms`, `get-room-messages`, `send-room-message`, `get-matrix-sync` ([chat-room.json](../Workflows/chat-room.json) `attributes.functions`).
+
+---
+
+## 8. start-chat
+
+**Dosya:** [Workflows/start-chat.json](../Workflows/start-chat.json)
+
+### Amaç
+
+Kalıcı danışman sohbetini açmak: oda yoksa oluştur, varsa doğrudan sohbete geç.
+
+### Akış
+
+1. **`check-existing-permanent-chat-room`:** Kullanıcının aynı `advisorType` için kalıcı odası var mı; `advisorId` eşleşmesi ayrı bayrakta tutulur.
+2. **Mevcut oda + aynı danışman** → **`in-chat`** (`open-existing-room`).
+3. **Mevcut oda + farklı danışman** → **`to-change-advisor`:** `chat-room` üzerinde **`transfer`** tetiklenir, sonra **`in-chat`**.
+4. **Oda yok** → **`start-permanent-chat-room`** ile **`chat-room`** senkron başlatılır, sonra **`in-chat`**.
+
+---
+
+## 9. add-participant-to-rezervation
+
+**Dosya:** [Workflows/add-participant-to-rezervation.json](../Workflows/add-participant-to-rezervation.json)
+
+### Önkoşul
+
+Rezervasyon state **`active`** veya **`in-meet`**; aksi halde **`state-not-valid`**.
+
+### Dallar
+
+- **`in-meet`:** `chat-room` üzerinde **update** (yeni üye) + `rezervation` üzerinde **`add-invited-participant`** tetikleri + **`start-video-call`** alt akışı (davetli müşteri gibi).
+- **`active`:** **`update-invited`** → **`end`** (davetli güncelleme).
+
+`newUserId` / `randevuKey` görev mapping’lerinde zorunludur.
+
+---
+
+## 10. Domain fonksiyonları (özet)
+
+| Fonksiyon | Dosya | Amaç / not |
+|-----------|--------|------------|
+| `check-livekit-room-access` | [Functions/check-livekit-room-access.1.0.0.json](../Functions/check-livekit-room-access.1.0.0.json) | Query `access_token` (JWT veya `prefix:roomName:participantName`). Tek eşleşen **active/in-meet** rezervasyonda katılımcı doğrulaması; çoklu eşleşmede hata. |
+| `get-absence-entry` | [Functions/get-absence-entry.1.0.0.json](../Functions/get-absence-entry.1.0.0.json) | Zorunlu `absenceType`: `public-holiday`, `personal-leave`, `working-hours-change`, `rezervation`. Opsiyonel `advisor`, `startDate`, `endDate`, `pageSize`. |
+| `get-advisor-stats` | [Functions/get-advisor-stats.1.0.0.json](../Functions/get-advisor-stats.1.0.0.json) | Danışman presence (Matrix: online, offline, busy, away). |
+| `get-available-slots` | [Functions/get-available-slots.1.0.0.json](../Functions/get-available-slots.1.0.0.json) | `advisorId`, `date`, isteğe bağlı `duration` (dakika). |
+| `get-chat-rooms` | [Functions/get-chat-rooms.1.0.0.json](../Functions/get-chat-rooms.1.0.0.json) | **`user` VEYA `advisor`** (birbirini dışlar). |
+| `get-customer-info` | [Functions/get-customer-info.1.0.0.json](../Functions/get-customer-info.1.0.0.json) | Müşteri bilgisi. |
+| `get-matrix-sync` | [Functions/get-matrix-sync.1.0.0.json](../Functions/get-matrix-sync.1.0.0.json) | Matrix sync yanıtı. |
+| `get-rezervations` | [Functions/get-rezervations.1.0.0.json](../Functions/get-rezervations.1.0.0.json) | Filtreli rezervasyon listesi. |
+| `get-room-messages` | [Functions/get-room-messages.1.0.0.json](../Functions/get-room-messages.1.0.0.json) | Oda mesajları. |
+| `send-room-message` | [Functions/send-room-message.1.0.0.json](../Functions/send-room-message.1.0.0.json) | Matrix’e mesaj gönderimi. |
+
+Detaylı HTTP örnekleri için [Functions/get-room-messages.http](../Functions/get-room-messages.http) dosyasına bakılabilir.
+
+---
+
+## 11. Postman koleksiyonu
+
+**Dosya:** [postman_collection.json](../../postman_collection.json) (workspace kökü)  
+**Koleksiyon adı:** vNext Touch Domain
+
+### Ortak değişkenler (varsayılanlar)
+
+| Değişken | Örnek değer |
+|----------|-------------|
+| `baseUrl` | `http://localhost:4201` |
+| `apiVersion` | `1` |
+| `domain` | `morph-touch` |
+| `instanceKey` / `user` | `core.user.user-001` |
+| `advisor` / `advisorId` | `morph-touch.portfolio-manager.pm-001` |
+
+### Workflow API şablonları
+
+- **Instance başlat:**  
+  `POST {{baseUrl}}/api/v{{apiVersion}}/{{domain}}/workflows/{flowKey}/instances/start?sync=true`  
+  Örnek: `rezervation`, `absence-entry`, `rezervation-start`, `chat-room`, `start-chat`, `rezervation-transfer`, `notification-sender` (alt süreç).
+- **Instance oku:**  
+  `GET .../workflows/{flowKey}/instances/{{instanceId}}`
+- **Geçiş:**  
+  `PATCH .../workflows/{flowKey}/instances/{{instanceId}}/transitions/{transitionKey}?sync=true`  
+  Gövde genelde `{ "attributes": { ... } }`.
+
+### Örnek istekler (koleksiyon klasörleri)
+
+| Klasör / istek | Metod | Not |
+|----------------|-------|-----|
+| **Reservation Workflow → Start Rezervation** | POST | `sub` header; body’de `user`, `advisor`, `startDateTime`, `endDateTime`. |
+| **Confirm Selection** | PATCH | `transitions/confirm-selection` — slot doğrulama adımı. |
+| **Appointment Form Retry** | PATCH | `appointment-form-retry` + yeni `startDateTime` / `endDateTime`. |
+| **Create Appointment** | PATCH | `create-appointment` → `active`. |
+| **Rezervation Start Workflow** | POST | `randevuKey`, `participantType` (advisor / customer / invited). |
+| **Chat Room Workflow** | POST / PATCH | Kalıcı PM/IA başlatma; `update`, `remove`, `transfer`. |
+| **Start Chat Workflow** | POST | Kalıcı oda yoksa oluşturur, varsa `in-chat`. |
+| **Rezervation Transfer** | POST + PATCH | `startDate`/`endDate`; `confirm-transfer` ile `transferPlan`. |
+| **Get Absence Entry Function** | GET | `.../functions/get-absence-entry?absenceType=...` |
+| **Get Available Slots** | GET | `advisorId`, `date`, `duration`. |
+| **Get Chat Rooms** | GET | `user=...` veya `advisor=...` |
+| **Matrix Synapse API** | çeşitli | `http://localhost:9080/...` — presence, createRoom (manuel test). |
+| **Notification Sender Subprocess** | POST | `workflows/notification-sender/instances/start` — kanal bayrakları ve recipient yapısı örnekleri. |
+
+Koleksiyon içi açıklamalar: instance filtreleme ve görev tipleri için [vNext dokümantasyonu](https://github.com/burgan-tech/vnext-runtime/tree/main/doc/en) referans verilir.
+
+---
+
+## 12. Ek kontroller ve kenar durumları
+
+- **Rezervasyon iptali:** `absence-entry` iptali tetiklenir; eski instance’larda `absenceEntryKey` yoksa cancel no-op olabilir.
+- **Çoklu davetli / video URL:** `merge-invited-user`, `merge-video-call-urls` ile liste birleştirme.
+- **check-livekit-room-access:** Token formatı JWT veya `room:participant`; birden fazla eşleşmede anlamlı olmayan sonuç döner.
+- **notification-sender:** SMS için telefon yapısı zorunlu; push için `citizenshipNo` / `customerNo` ve kayıtlı cihaz bayrağı.
+- **chat-room:** Matrix `M_ROOM_IN_USE`; history visibility için izin verilen değerler (`shared`, `invited`, `joined`, `world_readable`) mapping’de sınırlı.
+
+---
+
+## 13. İlgili kaynak dosyalar
+
+- Workflow JSON: [Workflows/](../Workflows/)
+- C# mapping’ler: [Workflows/src/](../Workflows/src/)
+- Fonksiyon tanımları: [Functions/](../Functions/)
+- Proje kuralları: [.cursorrules](../../.cursorrules)
+
+---
+
+*Bu doküman, kod ve workflow tanımlarına göre oluşturulmuştur; çalışma zamanı URL’leri ve auth şeması ortamınıza göre değişebilir.*

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@burgan-tech/morph-touch-runtime",
-  "version": "0.0.4",
+  "version": "0.0.6",
   "description": "morph-touch - Runtime Package for engine deployment",
   "main": "index.js",
   "type": "module",