isphere-ai-bridge/docs/current-status-card.md

Current Status Card

Date: 2026-07-09 Branch: main HEAD: b2d839e (HEAD -> main, gitea/main, gitea/HEAD) Merge branch 'codex/n15-report-hardening'

Business direction

项目核心不是继续做 UIA selector/report，而是通过 MCP 暴露 iSphere 的联系人、群组、消息、文件能力。

后续研发主线切换为 MCP 核心通信能力：搜索联系人、搜索群组、收发消息、收发文件。现有 UIA/selector/report 只作为底层辅助和证据，不再作为主线继续扩展。

Current completed state

• Go MCP foundation exists: cmd/isphere-mcp, internal/mcpserver, internal/helperclient, and internal/tools build a stdio MCP server.
• The current MCP surface exposes only four read-only helper tools:
  • win_helper_version
  • win_helper_self_check
  • win_helper_scan_windows
  • win_helper_dump_uia
• C# ISphereWinHelper exists under native/ISphereWinHelper and uses the isphere.helper.v1 stdin/stdout JSON contract.
• scripts/verify-win-helper.ps1 and scripts/verify-go-mcp.ps1 provide repeatable local checks for the helper and first-phase Go MCP server.
• N12-pre and N12R documents define safe offline evidence intake and internal-sandbox live UIA capture procedures.
• N13/N14/N15 produced selector catalog/report validation infrastructure, but those are supporting validation assets only.

What cannot be claimed externally

• The project has not yet implemented business MCP tools for contact search, group search, message receiving, message sending, file receiving, or file sending.
• The project has not completed production iSphere integration.
• The project has not proven a stable real message source for the full business workflow.
• The project has not implemented approval-backed real sending or real file upload.
• N12-pre offline evidence is not N12 pass.
• N13/N14/N15 selector/report work is not business completion and must not be described as finished contact/message/file capability.

What can be claimed externally

• The repository has a Go MCP + C# WinHelper foundation for controlled Windows-side read-only observation.
• The helper protocol boundary is explicit and avoids automatic login, process injection, hooks, memory reading, and endpoint-security bypass.
• The current code can support future MCP business tools by routing low-level Windows/UIA fallback work through a bounded helper layer.
• The project has repeatable verification scripts for the first-phase helper/MCP foundation.
• The project now has a corrected business contract and plan for core MCP communication tools.

N13/N14/N15 positioning

N13/N14/N15 are pre-business validation results. They can help identify UI elements and validate reports if UI automation becomes necessary, but they are not the product route. Do not start N16/N17 selector/report hardening by default. New work should first validate real business capability sources and core MCP tool contracts.

Next business mainline

1. Freeze the MCP core tools contract in docs/mcp-core-tools-contract.md.
2. Discover the best real capability source for:
   • isphere_search_contacts
   • isphere_search_groups
   • isphere_receive_messages
   • isphere_receive_files
3. Build the read-only loop first.
4. Add isphere_send_message and isphere_send_file only after approval and audit are implemented.
5. Keep UIA selector/report work as fallback support, not as the primary roadmap.