@salesforce/afv-skills 1.59.0 → 1.60.0

package/skills/insurance-brokerage-agency-billing-configure/references/org-defaults.md

@@ -0,0 +1,64 @@
+# Phase 4: Org Defaults
+
+All five org defaults are set via dedicated headless routes on `BillingGettingStartedController` — no Tooling API required.
+
+> **Run after Phase 3.** You need the record IDs for Legal Entity, Billing Treatment, and Tax Treatment from Phase 3.
+
+> **Note:** `BillingSettings` is a standard platform Metadata type accessible via Metadata API deploy/retrieve, but `SELECT Id,Metadata FROM BillingSettings` via Tooling API SOQL is not supported on all org types (returns INVALID_TYPE on orgfarm). Use the headless routes below instead — they write the same underlying OrgValues and are the correct headless path.
+
+---
+
+## Step 1: Default Legal Entity
+
+```text
+dispatch PATCH /headless/invoke/platform/billing-invoice-configurations/set-default-legal-entity-org-value
+{"defaultLegalEntity": "<LEGAL_ENTITY_ID>"}
+```
+
+---
+
+## Step 2: Default Billing Treatment
+
+```text
+dispatch PATCH /headless/invoke/platform/currency-conversion-guided-setup/set-default-billing-treatment-org-value
+{"defaultBillingTreatment": "<ADVANCE_BT_ID>"}
+```
+
+---
+
+## Step 3: Default Tax Treatment
+
+```text
+dispatch PATCH /headless/invoke/platform/billing-settings/set-default-tax-treatment-org-value
+{"defaultTaxTreatment": "<TAX_TREATMENT_ID>"}
+```
+
+---
+
+## Step 4: DPE Template — GL Account Period Summary
+
+```text
+dispatch PATCH /headless/invoke/platform/billing-prerequisites/set-default-leap-sum-dpetemplate-name-org-value
+{"defaultLeapSumDPETemplate": "CreateGLAccountingPeriodSummaryRecord"}
+```
+
+---
+
+## Step 5: DPE Template — Accounting Period Closure/Reopen
+
+```text
+dispatch PATCH /headless/invoke/platform/billing-prerequisites/set-default-leap-reop-dpetemplate-name-org-value
+{"defaultLeapReopDPETemplate": "LegalEntityAccountingPeriodClosureBillingSuite"}
+```
+
+---
+
+## Field Reference
+
+| Setting | Route segment | Field | Value source |
+|---------|--------------|-------|--------------|
+| Default Legal Entity | `billing-invoice-configurations/set-default-legal-entity-org-value` | `defaultLegalEntity` | LegalEntity record Id from Phase 3 |
+| Default Billing Treatment | `currency-conversion-guided-setup/set-default-billing-treatment-org-value` | `defaultBillingTreatment` | Advance BT record Id from Phase 3 |
+| Default Tax Treatment | `billing-settings/set-default-tax-treatment-org-value` | `defaultTaxTreatment` | TaxTreatment record Id from Phase 3 |
+| DPE: GL Period Summary | `billing-prerequisites/set-default-leap-sum-dpetemplate-name-org-value` | `defaultLeapSumDPETemplate` | `CreateGLAccountingPeriodSummaryRecord` |
+| DPE: AP Closure/Reopen | `billing-prerequisites/set-default-leap-reop-dpetemplate-name-org-value` | `defaultLeapReopDPETemplate` | `LegalEntityAccountingPeriodClosureBillingSuite` |

package/skills/insurance-brokerage-agency-billing-configure/references/permissions-config.md

