slnodejs 6.2.62 → 6.2.63

package/README.md

@@ -159,3 +159,27 @@ If you encounter issues:
 - You're working in a dedicated development environment
 - You want to reduce command verbosity
 - You're setting up CI/CD pipelines where all Node.js executions should include the preloader and Sealights Agent
+
+---
+
+## Integration Tests
+
+PRs to `main` automatically trigger the JS Agent Integration Tests, which validate the agent works correctly with the plugins and example apps across Node.js 18, 20, and 22.
+
+The tests are defined in [`SL.JavaScript.AgentTests`](https://github.com/Sealights/SL.JavaScript.AgentTests) and run via a reusable workflow (`validate-agent.yml`).
+
+### Cross-Repo Branch Resolution
+
+When working on a feature that spans multiple repos, create branches with the **same name** across repos. The CI automatically detects matching branches and tests them together.
+
+For example, if your PR branch is `feature/new-scanner` and a branch with the same name exists in the Plugins or ExampleApps repos, the integration tests will use those branches instead of the defaults.
+
+This is handled via the `feature-branch` input — see the [AgentTests README](https://github.com/Sealights/SL.JavaScript.AgentTests#cross-repo-branch-resolution) for details.
+
+### Manual Dispatch
+
+You can also trigger integration tests manually via the **Actions** tab → **JS Agent Integration Tests** → **Run workflow**, with options for:
+
+- `plugins-branch` — test against a specific plugins branch
+- `feature-branch` — try this branch in every repo (falls back to defaults where not found)
+- `node-versions` — JSON array of Node.js versions to test

package/browser-agent/dist/browser-agent-all.js

@@ -1093,7 +1093,7 @@ var __awaiter = this && this.__awaiter || function (thisArg, _arguments, P, gene
     value: true
   });
   exports.SL_AGENT_TYPE = exports.SL_AGENT_VERSION = void 0;
-  exports.SL_AGENT_VERSION = '6.2.62';
+  exports.SL_AGENT_VERSION = '6.2.63';
   exports.SL_AGENT_TYPE = 'browser';
 });