PXIL Automation Runtime Diagram

pytest runs selected tests; flow code controls Selenium and Chrome, which interacts with the remote Pratyay UI.
Pratyay login fills credentials and pauses for manual CAPTCHA entry before submission (tests/regression/auth.py:46-122).
Arrows describe control and I/O; results return to pytest. No direct backend API or database integration is asserted.

Root config.json selects setup products and session/token actions; config/runtime.json selects regression environment, role, product and flow.
Bidding supports Excel/JSON grids, files and folders. Optional parallel folder workers create their own browsers (bidding flow:551-587).
Matching requires the exchange role; rejected or unsupported bid-transfer status stops matching (matching flow:28-44, 123-135).

Boundaries show host/process and remote ownership, not verified network isolation or firewall policy.
Credentials come from local JSON and are entered into remote login forms. Values and endpoint addresses are omitted.
Chrome/WebDriver is an external runtime dependency. Pratyay and MCO server internals and transport guarantees are outside the observed source.
MCO is an independent, enabled-only dashboard login test; no Pratyay-to-MCO backend connection is inferred.

StepActions requests browser screenshots; pytest hooks attach evidence and configure pytest-html. Reports live under reports/.
Matching configures browser downloads separately; setup can save session backups. These details are kept off the main path.
Snapshot: clean repository at 5ab89ce0059525b31558a1fa82251a2a6f610dd7. Sources use local-only links.
Registered reports/order-book/trade-book markers are placeholders, not implemented runtime services (RUN_COMMANDS.md).