docs: confirm groupchat source evidence

This commit is contained in:
zhaoyilun
2026-07-09 23:39:29 +08:00
parent 2832e286e7
commit 7e616a1f10
3 changed files with 72 additions and 9 deletions

View File

@@ -49,7 +49,7 @@ N13/N14/N15 are pre-business validation results. They can help identify UI eleme
## Current loop
Current loop: `Stage C / Loop C9 - group source evidence precheck`.
Current loop: `Stage C / Loop C10 - log-backed group candidate extraction`.
Plan file: `docs/superpowers/plans/2026-07-09-stage-c-log-backed-receive-messages-loop.md`.
@@ -70,10 +70,12 @@ Current loop output so far:
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.
## Next business mainline
1. Run Stage C Loop C9: verify whether current decrypted log evidence contains group/groupchat identifiers before implementing `isphere_search_groups`.
2. Add group/file read tools after their source decisions are recorded.
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.
1. Implement Stage C Loop C10: extract group candidates from log-backed groupchat/conference JIDs.
2. Register `isphere_search_groups` after group source tests pass.
3. Add file read tools after their source decisions are recorded.
4. Add `isphere_send_message` and `isphere_send_file` after source discovery and connector selection.
5. Keep UIA selector/report work as fallback support, not as the primary roadmap.