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

feat: add send connector preflight probes

Browse Source
This commit is contained in:
zhaoyilun
2026-07-10 13:37:08 +08:00
parent b2ce7b0e36
commit 1f99681348
11 changed files with 1307 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source-discovery/2026-07-10-send-sidecar-b-first-plan.md
View File

@@ -344,16 +344,18 @@ connector_stage = "preview" | "sandbox_send" | "production"
## Next implementation loop
R5b/C30-live returned-probe intake is now complete. The live probe confirmed a running x86 `IMPlatformClient.exe` `4.1.2.6842`, installed B-route candidate DLLs, and A-route UIA controls, but it did not prove runtime send entrypoint reachability. It also observed an offline-send blocker in the captured chat windows.
R6a/C31 non-mutating send connector preflight is now complete. WinHelper `0.4.0` adds read-only `probe_send_entrypoints` and `probe_send_uia_controls`; the live recorder now emits `send_entrypoints_preflight.json` and `send_uia_controls_preflight.json`; copied install metadata reports all required B-route entrypoints available; and the UIA classifier can report offline-blocked state.
Next node should be **R6a/C31 non-mutating send connector preflight**:
Next node should be **R6b B-route preview/dry-run contract**:
1. Use the C# WinHelper read-only op `probe_client_runtime`.
2. Add or run `probe_send_entrypoints` against copied/installed binaries to confirm `SendTxtMessageByJid`, `MessageScheduling.SendChatMessage`, `Chat.SendMessage`, and file-upload/file-message candidates by metadata only.
3. Add or run a UIA preflight classifier for `skinAlphaTxt`, `rtbSendMessage`, `btnSend`, `发送文件`, and offline-send message state.
4. Do not send, click, type, upload, attach hooks, or capture network traffic in this node.
5. Update `capability-source-matrix.md` after B2/A-route preflight passes or fails.
1. Keep `isphere_send_message` in preview/dry-run only.
2. Resolve target refs from existing contact/group search output.
3. Validate `content_sha256` and `idempotency_key`.
4. Return connector metadata such as `connector="implatform-sidecar"` and `connector_stage="preview"`.
5. Append a local audit event for preview attempts.
6. Do not send, click, type, upload, attach hooks, or capture network traffic in this node.
7. Keep the later online-only sandbox-send gate separate.
## Current status
B is selected as the primary send/file-send route. The first non-mutating runtime probe has now been run against a real logged-in environment through the returned live-probe package. B can continue only through non-mutating entrypoint confirmation; A remains the fallback and now has concrete UIA selector evidence, but production send remains blocked until dry-run/idempotency/audit and sandbox-send evidence exist.
B is selected as the primary send/file-send route. Runtime discovery and entrypoint metadata preflight have passed enough to continue to preview/dry-run design. A remains the fallback and now has concrete UIA selector/offline-blocker classifier support. Production send remains blocked until dynamic observation, idempotent dry-run/audit, and one approved sandbox send prove success/ack behavior.