# ChatGPT Orchestrator Baseline Qualification — 2026-08-20

This receipt records the qualification state of the baseline orchestration/executor stack before implementation of the separate Execution Continuity program.

## Repository gate

Isolated host: `debian2`.

Command:

```text
pnpm install --frozen-lockfile
pnpm gate
```

Result: PASS.

Covered test counts in the final gate:

```text
protocol                 4 passed
ChatGPT DOM adapter      7 passed
persistence              3 passed
core                     5 passed
extension                5 passed
MCP/executor bridge      4 passed
```

TypeScript typecheck and all workspace builds passed before and after the test run.

## Firefox executor qualification

Isolated host: `debian3`.
Browser: stock Firefox 154.0 in an isolated temporary profile.
Installation: temporary `web-ext` extension load; no workstation browser/profile involved.

Result: PASS.

Receipt fields:

```text
hello: true
inspectAck: true
unmanagedRejected: true
createAck: true
managedTabCreated: true
browser: firefox
```

This proves authenticated executor startup, command acknowledgement, unmanaged-tab fail-closed behavior, and managed ChatGPT tab creation without requiring a real account or private conversation content.

## Chromium compatibility qualification

Isolated host: `debian1`.
Browser: Chromium 150 in an isolated profile.

Result: PASS for Chromium compatibility shell.

Verified:

```text
Manifest V3
background service worker loads
Chromium options page loads
Chromium LNA onboarding section is visible
Allow local executor access control is present
loopback HTTP onboarding host permissions are Chromium-only
```

Chromium 142+ requires a user Local Network Access grant before a service worker may use the loopback executor. The browser platform does not allow the background service worker itself to create that permission prompt reliably. Production onboarding therefore uses the active extension options page and its **Allow local executor access** control. The Firefox build does not request those Chromium-only loopback HTTP host permissions.

The compatibility qualification does not bypass or disable this browser permission boundary.

## Package validation

Firefox `web-ext lint --warnings-as-errors`: PASS, zero errors/notices/warnings.

Final local paired artifact hashes at qualification time:

```text
Firefox XPI  706dfe9f4f3e6c96555d30226e6bd6b8031e00cdf87da898de45d1b5b53385d7
Chromium ZIP 9f1c60b4daa2015c642b7b873ca052a1b3d5bfa52dc6033b92f60fe731f07746
Agent Skill  6067c24bd78c69b27e6a01e5d110081309e14ce6372dd07d01a9879c18c29cb6
```

The paired Firefox XPI contains the local executor credential and is private deployment material; only its hash is recorded here.

## Local runtime/tunnel

`chatgpt-orchestrator.service`: active.

Local listeners:

```text
http://127.0.0.1:8764/mcp
ws://127.0.0.1:8765
```

`chatgpt-orchestrator-tunnel.service`: active.

OpenAI `tunnel-client doctor`: all checks PASS, including MCP reachability. Tunnel readiness endpoint: `ready`. Tunnel startup successfully initialized an MCP session with `@platform-modules/chatgpt-orchestrator-mcp`.

## LibreWolf deployment boundary

The final paired XPI is staged at the active LibreWolf profile extension path and matches the Firefox artifact hash above.

No LibreWolf restart was performed as part of this final qualification. Browser activation/reload of the newly staged XPI is deliberately left to the user. Until that reload occurs, `/healthz` may correctly report `executor.connected=false` even though the staged extension artifact is current.