admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
d78152cbfa3b6eee972dd06f5534936c01d19f68
isphere-ai-bridge/docs/current-status-card.md
zhaoyilun d78152cbfa docs: replan core business capabilities
2026-07-10 09:22:28 +08:00

14 KiB
Raw Blame History

Current Status Card

Date: 2026-07-10 Branch: main Loop base: e993ce1 docs: trim safety constraints from mcp roadmap Remote base before local roadmap commits: b2d839e 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 eight read-oriented tools:
    • win_helper_version
    • win_helper_self_check
    • win_helper_scan_windows
    • win_helper_dump_uia
    • isphere_receive_messages
    • isphere_search_contacts
    • isphere_search_groups
    • isphere_receive_files
  • 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, eight-tool MCP surface, default empty-source receive/contact/group/file calls, synthetic configured-file receive/contact/group/file smoke, and synthetic configured-directory receive/contact/group/file smoke.
  • isphere_receive_messages now returns the contract-facing ok, conversation, messages, next_cursor, and audit envelope while retaining legacy parser-native message fields for compatibility.
  • isphere_receive_messages accepts the read-contract argument set for the current local-readonly path: conversation_id, query, since, limit, include_attachment_metadata, source_preference, preview, and empty cursor.
  • isphere_search_contacts and isphere_search_groups accept and validate the safe search-contract args for the current local-readonly path and can optionally enrich results from the env-configured C29 MsgLib.db display-entity reader; default behavior remains log/JID-backed when MsgLib env vars are absent.
  • isphere_receive_files list mode accepts and validates the safe file-list contract args for the current local-readonly path while keeping download blocked.
  • native/MsgLibReadSidecar provides a bounded x86 .NET read-only boundary for MsgLib.db schema/display-source checks, bounded contact/group display-entity reads, message-source metadata, and sidecar-level bounded message listing; internal/msglib wraps it from Go, C30 wires display metadata as an optional MCP contact/group enrichment source, C39 adds a Go receive-source adapter around ListMessages, C40 adds tool-level explicit msglib_readonly source selection, and C41 wires it through env configuration without changing the MCP default source.
  • 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 message sending, file download, or file sending; isphere_receive_messages, isphere_search_contacts, isphere_search_groups, and isphere_receive_files list mode have operator-local encrypted log-file/log-directory support but not a production ingestion path.
  • The project has not completed production iSphere integration.
  • The project has not proven a stable real message source for the full business workflow beyond decrypted PacketReader log evidence and synthetic/redacted tests.
  • The project has not implemented real message sending or real file upload.
  • N12-pre offline evidence is not N12 pass.
  • N13/N14/N15 selector/report work is pre-business evidence, not 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 keeps Windows/UIA work separate from the Go MCP service layer.
  • 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 helper/MCP foundation and the current eight-tool surface.
  • The project now has a corrected business contract and plan for core MCP communication tools, plus registered receive/contact/group/file-list read tools that can use ISPHERE_PACKET_LOG_FILE for one operator-local encrypted PacketReader log-line file or ISPHERE_PACKET_LOG_DIR for an operator-local directory of encrypted .log/.txt PacketReader files.

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. New work should first validate real business capability sources and core MCP tool contracts.

Current loop

Current loop: Business Roadmap / R1 - Receive-message source reconciliation precheck.

Plan file: docs/superpowers/plans/2026-07-10-core-business-capabilities-roadmap.md.

Loop rule:

  1. Write or update the plan before coding.
  2. Implement one loop only.
  3. Verify, commit exact paths, then update the next loop based on actual results.
  4. Continue automatically while the next step is clear; ask the user only when blocked or when business direction changes.

