Daybreak / passive context probeTelemetry armed

One click. One context handoff.

This page prepares the parser-valid psdebugwebview:?url=… navigation to an inert same-origin landing page. It performs no automatic launch, WebGL creation, GNM request, memory corruption, or exploit stage.

Origin evidenceInitial browser page; expected NKWebProcess. User agent, feature surface, load events, and timestamps are recorded here.
Destination evidenceDebug WebContext candidate. URI parsing is statically established; FW13 browser-broker acceptance and live child identity remain unverified.
Attempt IDreading server token…

Canonical parser-valid route

Correct JIT GOT decoding proves the query key is url; ParseUrlGeneric accepts an empty command. The landing URL is percent-encoded into the single minimal form below.

Established grammar: psdebugwebview:?url={ENCODED_URL}
Fixed safe destinationbuilding same-origin URL…
Resolved launch URIbuilding parser-valid URI…
Only the parser and ShellUI dataflow are statically established. FW13 browser-broker acceptance and the live destination executable/PAID are still the evidence targets.
Launch passive landing page One explicit click; no timer, reload loop, iframe, or retry.

This page’s telemetry

  • Lifecycle telemetry started before the page body parsed.

Evidence boundary: reaching the landing page shows that the canonical URI delivered its URL. Confirming SecureWebProcess.self on FW13 still requires independent live process/PAID evidence.