@@ -0,0 +1,226 @@
+# Phase 6: Permissions & FLS
+
+## Permission Sets (15 total)
+
+| # | Label | API Name |
+|---|-------|----------|
+| 1 | Billing Admin | RevenueLifecycleManagementBillingAdmin |
+| 2 | Basic CSV Data Import | SimpleCsvDataImport |
+| 3 | Context Service Admin | ContextServiceAdminPsl |
+| 4 | Insurance Billing Integration | InsuranceBillingIntegration |
+| 5 | Billing Operations User | RevenueLifecycleManagementBillingOperations |
+| 6 | Collections and Recovery Admin | CollectionsAndRecoveryAdmin |
+| 7 | Generate Invoices From Billing Schedule API | RevenueLifecycleManagementBillingCreateInvoiceFromBillingScheduleApi |
+| 8 | Data Pipelines Base User | AnalyticsStoreUser |
+| 9 | Payment Admin | BillingAdvancedPaymentAdministrator |
+| 10 | DocGen Designer | DocGenDesigner |
+| 11 | Payment Operations User | BillingAdvancedPaymentOperations |
+| 12 | Tax Admin | RevenueLifecycleManagementBillingTaxAdmin |
+| 13 | DocGen User | DocGenUser |
+| 14 | Accounts Receivables Admin | RevenueLifecycleManagementAccountingAdmin |
+| 15 | FSC Insurance | FSCInsurance |
+
+---
+
+## Check Existing Assignments
+
+Use the target user ID captured in Phase 1 (`<TARGET_USER_ID>`).
+
+```text
+dispatch GET /query?q=SELECT+PermissionSet.Name,PermissionSet.Label+FROM+PermissionSetAssignment+WHERE+AssigneeId='<TARGET_USER_ID>'+AND+PermissionSet.Name+IN+('RevenueLifecycleManagementBillingAdmin','SimpleCsvDataImport','ContextServiceAdminPsl','InsuranceBillingIntegration','RevenueLifecycleManagementBillingOperations','CollectionsAndRecoveryAdmin','RevenueLifecycleManagementBillingCreateInvoiceFromBillingScheduleApi','AnalyticsStoreUser','BillingAdvancedPaymentAdministrator','DocGenDesigner','BillingAdvancedPaymentOperations','RevenueLifecycleManagementBillingTaxAdmin','DocGenUser','RevenueLifecycleManagementAccountingAdmin','FSCInsurance')
+```
+
+---
+
+## Assign Missing Permission Sets
+
+For each missing permission set, first resolve its Id by name, then create the assignment.
+
+**Step 1 — Resolve PermissionSet Id:**
+```text
+dispatch GET /query?q=SELECT+Id+FROM+PermissionSet+WHERE+Name='<apiName>'+AND+IsOwnedByProfile=false
+```
+
+**Step 2 — Create assignment:**
+```text
+dispatch POST /sobjects/PermissionSetAssignment
+{"AssigneeId": "<TARGET_USER_ID>", "PermissionSetId": "<PS_ID>"}
+```
+
+If assignment fails (e.g., missing license), log the error and continue with remaining sets.
+
+---
+
+## Field-Level Security for InsPolicyBillingInfo
+
+**MANDATORY STEP — CANNOT BE SKIPPED.** The 6 billing lookup fields on InsPolicyBillingInfo require Field-Level Security to be visible. Without this, Phase 7 will fail with INVALID_FIELD when creating InsPolicyBillingInfo records.
+
+**CRITICAL: The permission set creation is UNCONDITIONALLY MANDATORY.** Even if FLS is already granted via another permission set, you MUST attempt to create the `Insurance_Billing_Field_Access` permission set. The creation may return a DUPLICATE error (which is acceptable and means it already exists), but you MUST NOT skip the creation attempt based on the FLS query results alone.
+
+### Verify FLS Exists (For Diagnostic Purposes Only)
+
+Query FieldPermissions to confirm FLS status (this is for verification, NOT a gate for creation):
+
+```text
+dispatch GET /query?q=SELECT+Field+FROM+FieldPermissions+WHERE+SobjectType='InsPolicyBillingInfo'+AND+Field+IN+('InsPolicyBillingInfo.BillingTreatmentId','InsPolicyBillingInfo.TaxTreatmentId','InsPolicyBillingInfo.ProrationPolicyId','InsPolicyBillingInfo.PaymentTermId','InsPolicyBillingInfo.ProductSellingModelId','InsPolicyBillingInfo.LegalEntityId')+AND+PermissionsRead=true+AND+PermissionsEdit=true
+```
+
+**DO NOT** use this query to decide whether to skip creation. Proceed to creation regardless of the result.
+
+### Create Custom Permission Set with FLS (ALWAYS — NO EXCEPTIONS)
+
+**UNCONDITIONALLY create the permission set.** Do NOT skip based on FLS query results. If the permission set already exists, the API will return a DUPLICATE error — treat this as success and continue to the assignment step.
+
+```text
+dispatch POST /services/data/v66.0/headless/metadata
+{
+  "type": "PermissionSet",
+  "fullName": "Insurance_Billing_Field_Access",
+  "xmlRep": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><PermissionSet xmlns=\"http://soap.sforce.com/2006/04/metadata\"><fieldPermissions><field>InsPolicyBillingInfo.BillingTreatmentId</field><readable>true</readable><editable>true</editable></fieldPermissions><fieldPermissions><field>InsPolicyBillingInfo.TaxTreatmentId</field><readable>true</readable><editable>true</editable></fieldPermissions><fieldPermissions><field>InsPolicyBillingInfo.ProrationPolicyId</field><readable>true</readable><editable>true</editable></fieldPermissions><fieldPermissions><field>InsPolicyBillingInfo.PaymentTermId</field><readable>true</readable><editable>true</editable></fieldPermissions><fieldPermissions><field>InsPolicyBillingInfo.ProductSellingModelId</field><readable>true</readable><editable>true</editable></fieldPermissions><fieldPermissions><field>InsPolicyBillingInfo.LegalEntityId</field><readable>true</readable><editable>true</editable></fieldPermissions><hasActivationRequired>false</hasActivationRequired><label>Insurance Billing Field Access</label><description>Grants FLS for InsPolicyBillingInfo billing lookup fields</description></PermissionSet>"
+}
+```
+
+**Expected responses:**
+1. **Success (new creation):**
+```json
+{
+  "results": [
+    {
+      "success": true,
+      "id": "0PS...",
+      "fullName": "Insurance_Billing_Field_Access",
+      "errors": []
+    }
+  ]
+}
+```
+
+2. **DUPLICATE_VALUE (already exists) — treat as success:**
+```json
+{
+  "results": [
+    {
+      "success": false,
+      "fullName": "Insurance_Billing_Field_Access",
+      "errors": [{"statusCode": "DUPLICATE_VALUE", "message": "..."}]
+    }
+  ]
+}
+```
+
+**In both cases, proceed to the reconciliation step.** Do NOT treat DUPLICATE_VALUE as an error — it means the permission set already exists, which is acceptable.
+
+### Reconcile Field Permissions (MANDATORY — DO NOT SKIP)
+
+**CRITICAL: When a pre-existing permission set is found (DUPLICATE_VALUE), verify it has all 6 required FieldPermissions.** A pre-existing `Insurance_Billing_Field_Access` permission set might be missing some of the required fields, which would cause Phase 7 InsPolicyBillingInfo creation to fail with INVALID_FIELD.
+
+**First, resolve the permission set ID:**
+
+```text
+dispatch GET /query?q=SELECT+Id+FROM+PermissionSet+WHERE+Name='Insurance_Billing_Field_Access'+AND+IsOwnedByProfile=false
+```
+
+**Then query existing FieldPermissions:**
+
+```text
+dispatch GET /query?q=SELECT+Id,Field,PermissionsRead,PermissionsEdit+FROM+FieldPermissions+WHERE+ParentId='<PS_ID>'+AND+SobjectType='InsPolicyBillingInfo'+AND+Field+IN+('InsPolicyBillingInfo.BillingTreatmentId','InsPolicyBillingInfo.TaxTreatmentId','InsPolicyBillingInfo.ProrationPolicyId','InsPolicyBillingInfo.PaymentTermId','InsPolicyBillingInfo.ProductSellingModelId','InsPolicyBillingInfo.LegalEntityId')
+```
+
+**For each of the 6 required fields, check the result:**
+- If the field exists with `PermissionsRead=true` and `PermissionsEdit=true`, no action needed
+- If the field exists but either permission is false, PATCH the FieldPermissions record to enable both
+- If the field is missing entirely, CREATE a new FieldPermissions record
+
+**To create missing FieldPermissions (repeat for each missing field):**
+
+```text
+dispatch POST /sobjects/FieldPermissions
+{
+  "ParentId": "<PS_ID>",
+  "SobjectType": "InsPolicyBillingInfo",
+  "Field": "InsPolicyBillingInfo.<FieldName>",
+  "PermissionsRead": true,
+  "PermissionsEdit": true
+}
+```
+
+**To fix incomplete FieldPermissions (if read or edit is false):**
+
+```text
+dispatch PATCH /sobjects/FieldPermissions/<FP_ID>
+{
+  "PermissionsRead": true,
+  "PermissionsEdit": true
+}
+```
+
+After reconciliation completes, proceed to assignment.
+
+### Assign Permission Set to Target User
+
+**MANDATORY STEP — DO NOT SKIP.** Verify assignment status and create the assignment if missing.
+
+**Then check if already assigned:**
+
+```text
+dispatch GET /query?q=SELECT+Id+FROM+PermissionSetAssignment+WHERE+AssigneeId='<TARGET_USER_ID>'+AND+PermissionSetId='<PS_ID>'
+```
+
+**If the assignment query returns 0 records, create the assignment:**
+
+```text
+dispatch POST /sobjects/PermissionSetAssignment
+{"AssigneeId": "<TARGET_USER_ID>", "PermissionSetId": "<PS_ID>"}
+```
+
+If the assignment POST returns `400 DUPLICATE_VALUE`, the user already has the permission set assigned between your query and now (treat as success). Any other error is a failure and must be reported.
+
+### Required Fields
+
+| Field | Type | Required |
+|-------|------|----------|
+| BillingTreatmentId | Lookup(BillingTreatment) | Read + Edit |
+| TaxTreatmentId | Lookup(TaxTreatment) | Read + Edit |
+| ProrationPolicyId | Lookup(ProrationPolicy) | Read + Edit |
+| PaymentTermId | Lookup(PaymentTerm) | Read + Edit |
+| ProductSellingModelId | Lookup(ProductSellingModel) | Read + Edit |
+| LegalEntityId | Lookup(LegalEntity) | Read + Edit |
+
+### Notes
+
+- The `/services/data/v66.0/headless/metadata` endpoint requires the `FileBasedMetadataCrud` org entitlement. If missing, the call returns `500 METADATA_CRUD_ERROR`.
+- PermissionSet is allowlisted for full CRUD (create, read, update, delete) via the metadata endpoint.
+- The `xmlRep` field must be a complete PermissionSet XML document following the Metadata API schema.
+- Field permissions use the format `<SobjectType>.<FieldName>` (e.g., `InsPolicyBillingInfo.BillingTreatmentId`).
+
+---
+
+## Field-Level Security
+
+Check FLS via standard SOQL.
+
+### Required FLS (Read + Edit for System Administrator)
+
+**InsurancePolicy:** OriginalPolicyId, PolicyStage, StandardCommissionAmount, TermCommissionAmount
+
+**InsurancePolicyCoverage:** OriginalCoverageId, StandardCommissionAmount, TermCommissionAmount
+
+**InsurancePolicyAsset:** OriginalAssetId, StandardCommissionAmount, TermCommissionAmount
+
+**InsurancePolicyParticipant:** OriginalParticipantId, StandardCommissionAmount, TermCommissionAmount
+
+### Query FLS
+
+```text
+dispatch GET /query?q=SELECT+Field,PermissionsRead,PermissionsEdit+FROM+FieldPermissions+WHERE+Parent.Profile.Name='System+Administrator'+AND+SobjectType='<OBJECT>'+AND+Field+IN+('<OBJECT>.<FIELD1>','<OBJECT>.<FIELD2>')
+```
+
+### Object-Level CRUD (full access needed)
+
+Objects: InsurancePolicyCoverage, InsurancePolicyAsset, InsurancePolicyParticipant, InsurancePolicySurcharge, InsurancePolicyTransaction, InsPolicyTransactionDetail, InsPolicyBillingInfo
+
+```text
+dispatch GET /query?q=SELECT+SobjectType,PermissionsRead,PermissionsCreate,PermissionsEdit,PermissionsDelete+FROM+ObjectPermissions+WHERE+Parent.Profile.Name='System+Administrator'+AND+SobjectType+IN+('InsurancePolicyCoverage','InsurancePolicyAsset','InsurancePolicyParticipant','InsurancePolicySurcharge','InsurancePolicyTransaction','InsPolicyTransactionDetail','InsPolicyBillingInfo')
+```
+
+If fields are missing access after permission set assignment, provide manual steps (Setup > Object Manager > Field > Set FLS).

