docs: prepare mcp source discovery loop

docs/current-status-card.md

@@ -2,7 +2,8 @@
 
 Date: 2026-07-09
 Branch: `main`
-HEAD: `b2d839e (HEAD -> main, gitea/main, gitea/HEAD) Merge branch 'codex/n15-report-hardening'`
+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
 
@@ -44,14 +45,26 @@ HEAD: `b2d839e (HEAD -> main, gitea/main, gitea/HEAD) Merge branch 'codex/n15-re
 
 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.
 
-## Next business mainline
+## Current loop
 
-1. Freeze the MCP core tools contract in `docs/mcp-core-tools-contract.md`.
-2. Discover the best real capability source for:
+Current loop: `Stage B1 - source discovery from N12-pre zyl package`.
+
+Plan file: `docs/superpowers/plans/2026-07-09-mcp-core-source-discovery-loop.md`.
+
+Loop output:
+
+1. Evidence index for downloaded `zyl.rar` package.
+2. Capability-source matrix for the four read tools:
    - `isphere_search_contacts`
    - `isphere_search_groups`
    - `isphere_receive_messages`
    - `isphere_receive_files`
-3. Build the read-only loop first.
+3. Selected first Stage C implementation slice.
+
+## Next business mainline
+
+1. Complete Stage B1 evidence index and capability-source matrix.
+2. Open Stage C with `isphere_receive_messages` as the first likely slice if evidence supports it.
+3. Add contact/group/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.