@engineeros/connector 1.52.0 → 1.52.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -491,13 +491,15 @@ A project can schedule a test command on the Quality page (**CI and schedules**)
491
491
 
492
492
  Bug Hunter tests a running test environment of the project (`bug_hunt.session`). The coding agent writes test cases; the connector runs them in a browser, with no model involved, so a recorded case is re-run on every new version for free. The connector does not need the project's code: a connector paired in an empty folder hunts from the project's EngineerOS artifacts.
493
493
 
494
- Set up the browser once on the hunt host:
494
+ Both repository connectors and dedicated hunt hosts automatically set up Playwright and check the browser after connecting. They reuse working Google Chrome or Microsoft Edge, or download the Chromium version required by their managed Playwright tool. Bug Hunter becomes ready only after the browser starts successfully.
495
+
496
+ To retry browser setup manually, use the same workspace as the connector:
495
497
 
496
498
  ```bash
497
- engineeros-connector tools setup playwright
499
+ engineeros-connector tools setup playwright --workspace PATH
498
500
  ```
499
501
 
500
- The case runner uses that tool's Playwright with installed Google Chrome, then Microsoft Edge, then Playwright's own Chromium (`npx playwright install chromium`).
502
+ On Linux, missing Chromium system libraries require administrator access. At a terminal, setup asks for your password; otherwise it prints the exact installation command to run. Download or launch failures are reported and can be retried with the command above. Installing the npm connector package alone does not download a browser; the connected workspace setup does.
501
503
 
502
504
  - **Catalogue runs** execute the recorded cases. A failure is run twice more from a fresh start: failing all three times it is reproduced, otherwise flaky.
503
505
  - **Hunts** run one agent turn in `.engineeros/bug-hunt/<session>/`. The agent writes each scenario as a case file in `cases/` and probes a draft with `node .engineeros/bug-hunt/<session>/probe.mjs <case file>`, which runs it through the same runner. Case files that cannot be read get one correction turn. The connector registers the cases with EngineerOS, which refuses duplicates, then runs each one.