# Independent 182aee93 native reconnect and ordinary send

Actual app head: `182aee9334edacb5291b7b13a8ee43deb5fb4b92`.
Windows Default-desktop capture completed 2026-10-21T22:35:30Z in an explicitly
authorized hands-off slot. Only the exact owned app window was captured.

This is the independent `182aee93` app with an owned synthetic loopback Gateway and a
throwaway profile. It is not the installed Hub or Gateway, a real model/provider,
paired-node/MXC proof, or the earlier combined `2dcf` preflight.

Native UIA selected Fixture Research and its research conversation. The actual
WebSocket connection closed/reconnected while agents.list was held; the
selector was disabled pending the fresh roster. After release, the same native
assistant and conversation were selected. The driver typed into the ordinary
ChatComposerInput via ValuePattern and invoked ChatComposerPrimaryAction. It
did not call app.chat.send and supplied no explicit send-thread override.

The owned Gateway's actual safe request record reports chat.send for
`agent:research:fixture-other`, outcome ok. A controlled fixture reply was then
published and rendered in that conversation. No provider was contacted.

All visible content is synthetic fixture data. Inspection found no endpoint,
credential, phone number or real user information in the three window frames,
so no pixel mask was needed. PNG metadata was removed and every RGBA channel
was compared to the original: pixels are unchanged. Public diagnostics are
field-selected and contain no endpoints, auth values, user paths or raw profile.

The exact app PID 29172 exited and was independently verified absent immediately
after capture. The desktop slot was released before media inspection or
publication. See runtime-diagnostics.json and proof-manifest.json for actual
UIA selection, routing, binary/image hashes and cleanup timing.