Current loop output so far:

  1. C1: internal/isphere/logcodec.DecryptLine and internal/isphere/packetlog.ParseMessageLog for redacted PacketReader message logs.
  2. C2: internal/isphere.EncryptedPacketLogSource.ReceiveMessages source abstraction with synthetic/redacted encrypted fixtures.
  3. C3: isphere_receive_messages MCP tool registration and server tool list update.
  4. C4: repeatable operator verification and docs for the five-tool surface.
  5. C5: safe ISPHERE_PACKET_LOG_FILE loader for operator-local encrypted PacketReader log lines.
  6. C6: fixture-backed operator smoke for configured receive source.
  7. C7: log-backed contact candidate extraction from sender/receiver JIDs.
  8. C8: isphere_search_contacts MCP registration and six-tool verification.
  9. C9: group source evidence precheck confirmed groupchat/conference/MUC hits in ignored decrypted logs.
  10. C10: log-backed group candidate extraction from groupchat/conference JIDs.
  11. C11: isphere_search_groups MCP registration and seven-tool verification.
  12. C12: file evidence precheck confirmed enough PacketReader/Smark evidence for file metadata listing, but not enough for real cache/download mapping.
  13. C13: internal/isphere.ListFilesFromMessages extracts synthetic/redacted file metadata candidates from normalized messages.
  14. C14: isphere_receive_files MCP list mode registered and verify-go-mcp now covers eight tools plus default/configured file-list smoke.
  15. C15: isphere_send_message source precheck found no validated write connector; send implementation is blocked pending bridge/API, UIA action, or protocol evidence.
  16. C16: configured PacketReader source hardening added ISPHERE_PACKET_LOG_DIR, deterministic recursive .log/.txt directory loading, ambiguous file/dir config failure, and configured-directory receive/contact/group/file smoke verification.
  17. C17: isphere_receive_messages output was aligned to the core read contract envelope and message fields while retaining legacy aliases; verify-go-mcp now asserts contract fields for configured file and directory source smokes.
  18. C18: isphere_receive_messages gained conversation_id and query filters across source, MCP args, tests, and configured file/directory smoke verification.
  19. C19: isphere_receive_messages gained RFC3339 since filtering against PacketReader epoch-millisecond timestamps plus invalid-since error handling.
  20. C20: isphere_receive_messages now accepts and validates the remaining safe read-contract args, rejects unsupported source/cursor cases, and can suppress inline attachment metadata.
  21. C21: isphere_search_contacts and isphere_search_groups now accept and validate safe search-contract args, while rejecting unsupported source/cursor cases.
  22. C22: isphere_receive_files list mode now accepts and validates safe contract args, rejects unsupported source/cursor/output/download cases, and keeps download blocked.
  23. C23: display-name enrichment was blocked because current committed evidence and ignored metadata do not validate a JID-to-display-name/group-title source; MsgLib.db remains the most likely next source but inspected copies are not directly readable as SQLite.
  24. C24: MsgLib.db readability precheck found high-entropy non-SQLite files with a consistent wrapper/encryption signature; wrapper candidates include HYHC.IMPP.DAL.dll, Utilities.Lib.SQLiteInteraction*.dll, Utilities.Lib.DBModel.dll, and RepairDatabase.exe.
  25. C25: static .NET wrapper analysis recovered the DAL open path: HYHC.IMPP.DAL.IMPPDAL configures System.Data.SQLite through Utilities.Lib.DBSQLite, sets DatabaseName to the DB path and Password to 123, and exposes candidate display/message tables such as TD_Roster, tblRecent, tblPersonMsg, tblMsgGroupPersonMsg, and TD_WorkGroupAuth.
  26. C26: copied MsgLib.db schema extraction succeeded through a 32-bit .NET System.Data.SQLite read-only probe with password 123; all three copied DB candidates opened, with confirmed contact/group/message/file schema tables.
  27. C27: added native/MsgLibReadSidecar with protocol isphere.msglib.v1, x86 build/verify scripts, and safe self_check, schema_summary, and display_sources operations; evidence-backed smoke returned 8 display-source candidates without row/message values.
  28. C28: added internal/msglib Go client wrapper for the sidecar protocol with env config, fake-sidecar unit tests, timeout handling, structured sidecar errors, SelfCheck, and DisplaySources; no MCP tool wiring or message/display row reads yet.
  29. C29: added bounded display_entities support across the x86 sidecar, Go client, and verification script; evidence-backed verification returned sanitized contact/group counts and source-table names only, with no message bodies, file paths, raw rows, sends, writes, hooks, or injection.
  30. C30: wired DisplayEntities into isphere_search_contacts and isphere_search_groups as an optional env-configured enrichment source with fake-source tests; default MCP verification now clears MsgLib env to keep the standard smoke deterministic.
  31. C31: added optional scripts/verify-msglib-mcp-enrichment.ps1; real copied-DB MCP smoke returned sanitized contact/group counts and MsgLib source refs without printing names, JIDs, message bodies, file paths, or raw rows.
  32. C32: isphere_receive_messages can now use the optional MsgLib display-entity source to fill safe sender_name and conversation.display_name fields while preserving message text/content/attachment behavior.
  33. C33: optional real copied-DB MCP smoke now also constructs a synthetic encrypted PacketReader fixture from internally selected MsgLib contact/group metadata and verifies receive-message display enrichment through MCP; output stays sanitized to counts, booleans, and msglib:<source_table> refs only.
  34. C34: docs/go-mcp-runbook.md now documents the operator setup path for optional MsgLib display-name enrichment, including the required env vars, partial-config failure rule, standard no-MsgLib verification, optional provider smoke, optional MCP enrichment smoke, and sanitized output boundaries.
  35. C35: docs/source-discovery/2026-07-10-msglib-message-source-precheck.md maps tblPersonMsg, tblMsgGroupPersonMsg, TD_SystemMessageRecord, receipt, recent, and file-record schema columns to the future isphere_receive_messages contract; decision is metadata-only message_sources sidecar first, not body-returning DB listing yet.
  36. C36: added metadata-only MsgLib message_sources across the x86 sidecar, Go wrapper, and sidecar verification; evidence-backed smoke returned six message-source summaries with source/table/role/availability/row-count metadata only.
  37. C37: docs/source-discovery/2026-07-10-db-backed-receive-source-design.md defines the bounded DB-backed receive-message design: sidecar op list_messages, hard limit, no cursor initially, explicit include_body, no raw rows, no file path values, PacketReader remains default until reconciliation.
  38. C38: added sidecar/Go-wrapper list_messages, clamped to 1..50, cursor rejected, optional attachment metadata without path/download refs, and copied-DB verification with include_body=false; printed evidence is only count/source-table/safety booleans.
  39. C39: added internal/isphere.MsgLibMessageSource, an injected-provider adapter that maps msglib.ListMessages results into the existing receive-message domain model, preserving explicit source refs and attachment metadata while leaving MCP default PacketReader behavior unchanged.
  40. C40: added tool-level explicit receive source selection: empty/auto/local_readonly still use the primary PacketReader/log-backed source, while source_preference="msglib_readonly" uses a configured MsgLib receive source and is rejected when not configured.
  41. C41: wired env-configured MsgLib client into both display enrichment and explicit receive selection; optional copied-DB MCP smoke now proves source_preference="msglib_readonly" returns sanitized count/source evidence while standard verify-go-mcp.ps1 remains deterministic.

Recompiled business roadmap

The active plan is now organized around the four business goals rather than the old technology-led C-loop:

  1. Search contacts and search groups: harden result quality, ranking, de-duplication, and richer fields.
  2. Receive/send messages: reconcile PacketReader and MsgLib receive sources first; then discover and validate a send-message connector.
  3. Receive/send files: map received file metadata to cache/download behavior first; send-file remains behind the send connector plus upload evidence.
  4. Keep UIA selector/report work as fallback support, not as the primary roadmap.

Next node: R1 receive-message source reconciliation precheck.

Reference in New Issue View Git Blame Copy Permalink