Browser and Replay Rules

Single Tab Rule

Use one claimed Chrome tab for the full run. Do not open Salesforce, OrderDesk, Packiyo, or Katana in separate tabs. Navigate the same tab in this order:

1. Salesforce Item Manager: https://exodus--safin.sandbox.lightning.force.com/lightning/n/Item_Bulk_Editor
2. Salesforce Purchase Order Pipeline: https://exodus--safin.sandbox.lightning.force.com/lightning/n/Purchase_Order_Pipeline
3. OrderDesk orders
4. Packiyo sandbox dashboard
5. Katana factory home

The browser policy is saved in the manifest as browser.mode = single-active-chrome-tab.

Do not use standard object creation URLs such as /lightning/o/Item__c/new or /lightning/o/Purchase_Order__c/new for this E2E.

Manifest

The manifest is the replay contract. It stores generated names, created Salesforce IDs, provider references, phase status, and the next resume marker.

Important fields:

Replay Events

The harness writes sanitized events to .artifacts/e2e/safin/<run-label>/events.jsonl. It omits screenshot/image payloads and records step starts, skipped planned steps, resolved UI targets, action results, assertion queries, and errors.

The stricter Playwright contract lives at .artifacts/e2e/safin/<run-label>/ui-replay-playwright-plan.json. Every browser step should include at least one executable selector, field value, click target, or assertion. Prose-only notes are not enough for replay.

Quote approval replay must enter the submission flow before any approval or rejection action is attempted. Record these exact inputs in the strict plan:

Sales Order payment replay must then verify token reuse instead of always saving a new card:

3PL inventory replay no longer creates or resolves Inventory Sync Audit records. Provider-owned stock is asserted on Inventory__c:

For the OrderDesk to Packiyo sandbox bridge, replay these exact controls:

On the Packiyo Pack Orders page, do not click the blue order-number link. That link opens the order edit page. Click the table row itself, or navigate to the row's packing_url, for example:

const row = page.locator('tr[role="row"]').filter({ hasText: 'SO-011654-10C97805B2' }).first();
await row.click({ position: { x: 20, y: 20 } });
await expect(page).toHaveURL(/\\/packing\\/single_order_shipping\\/19176/);

If the row is not visible, use the equivalent direct route: https://sandbox.app.packiyo.com/packing/single_order_shipping/<packiyoOrderId>.

For Packiyo cleanup and real packing, replay must scope row actions by exact SKU text before clicking cancel/uncancel controls. The exploration accidentally cancelled E2E-NIC-12T163353Z-FG-BI9 once and immediately uncancelled it, which is now recorded as a failure mode. Use row-scoped locators:

const row = page.locator('tr, .row, [role="row"]').filter({ hasText: sku }).first();
await row.locator('button[title*="Cancel"], a[title*="Cancel"], button:has-text("Cancel")').first().click();

The current Packiyo inventory import replay data is:

Packiyo Stock Creation

When Packiyo reports order 19176 / SO-011654-10C97805B2 as backordered, the replay should try the native PO path before CSV import:

The current Chrome exploration reached the populated backorder rows, but warehouse selection and subsequent save could not be completed because Packiyo's Select2 field needed text/dropdown input after showing Please enter 1 or more characters, and the Chrome extension reported the Browser Use virtual clipboard was not installed for text entry. The working fallback is the Salesforce managed Packiyo provider account, not the local .env.safin.local token. Managed auth resolved TEST LOCATION as id 318 under warehouse Primary id 40; POST /api/v1/products/{productId}/inventory with { "location_id": 318, "quantity": 120 } cleared the three physical backorders.

Packiyo Shipment Creation

After stock cleared, the strict replay can create the sandbox shipment through the Packiyo API when the packing UI is unavailable:

The completed provider writeback replay for SO-011654 has these exact steps:

The replay harness currently wraps the Salesforce writeback with SalesOrderTriggerHandler.pushRuntimeFinancialAuditBypass() and DataImportRuntimeGuard.push() to keep nonessential financial-audit and customer-email side effects out of the heavy fulfillment transaction. A production fix for FulfillmentOrderUpdateService.updateOrderRecord is local, but Apex deploy 0AffY000004C0bRSAS failed because the sandbox org exceeds the 6,000,000 Apex character limit.

Safety Gates

Mutating Salesforce and provider-app steps require:

--allow-mutations

Payment submission or payment-like approval actions require:

--allow-payment-submit

The setup command also requires --allow-mutations because it inserts fake Vendor Accounts and fake internal Warehouses.

Resume

Use the failed step ID from events.jsonl or manifest.resume.nextStepId.

npm run e2e:safin:resume -- --from quote-reject-approve-sync --allow-mutations

After an LWC fix, run the focused Jest test, deploy the changed metadata, then resume without changing the run label. This preserves provider references and keeps the generated data set linear.

Future Recording Placement

Place screen recordings and still evidence in:

docs/evidence/safin-e2e/<run-label>/

Use filenames that start with the step ID, for example quote-reject-approve-sync-approval-modal.mov.