JMISJUSTME · 32
JM Access Mesh · Additive host adapter · CP01

Browser contact.
Not browser control.

A real browser-capability bench for JM ECOSTATE on phone, Fold and desktop. This is an additional carrier beside the existing MCP and Android routes; no JM body is replaced.

UNTESTED — CONTACT OPEN
Route A · Existing website

Public ECOSTATE

Canonical public front door. Opening this proves navigation only, not authenticated site operations.

jmisjustme-estate.pages.dev

Open Estate
Route B · Existing source

JM GitHub

Repository contact can be made with the connected GitHub app; the website path is independent.

JMisJustMe/JM-cading-lab

Open repository
Owner-authorised website permissions

Use the setting you've already found

In ChatGPT → Browser → Specific websites → Add website, select an appropriate permission for the exact site. Only you can change that setting. This page cannot inspect or grant ChatGPT Browser permissions.

Canonical sitehttps://jmisjustme-estate.pages.dev

Suggested: use Automatic unless a site-specific rule is necessary. Prefer approval for sensitive operations.

Source hosthttps://github.com

Grant only what you actually want the browser to do. Repository tool access is a separate permission system.

Cloudflare / Render dashboardsAdministrative sessions are higher risk. Keep explicit approval for deployment, deletion, configuration or billing changes.

Browser setting ≠ MCP tool execution ≠ Android native execution ≠ owner-device acceptance.

Route C · Browser engine self-contact

32-cycle live contact run

Runs 32 fresh actual message round trips to a dedicated Web Worker and 32 IndexedDB write→read checks on this page's origin. Failures are reported as HOLD, not converted into simulated passes. No external network calls, passwords or token collection.

—
Worker messages / 32
—
IndexedDB cycles / 32
OPEN
Re-entry evidence

No browser runtime contact has been attempted on this origin.

Technical trace and limits
Not run.
CP02 · Additive network and MCP relay

Prove remote source contact

Make one user-triggered, read-only cross-origin HTTPS request to your existing GitHub repository, compare the returned Git blob identity with a pinned known-good file, and prepare an independent capsule for the connected JM Build Mesh. No credentials, URL forwarding, or automatic write actions.

api.github.com/repos/JMisJustMe/JM-cading-lab

OPEN
External source contact
OPEN
Exact source identity
HOLD
Hosted MCP receipt

The remote network gate has not been attempted in this session.

Network contact and capsule trace
Unattempted.

MCP is a separate host route: only a real connected ChatGPT tool invocation can close that gate. Preparing a capsule does not imply that an MCP received it.

What a pass actually means

  1. Worker PASS: a real Web Worker on this browser/origin returned the expected data 32 times; this does not prove the protected CP04's five-worker system.
  2. IndexedDB PASS: browser storage wrote and read 32 independently identified records during this run; it does not prove crash recovery or another application's storage.
  3. Re-entry: a later page load can read the previous checkpoint. Reload the page to check. This is not a substitute for a physical Fold screenshot or a full crash test.
  4. Permission HOLD: this page cannot detect ChatGPT's site permission, logged-in status, background browser automation or MCP use; those require their own contact and receipt.

SOURCE → SIGNAL → CONTACT FIELD → ROUTE PRESSURE → STATE CHANGE → DING → TRACE → RECOVERY → OUTPUT