sms template corrected and now fires at the end of the fanavaran stage (Expertise). Docs also added.

docs/fanavaran/01-write-apis.md

@@ -127,8 +127,7 @@ Full shape: see skill reference sample and `buildFanavaranSubmitPayload` / `appl
 | `Id` | `claimCases.claimId` |
 | `ClaimNo` | `claimCases.claimNo` |
 
-History: `FANAVARAN_EARLY_AUTO_SUBMIT_SUCCEEDED`.  
-SMS owner via `SmsOrchestrationService` (deduped `fanavaranSync.baseClaim.smsNotifiedAt`).
+History: `FANAVARAN_EARLY_AUTO_SUBMIT_SUCCEEDED`.
 
 ### Error handling
 
@@ -309,6 +308,7 @@ Requires `claimId` + `dmgCaseId` (soft-ensures earlier stages).
 | `Id` | `claimCases.expertiseId` |
 
 History: `FANAVARAN_EXPERTISE_AUTO_SUBMIT_SUCCEEDED`.  
+SMS owner via `SmsOrchestrationService` (deduped `fanavaranSync.expertise.smsNotifiedAt`).  
 Proven Parsian: `expertiseId=403144`, `ClaimExpertId=29`.
 
 Manual: `POST /v2/fanavaran/{client}/claim-cases/{id}/expertise/submit`.

docs/fanavaran/04-tenant-matrix.md

@@ -31,7 +31,7 @@ source: fanavaran-module-docs
 | Validation: FileTypeId ∈ tenant lookup | logic ✅ | allowed ids ✅ |
 | Business: THIRD_PARTY only | ✅ | ❌ |
 | Provisional address / dummy licence | ✅ today | may customize later |
-| SMS template after base claim | shared orchestration | provider/templates may ✅ |
+| SMS template after expertise | shared orchestration | provider/templates may ✅ |
 | Mongo collections / audit schema | ✅ | ❌ |
 | Offline inquiry seeds | may exist per client | ✅ |
 

docs/fanavaran/05-claim-flow.md

@@ -15,13 +15,13 @@ Start local claim
   → Validate THIRD_PARTY + data readiness
   → Auth (cached token)
   → Policy inquiry (resolve-once PolicyId)
-  → GEN.03 base claim → store claimId / claimNo → SMS owner
+  → GEN.03 base claim → store claimId / claimNo
   → SELECT_OUTER_PARTS
   → GEN.12 damage case → store dmgCaseId
   → Upload docs/images locally
   → GEN.07 attachments (per file, best-effort)
   → Expert pricing ready
-  → GEN.08 expertise → store expertiseId
+  → GEN.08 expertise → store expertiseId → SMS owner
   → End (local completion independent of Fanavaran success)
 ```
 
@@ -56,7 +56,6 @@ sequenceDiagram
   YARA->>FV: POST third-party-car-financial-claims (GEN.03)
   FV-->>YARA: Id, ClaimNo
   YARA->>DB: claimId, claimNo, history SUCCESS
-  YARA->>YARA: SMS owner (deduped)
 
   User->>YARA: SELECT_OUTER_PARTS
   YARA->>YARA: autoSubmitFanavaranDamageCase...
@@ -77,6 +76,7 @@ sequenceDiagram
   YARA->>FV: POST .../expertise (GEN.08)
   FV-->>YARA: ExpertiseId
   YARA->>DB: expertiseId, history SUCCESS
+  YARA->>YARA: SMS owner (deduped)
 ```
 
 ## Flow diagram (stages + soft-ensure)

docs/fanavaran/06-yara-integration.md

@@ -17,7 +17,7 @@ source: fanavaran-module-docs
 | Tenant config | boot + System Settings | `fanavaran-client-config.service.ts`, `system-settings.*` |
 | Orchestration | `ClaimRequestManagementModule` | `claim-request-management.service.ts` |
 | Policy select | same | `fanavaran-policy-selection.ts` |
-| SMS after base | `SmsOrchestrationModule` | `sms-orchestration.service.ts` |
+| SMS after expertise | `SmsOrchestrationModule` | `sms-orchestration.service.ts` |
 
 ---
 

docs/fanavaran/08-dependencies.md

@@ -21,7 +21,7 @@ source: fanavaran-module-docs
 
 | Dependency | Role |
 |------------|------|
-| **SMS provider** | Notify owner after successful GEN.03 (`SmsOrchestrationService`; same as login SMS stack) |
+| **SMS provider** | Notify owner after successful GEN.08 expertise (`SmsOrchestrationService`; same as login SMS stack) |
 | **Offline inquiry seeds** | Can supply driver/policy test data without live inquiry |
 | **Redis / Queue** | **Not** used for Fanavaran stage orchestration today — retries are in-process `setTimeout` + Mongo `nextRetryAt` |
 

docs/fanavaran/09-error-handling.md

@@ -69,4 +69,4 @@ Per HTTP step:
 
 ## SMS
 
-After successful base claim, owner SMS may be sent once (`smsNotifiedAt`). Failure to SMS should not roll back Fanavaran claim create; treat as separate notification concern.
+After successful expertise (last Fanavaran stage), owner SMS may be sent once (`fanavaranSync.expertise.smsNotifiedAt`). Failure to SMS should not roll back Fanavaran expertise submit; treat as separate notification concern. Claims already notified at base claim (`fanavaranSync.baseClaim.smsNotifiedAt`) are not re-notified.