package/skills/insurance-brokerage-agency-billing-configure/references/prerequisites.md

@@ -0,0 +1,142 @@
+# Phase 1: Prerequisites — Licenses & Feature Enablement
+
+## Target User
+
+Identify the authenticated user before any license or permission operations:
+
+```text
+dispatch GET /chatter/users/me
+```
+
+Returns `{ id, username, displayName, ... }`. Capture `id` as the target user ID (`<targetUserId>`) for all subsequent license and permission set assignment calls in this workflow.
+
+---
+
+## Required PermissionSetLicenses (19 total)
+
+Query all at once:
+
+```text
+dispatch GET /query?q=SELECT+Id,DeveloperName,MasterLabel,Status+FROM+PermissionSetLicense+WHERE+DeveloperName+IN+('InsuranceBrokerageFoundationPsl','InsBrokerageCmsnMgmtPsl','InsBrokeragePolicyManagementPsl','InsBillingIntegrationPsl','ContextServiceAdminPsl','ContextServiceRuntimePsl','CorePricingRunTime','BREDesigner','BRERuntime','CSVDataImportPsl','RevLifecycleMgmtBillingPsl','BillingAdvancedPsl','ProductCatalogManagementAdministratorPsl','SonicEmbeddedStorePsl','UsageDesignTimePsl','UsageRunTimePsl','DataPipelinesAddOnPsl','FSCInsurancePsl','DocGenDesignerPsl')
+```
+
+| # | MasterLabel | DeveloperName |
+|---|-------------|---------------|
+| 1 | Insurance Brokerage | InsuranceBrokerageFoundationPsl |
+| 2 | Insurance Brokerage Commission Management | InsBrokerageCmsnMgmtPsl |
+| 3 | Insurance Brokerage Policy Management | InsBrokeragePolicyManagementPsl |
+| 4 | Insurance Billing Integration | InsBillingIntegrationPsl |
+| 5 | Context Service Admin | ContextServiceAdminPsl |
+| 6 | Context Service Runtime | ContextServiceRuntimePsl |
+| 7 | Salesforce Pricing Run Time | CorePricingRunTime |
+| 8 | Business Rules Engine Designer | BREDesigner |
+| 9 | Business Rules Engine Runtime | BRERuntime |
+| 10 | CSV Basic Data Import | CSVDataImportPsl |
+| 11 | Billing | RevLifecycleMgmtBillingPsl |
+| 12 | Billing Advanced | BillingAdvancedPsl |
+| 13 | Product Catalog Management Administrator | ProductCatalogManagementAdministratorPsl |
+| 14 | Data Pipelines Base User | SonicEmbeddedStorePsl |
+| 15 | Usage Management Design Time | UsageDesignTimePsl |
+| 16 | Usage Management Run Time | UsageRunTimePsl |
+| 17 | Data Pipelines Add On User Settings | DataPipelinesAddOnPsl |
+| 18 | FSC Insurance | FSCInsurancePsl |
+| 19 | DocGen Designer | DocGenDesignerPsl |
+
+If any are missing from the org, stop and tell the user which licenses need provisioning.
+
+---
+
+## License Assignment Check
+
+Query assignments for the target user:
+
+```text
+dispatch GET /query?q=SELECT+PermissionSetLicense.DeveloperName+FROM+PermissionSetLicenseAssign+WHERE+AssigneeId='<targetUserId>'+AND+PermissionSetLicense.DeveloperName+IN+('InsuranceBrokerageFoundationPsl','InsBrokerageCmsnMgmtPsl','InsBrokeragePolicyManagementPsl','InsBillingIntegrationPsl','ContextServiceAdminPsl','ContextServiceRuntimePsl','CorePricingRunTime','BREDesigner','BRERuntime','CSVDataImportPsl','RevLifecycleMgmtBillingPsl','BillingAdvancedPsl','ProductCatalogManagementAdministratorPsl','SonicEmbeddedStorePsl','UsageDesignTimePsl','UsageRunTimePsl','DataPipelinesAddOnPsl','FSCInsurancePsl','DocGenDesignerPsl')
+```
+
+For each missing license, assign it:
+
+```text
+dispatch POST /sobjects/PermissionSetLicenseAssign
+{"AssigneeId": "<targetUserId>", "PermissionSetLicenseId": "<licenseId>"}
+```
+
+---
+
+## Feature Enablement
+
+Each feature is an independent **read current state → write → verify (re-read)** cycle. Enable in the order below — dependencies are strict.
+
+### 1. Context Service
+
+**Read:**
+```text
+dispatch GET /connect/contextservice/access/contextServiceEnabled/contextServiceEnabled
+```
+Returns `{ isEnabled: boolean, uniqueIdentifier: "contextServiceEnabled" }`.
+
+**Enable (if `isEnabled` is false):**
+```text
+dispatch PUT /connect/contextservice/access/contextServiceEnabled/contextServiceEnabled
+{"isEnabled": true}
+```
+
+**Verify:** re-read. Confirm `isEnabled` is `true`.
+
+> NOT writable via `/setup/org/preferences/` — use the Context Service Connect endpoint only.
+
+---
+
+### 2. Brokerage (requires Context Service to be on first)
+
+**Read:**
+```text
+dispatch GET /setup/org/preferences/InsBrokerageEnabled
+```
+Returns `{ isPreferenceEnabled: boolean }`.
+
+**Enable (if `isPreferenceEnabled` is false):**
+```text
+dispatch PATCH /setup/org/preferences/InsBrokerageEnabled
+{"desiredState": true}
+```
+
+**Verify:** re-read. Confirm `isPreferenceEnabled` is `true`.
+
+> Enabling Brokerage triggers server-side seeding of default brokerage metadata records.
+
+---
+
+### 3. Billing (requires Brokerage to be on first)
+
+**Read:**
+```text
+dispatch GET /headless/invoke/platform/billing-settings/get-billing-general-setting-states
+```
+Inspect `BillingEnabled` key in the returned map.
+
+**Enable (if `BillingEnabled` is false):**
+```text
+dispatch PATCH /headless/invoke/platform/billing-settings/set-billing-setup-enabled
+{"billingOrgPrefValue": true}
+```
+
+**Verify:** re-read. Confirm `BillingEnabled` is `true`.
+
+---
+
+### 4. Salesforce Pricing
+
+**Read:**
+```text
+dispatch GET /setup/org/preferences/CorePricingPreference
+```
+Returns `{ isPreferenceEnabled: boolean }`.
+
+**Enable (if `isPreferenceEnabled` is false):**
+```text
+dispatch PATCH /setup/org/preferences/CorePricingPreference
+{"desiredState": true}
+```
+
+**Verify:** re-read. Confirm `isPreferenceEnabled` is `true`.

