docs: add offline b-route reverse decision

docs/superpowers/plans/2026-07-12-b-route-bridge-next-plan.md

@@ -2,9 +2,9 @@
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
-**Goal:** Push the primary B-route from a dry-run shell toward a verifiable sidecar/API bridge without enabling real send yet.
+**Goal:** Push the primary B-route from offline reverse evidence into the selected `in_process_adapter_research` branch, while keeping any external sidecar work preview/probe-only and not enabling real send.
 
-**Architecture:** Keep the Go MCP tool contracts stable. B-route remains the primary product route: reuse the logged-in `IMPlatformClient.exe` runtime through a narrow sidecar/API bridge if a safe bridge transport exists. A-route/RPA remains backup-only and should be used only for UI action smoke or when B-route is proven blocked.
+**Architecture:** Keep the Go MCP tool contracts stable. B-route remains the primary product route: reuse the logged-in `IMPlatformClient.exe` runtime through a narrow bridge. Offline reverse now rules out existing IPC/plugin as the next first step, so a dedicated in-process adapter research plan is required before any production send. External sidecars may only do self-check/probe/preview. A-route/RPA remains backup-only and should be used only for UI action smoke or when B-route is proven blocked.
 
 **Tech Stack:** Go 1.23.4, github.com/modelcontextprotocol/go-sdk, Windows PowerShell, .NET Framework C# helper/sidecar, stdin/stdout JSON protocols, Windows UI Automation only as fallback.
 
@@ -21,9 +21,17 @@
 
 ---
 
-## Offline reverse amendment
+## Offline reverse result amendment
 
-Because the next working day has no logged-in iSphere environment, execute `docs/superpowers/plans/2026-07-12-offline-broute-reverse-plan.md` before the online evidence/package tasks. This keeps B-route primary while using offline static reverse evidence to decide IPC/plugin/in-process/preview-only feasibility. A-route/RPA remains backup-only.
+`docs/superpowers/plans/2026-07-12-offline-broute-reverse-plan.md` has now produced the offline reverse decision set:
+
+- `docs/source-discovery/2026-07-12-offline-broute-reverse-index.md`
+- `docs/source-discovery/2026-07-12-broute-text-send-static-map.md`
+- `docs/source-discovery/2026-07-12-broute-file-send-static-map.md`
+- `docs/source-discovery/2026-07-12-broute-bridge-static-map.md`
+- `docs/source-discovery/2026-07-12-offline-broute-reverse-decision.md`
+
+Decision correction: B-route remains primary, but **existing IPC/local service** and **plugin extension** are not confirmed usable. The selected next branch is `in_process_adapter_research`. External sidecar work is allowed only as preview/probe plumbing until an in-process bridge is selected. A-route/RPA remains backup-only.
 
 ## Current evidence summary
 
@@ -36,7 +44,7 @@ The current `main` state already has:
 - Offline real `frmP2PChat` opener for RPA backup validation.
 - No B-route env wiring, no process-backed B-route sidecar client, no in-process bridge transport decision, and no real send/file-upload connector.
 
-Important technical conclusion: an external C# process cannot automatically reuse the logged-in static runtime of `IMPlatformClient.exe`. Before building send invocation, the next B-route node must decide the bridge transport: existing API/IPC, plugin/extension loading, in-process adapter, or fallback.
+Important technical conclusion: an external C# process cannot automatically reuse the logged-in static runtime of `IMPlatformClient.exe`. Offline reverse has now made the transport decision for this evidence set: existing API/IPC and plugin extension are not confirmed; the next B-route node is a separate `in_process_adapter_research` plan. Do not build production send/file upload in this plan.
 
 ---
 
@@ -72,11 +80,11 @@ B-route remains primary. The immediate next implementation is not production sen
 
 | Candidate | Can reuse logged-in runtime? | Local feasibility | Next action |
 | --- | --- | --- | --- |
-| existing_ipc/local_service | unknown | inspect live probe named pipes/services/network metadata | continue if concrete API appears |
-| plugin_extension | unknown | inspect install/plugin loader evidence | continue if client loads local plugin DLL/exe |
-| in_process_adapter | possible but highest risk | requires explicit bridge mechanism | defer until IPC/plugin ruled out |
-| external_dry_run_only | cannot reuse logged-in static runtime | useful for protocol/client tests only | implement as non-mutating sidecar boundary |
-| fallback_rpa | can drive UI only | already backup-ready | keep as backup, not primary |
+| existing_ipc/local_service | not confirmed | offline bridge map found no send/file API | park unless new online evidence appears |
+| plugin_extension | not confirmed | plugin evidence is UI/app-store/context-menu oriented | park unless a concrete local load contract appears |
+| in_process_adapter | possible but requires explicit bridge mechanism | selected by offline decision | create dedicated research plan before coding |
+| external_dry_run_only | cannot reuse logged-in static runtime | useful for protocol/client tests only | keep preview/probe-only boundary |
+| fallback_rpa | can drive UI only | backup-ready for UI action smoke | keep as backup, not primary |
 ```
 
 - [ ] Update `capability-source-matrix.md` so the next slice says: “B-route bridge transport feasibility and dry-run sidecar boundary”, not “RPA send”.
@@ -91,6 +99,10 @@ git diff --check
 
 Expected: exit 0.
 
+### 2026-07-12 plan correction
+
+Task 1 is now satisfied by the offline reverse reports listed above. Before executing Tasks 2-5, create or approve a new `in_process_adapter_research` plan. Tasks 2-4 may still be used later for non-mutating sidecar preview plumbing, but they do not solve production send by themselves.
+
 ## Task 2: Add B-route connector env selection without starting real send
 
 **Files:**