Adom Bridge

@@ -462,6 +462,8 @@ <p>The local dev-environment app Adom Bridge can embed into; Adom Bridge relays Hydrogen's runtime state and drives its lifecycle.</p>
 <p>Install a third-party bridge by pasting its manifest URL, or <code>bridge_install {"manifestUrl":"..."}</code>.</p>
 <p>Deep dive: <a href="https://wiki.adom.inc/adom/adom-bridge/files/docs/bridges.md">bridges from the user's side</a> (cards, LEDs, console, installing and updating).</p>
+<h2>A bridge's page has a stable address</h2>
+<p>A bridge that serves its own page (a dashboard) gets <code>http://127.0.0.1:24680/open/&lt;bridge&gt;</code> on Adom Bridge's fixed port: bookmark that one, not the bridge's own port, which can move after a sleep or an update. Removing a bridge stops it first, and the installed bridge is always the one that runs, never the older copy inside the installer. Deep dive: <a href="docs/bridges.md">docs/bridges.md</a>.</p>
 <h2>Build your own bridge</h2>
 <p>The bridges above are not special: they are ordinary bridges, and you can add your own. A bridge is a small local program in any language that serves HTTP on localhost. Adom Bridge spawns it, keeps it alive, and routes a namespace of verbs to it, so <code>kicad_*</code> reaches the KiCad bridge and <code>yourprefix_*</code> would reach yours.</p>
 <p>Adom Bridge core owns the machine: spawning, ports, health, permissions, screenshots, files, windows, and the relay. You own your app and what its verbs mean. Runtimes are handled for you, a portable Node and Python with no elevation prompt, and your bridge inherits the human-approval permission model rather than inventing one.</p>
@@ -511,6 +513,8 @@ <p><strong>The trust boundary is install-consent plus the localhost bind.</strong> Installing the app (and each bridge) is you granting permission for the AI to drive your machine; if you do not want that, uninstall. And the app plus every bridge binds <code>127.0.0.1</code> <strong>only, never <code>0.0.0.0</code></strong>, so a caller must already be a program you installed on your own machine to reach it. No network attack surface by construction.</p>
 <p>On top of that, the <strong>remote cloud-AI path is approval-gated.</strong> Verbs that run code or change the machine (<code>shell_execute</code>, <code>run_script</code>, <code>launch_process</code>, <code>write_file</code>, <code>registry_*</code>, <code>process_kill</code>, and so on) require a human grant when they arrive over the <em>relay</em>: <strong>+1hr / +24hr</strong> (time-boxed), <strong>Bypass</strong> (indefinite), or <strong>Revoke</strong>. The grant is human-only; local callers (your CLI, Hydrogen, bridges) are trusted by transport and never prompt; read-only verbs are never gated.</p>
 <p>Deep dive: <a href="https://wiki.adom.inc/adom/adom-bridge/files/docs/permissions.md">permissions</a> (what each Approve choice means, and how to revoke).</p>
+<h2>Every prompt is kept</h2>
+<p>A prompt nobody answers is reported to the AI as expired, not as a refusal, so an agent asks again instead of giving up (an AI that knows an install takes a while can ask Adom Bridge to hold the prompt for up to ten minutes). And every prompt raised on a machine, with its decision, the time and which of your machines decided it, is written to a local history that Hydrogen's bell and the AI can read back (<code>permission_history</code>), so "closed on another surface" always has an answer. Deep dive: <a href="docs/permissions.md">docs/permissions.md</a>.</p>
 <h2>Notifications</h2>
 <p>Adom Bridge speaks to you through native Windows toasts via <code>notify_user</code>, under Adom Bridge's own identity (the Adom logo, and Action Center history like any first-class app). A cloud AI or a bridge, even one on a different machine addressed with <code>target</code>, fires them to reach you wherever you are. Every image below is the real toast, captured live from the exact call shown.</p>
 <p><strong>Basic alert.</strong> Awareness: a build finished, a file is ready. Auto-dismisses in about 7 seconds. Add <code>"durationLong":true</code> to hold it around 25 seconds; <code>"level":"error"</code> and up do that automatically, and <code>"emergency"</code> also flashes the taskbar.</p>