Add desktop shell prompt bridge

docs/desktop-vertical.md

@@ -30,3 +30,15 @@ The first transport target is Tor through an AMPB-owned Arti/Tor runtime. The de
 vertical is not complete until AMPB can start the runtime, verify the SOCKS endpoint, and
 launch the bundled browser profile without clearnet fallback. I2P and Reticulum use the
 same route, consent, state, and health-check model after Tor works.
+
+## Desktop Shell
+
+`ampbrowser shell <url>` is the first desktop shell bridge. It prepares the same open plan
+as `ampbrowser open`, renders first-use transport consent as a desktop dialog when a
+prompt is required, and then launches the bundled browser through the shared runner after
+approval. Use `--yes` for scripted verification without showing the dialog.
+
+```sh
+python3 -m ampbrowser shell http://example.onion/
+python3 -m ampbrowser shell http://example.onion/ --yes
+```

docs/open-flow.md

@@ -30,6 +30,10 @@ render those fields as the first-use popup. After approval, launch output includ
 `transport_setup_pid`, and `transport_setup_endpoint` so the shell can distinguish an
 adopted daemon from an AMPB-owned managed process.
 
+`ampbrowser shell <url>` is the desktop wrapper for this contract. It shows the prompt
+through a desktop dialog when possible, falls back to a terminal prompt when needed, and
+launches through the same transport runner after approval.
+
 ## Examples
 
 ```sh
@@ -41,4 +45,5 @@ python3 -m ampbrowser open http://example.b32.i2p/ --platform android
 python3 -m ampbrowser open https://wownero.org/ --launch
 python3 -m ampbrowser open http://example.onion/ --launch
 python3 -m ampbrowser open http://example.onion/ --yes --launch
+python3 -m ampbrowser shell http://example.onion/
 ```