package/skills/life-sciences-fieldsalesrep-coordinate/SKILL.md

@@ -130,9 +130,10 @@ Before presenting the workflow, establish which org to use. Do this **every time
 
 2. **Ask for confirmation**: "Ready to begin the full Life Sciences Cloud setup? (yes/no)"
 
-3. **Download the shared source folder ONCE (MANDATORY — hard gate, before any stage).** Both Stage 2 (Starter Config Deploy — metadata + config records) and Stage 5 (Sample Visit Creation — Data CSVs) read from `.lsc-starter-config/LSStarterConfig/`; those stages do NOT download or delete it — the orchestrator owns a single download here and a single delete in Phase 8. Sparse-checkout only that subtree (the repo is large) into the CWD:
+3. **Download the shared source folder FRESH (MANDATORY — hard gate, before any stage).** Both Stage 2 (Starter Config Deploy — metadata + config records) and Stage 5 (Sample Visit Creation — Data CSVs) read from `.lsc-starter-config/LSStarterConfig/`; those stages do NOT download or delete it — the orchestrator owns one fresh download here and a single delete in Phase 8. **Always re-pull — never reuse an existing folder** (a stale copy could serve outdated CSVs, silently defeating Stage 5's "create strictly from the current CSV" rule, or skip newly added components). Delete any pre-existing `.lsc-starter-config` first, then sparse-checkout only that subtree (the repo is large) fresh into the CWD:
 
    ```bash
+   rm -rf .lsc-starter-config lsstarter-tmp
    git clone --no-checkout --depth 1 --filter=blob:none \
      https://github.com/SalesforceLabs/LSStarterConfig.git lsstarter-tmp
    cd lsstarter-tmp && git sparse-checkout init --cone \
@@ -140,7 +141,7 @@ Before presenting the workflow, establish which org to use. Do this **every time
    mv lsstarter-tmp/Codey ./.lsc-starter-config && rm -rf lsstarter-tmp
    ```
 
-   > `.lsc-starter-config/LSStarterConfig/` contains its own `sfdx-project.json` (pins `sourceApiVersion: 65.0`) — the deploy step (Phase 3) must run from inside it. If the folder already exists in the CWD (from a prior run), reuse it (skip the download).
+   > `.lsc-starter-config/LSStarterConfig/` contains its own `sfdx-project.json` (pins `sourceApiVersion: 65.0`) — the deploy step (Phase 3) must run from inside it.
 
 4. **Download gate — verify the folder exists before proceeding.** Confirm the download succeeded by checking that `.lsc-starter-config/LSStarterConfig/sfdx-project.json` and `.lsc-starter-config/LSStarterConfig/Data/` are present (e.g. `ls .lsc-starter-config/LSStarterConfig/sfdx-project.json .lsc-starter-config/LSStarterConfig/Data`).
    - If present → set `sourceFolderDownloaded: true` in `OrchestrationState` and proceed to Phase 2.

package/skills/life-sciences-fieldsalesrep-coordinate/references/stage-5-visit-creation-execution-state-and-recovery.md

@@ -103,8 +103,6 @@ Step <N>/16 FAILED: <StepName>
 | Territory query returns no results | Territory model may not be Active — direct user to `life-sciences-territory-configure` |
 | `FIELD_INTEGRITY_EXCEPTION` on PlaceId in Visit | ContactPointAddress must be linked to the same Account; verify ParentId matches |
 | `INSUFFICIENT_ACCESS` creating ObjectTerritory2Association | This object may require admin access — if rep fails, create this specific record as admin and document the exception |
-| Account active flag | Use the standard `IsActive` (boolean), NOT `IsActive__c`. If the rep lacks FLS to it, omit and set as admin |
-| `Unable to create/update fields: NationalProviderIdentifier` on HealthcareProvider | FLS — rep lacks access. Omit NPI and IsSpeaker (not needed for visit); admin can set later |
 | `entity type cannot be inserted: Object Territory Association` (Step 5) | Rep lacks "Manage Territories"; create as admin (or skip — nothing downstream needs it) |
 | `No such column 'ProductCode' on Product2` (Steps 7–8) | Rep has no create permission on product master data. Create Steps 7–9 as admin |
 | Date format rejected | Use ISO 8601: `YYYY-MM-DDTHH:MM:SS.000+0000` for datetime, `YYYY-MM-DD` for date |
@@ -183,6 +181,8 @@ After all records are created, display this block (substituting the actual IDs a
 |-----------|-----------|
 | **Require `.lsc-starter-config/LSStarterConfig/` to already be present in the CWD; do NOT download or delete it** | The shared folder's download/cleanup is owned by the coordinator (`life-sciences-fieldsalesrep-coordinate`) — one download at start, one delete at end |
 | **Read the `.lsc-starter-config/LSStarterConfig/Data/` CSV for each object and use ONLY its values** — read at execution time, one record per row; never hardcode field values from this stage or reuse values from a prior run | The CSVs are the single source of truth and may change between runs; illustrative values in the steps can be stale |
+| **Build `--values` strictly from the row's CSV columns; only these non-CSV values are permitted** — (a) runtime FK IDs threaded from a prior create, (b) an org-resolved ID (RecordTypeId — including the Product2 RecordType resolved via `DeveloperName='LSC_Sample'`, whose CSV value is a foreign Id — Territory2Id, the Product2/LifeSciMarketableProduct natural-key map), (c) the generated `PlannedVisitStartTime` (NOW). Anything else is a violation. **On recovery, re-`cat` the CSV — never resume from remembered/hardcoded values** | Recovery must not silently reintroduce hardcoded literals; the closed set keeps every field either CSV-sourced or a documented runtime/resolved ID |
+| **Post-create reconciliation:** for every object in Steps 2–13, records created this run == data rows in that object's CSV; the product chain (`product2.csv`, `lifescimarketableproduct.csv`, `productterritoryavailability.csv`, `providervisitproddetailing.csv`, `providervisitproddiscussion.csv`) is multi-row — verify none were dropped. If a count is short, STOP before Phase 5 and report object/expected/actual | Catches the "created 1 of N" regression where only the first product row is created and the rest are silently dropped |
 | Create the **visit records** (Account, HealthcareProvider, ContactPointAddress, ProviderAcctTerritoryInfo, Visit, ProviderVisit, detailing, discussion) as the Sales Rep | Visit ownership must be the field rep for realistic field sales workflows |
 | Create **territory associations (Step 5), product master data (Steps 7–9), and metadata cache (Steps 14–15) as the admin** | The LSC Custom Profile has no create permission on ObjectTerritory2Association, Product2, or LifeSciMarketableProduct; metadata cache records are admin-managed |
 | Ask for rep credentials — never assume | Security; credentials vary per org |
@@ -191,6 +191,6 @@ After all records are created, display this block (substituting the actual IDs a
 | Create records in exact order 2→15, then run the manual iPad validation (Step 16) last | Later records reference earlier IDs (Account→Visit→ProviderVisit); the metadata cache (14–15) must exist before the app can sync the Visit |
 | Step 16 (iPad validation) is **manual** — show the rep credentials (ask for the password if unknown; never use admin creds), give the instructions, and never claim it is done without the user's explicit "yes" | It requires a human with a physical iPad or simulator, logged in as the rep; the skill cannot verify app visibility programmatically |
 | Treat a "yes" on the Step 16 prompt as the end of the LSC setup; on a reported issue, run the troubleshooting checks (territory assignment, ProviderAcctTerritoryInfo, metadata cache freshness) before re-asking | Confirms the end-to-end setup actually works on the device the rep uses |
-| Product2 must NOT have a RecordType | Explicit requirement — no record type for Product2 |
+| Product2 `RecordTypeId` is org-resolved | `product2.csv` holds a foreign RecordTypeId; resolve the target org's `Product2` RecordType with `DeveloperName='LSC_Sample'` and use that Id instead |
 | Show diagnosis on every failure | User needs to understand what went wrong without investigating CLI output |
 | Wait for user decision on failure — no silent skips | User controls recovery path |