admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: analyze returned live probe evidence

Browse Source
This commit is contained in:
zhaoyilun
2026-07-10 13:11:42 +08:00
parent 81f23a6a54
commit b2ce7b0e36
6 changed files with 279 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/source-discovery/2026-07-10-send-message-connector-selection.md
View File

@@ -124,3 +124,17 @@ Because R5 did not select a connector:
- R6 production send implementation is blocked.
- R7/R8 send-file work is also blocked behind the send-message connector and upload/file-transfer evidence.
- The project should pause write-side implementation and request one of the evidence packages above.
## R5b update from returned live probe
The later returned live-probe package is documented in `docs/source-discovery/2026-07-10-returned-live-probe-analysis.md`.
It changes this R5 conclusion from “waiting for any connector evidence” to “connector evidence exists, but production send remains blocked”:
- B-route runtime discovery now passes for a real x86 `IMPlatformClient.exe` `4.1.2.6842` process.
- The live install contains the expected B-route DLL candidates.
- A-route UIA selectors for search, draft editor, send button, and file-send menu are visible.
- Runtime send entrypoint reachability and success/ack mapping are still unproven.
- The captured chat windows show an offline-send blocker.
The next node is therefore R6a/C31 non-mutating send connector preflight, not R6 production send.