feat: extract files from message logs

This commit is contained in:
zhaoyilun
2026-07-10 00:45:08 +08:00
parent 3d68a18097
commit fe242145bb
5 changed files with 249 additions and 7 deletions

View File

@@ -50,7 +50,7 @@ N13/N14/N15 are pre-business validation results. They can help identify UI eleme
## Current loop
Current loop: `Stage C / Loop C13 - log-backed file metadata extraction`.
Current loop: `Stage C / Loop C14 - register isphere_receive_files list mode`.
Plan file: `docs/superpowers/plans/2026-07-09-stage-c-log-backed-receive-messages-loop.md`.
@@ -75,10 +75,11 @@ Current loop output so far:
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; MCP registration is next.
## Next business mainline
1. Run Stage C Loop C13: implement log-backed file metadata extraction from normalized messages.
2. Register `isphere_receive_files` list mode after C13 source behavior passes; leave actual download/cache mapping as a later connector node.
1. Run Stage C Loop C14: register `isphere_receive_files` list mode on top of `ListFilesFromMessages`.
2. Leave actual download/cache mapping as a later connector node until a message-to-cache hash or client download source is validated.
3. Add `isphere_send_message` and `isphere_send_file` after source discovery and connector selection.
4. Keep UIA selector/report work as fallback support, not as the primary roadmap.