browser-pilot-cli 0.4.0 → 0.5.0
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 +259 -406
- package/dist/cli.js +1089 -2550
- package/dist/daemon.js +125 -172
- package/docs/architecture/browser-pilot-platform-spec.md +443 -1047
- package/docs/plans/browser-capability-evolution.md +6 -6
- package/docs/plans/profile-context-routing.md +1 -1
- package/docs/plans/universal-agent-integration.md +121 -348
- package/docs/releases/v0.5.0.md +93 -0
- package/package.json +2 -8
- package/docs/integration/stdio-bridge.md +0 -694
- package/docs/integration/stdio-conformance.md +0 -51
- package/scripts/run-stdio-conformance.mjs +0 -698
|
@@ -1,51 +0,0 @@
|
|
|
1
|
-
# Stdio Conformance Suite
|
|
2
|
-
|
|
3
|
-
The stdio conformance suite verifies an embedded Browser Pilot executable as a
|
|
4
|
-
black box. It launches the exact command supplied by the integrator, exchanges
|
|
5
|
-
only newline-delimited JSON-RPC 2.0 over stdin/stdout, and imports no Browser
|
|
6
|
-
Pilot source or protocol modules.
|
|
7
|
-
|
|
8
|
-
Build and test the repository executable:
|
|
9
|
-
|
|
10
|
-
```bash
|
|
11
|
-
npm run build
|
|
12
|
-
node scripts/run-stdio-conformance.mjs
|
|
13
|
-
```
|
|
14
|
-
|
|
15
|
-
An installed package also exposes the same runner as
|
|
16
|
-
`browser-pilot-conformance`.
|
|
17
|
-
|
|
18
|
-
Test an executable or product-bundled adapter with its exact arguments. The
|
|
19
|
-
command after `--` is passed directly to the operating system without a shell:
|
|
20
|
-
|
|
21
|
-
```bash
|
|
22
|
-
node scripts/run-stdio-conformance.mjs -- \
|
|
23
|
-
/absolute/path/to/browser-pilot bridge --stdio
|
|
24
|
-
```
|
|
25
|
-
|
|
26
|
-
Use `--report <path>` to write the same JSON report printed to stdout, and
|
|
27
|
-
`--timeout-ms <value>` to change the per-operation timeout. A passed suite exits
|
|
28
|
-
with status 0, a conformance failure exits with status 1, and invalid runner
|
|
29
|
-
arguments exit with status 2.
|
|
30
|
-
|
|
31
|
-
The suite creates one transient Workspace, one renewable Lease, and one managed
|
|
32
|
-
`about:blank` target. It does not enumerate or control user tabs. It validates:
|
|
33
|
-
|
|
34
|
-
- initialization and capability negotiation;
|
|
35
|
-
- tool manifest discovery;
|
|
36
|
-
- Workspace, Lease, and heartbeat lifecycle;
|
|
37
|
-
- managed target creation and inventory;
|
|
38
|
-
- a bounded Observation;
|
|
39
|
-
- screenshot creation, protected Artifact access, and release;
|
|
40
|
-
- event cursor polling;
|
|
41
|
-
- explicit target, Lease, Workspace, and bridge cleanup.
|
|
42
|
-
|
|
43
|
-
Failures trigger best-effort cleanup of only the resources created by the
|
|
44
|
-
suite. The versioned report contains check outcomes, counts, timings, version
|
|
45
|
-
metadata, and a bounded error summary. It intentionally omits opaque resource
|
|
46
|
-
IDs, Artifact paths, browser content, and bridge stderr text.
|
|
47
|
-
|
|
48
|
-
The repository tests exercise the runner against an independent fake stdio
|
|
49
|
-
executable, so normal unit tests do not connect to Chrome. Running the suite
|
|
50
|
-
against the real executable requires a ready supported browser and may start or
|
|
51
|
-
reuse the per-user Browser Pilot daemon.
|