Revert "chore: Document I/O port handler system and improve docs UX"

This reverts commit 8d9d80f.

Author: maximilien-noal

README.md

@@ -18,18 +18,6 @@ NOTE: This is a port, and a continuation from the [original Java Spice86](https:
 
 It requires [.NET 10](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) and runs on Windows, macOS, and Linux.
 
-## Quick navigation
-
-- [Approach](#approach)
-- [Running your exe](#running-your-exe)
-- [Command line options](#command-line-options)
-- [I/O port handlers (replacing IOPortHandler)](#io-port-handlers-replacing-ioporthandler)
-- [Dynamic analysis](#dynamic-analysis)
-- [Overriding emulated code with C# code](#overriding-emulated-code-with-c-code)
-- [HTTP server](#http-server)
-- [How to build on your machine](#how-to-build-on-your-machine)
-- [Some screenshots](#some-screenshots)
-
 ## Approach
 
 Rewriting a program from only the binary is a hard task.
@@ -160,22 +148,6 @@ Spice86 -e program.exe --CpuHeavyLog \
 - OplMode: OPL synthesis mode. Values: None, Opl2, DualOpl2, Opl3, Opl3Gold. Default is Opl3.
 - SbMixer: Enable Sound Blaster mixer control of OPL voices. Default is true.
 
-## I/O port handlers (replacing IOPortHandler)
-
-Spice86 routes emulated hardware port I/O through the dispatcher / handler system:
-
-- `IIOPortHandler`: contract implemented by a device that handles one or more I/O ports.
-- `IOPortDispatcher`: central router that maps ports to handlers.
-- `DefaultIOPortHandler`: fallback behavior for unhandled ports.
-
-If you need to replace an `IOPortHandler` implementation in your integration:
-
-1. Implement `IIOPortHandler` in your device class.
-2. Register your handler for the port range in the dispatcher wiring.
-3. Keep `--FailOnUnhandledPort` enabled when validating to catch missing routes early.
-
-This makes it easier to incrementally swap hardware behavior while keeping unsupported ports visible during reverse engineering.
-
 ## Dynamic analysis
 
 Spice86 speaks the [GDB](https://www.gnu.org/software/gdb/) remote protocol:

docs/index.html

@@ -20,9 +20,6 @@
       --code-bg:     #1a2236;
       --warn:        #d29922;
       --danger:      #f85149;
-      --info-bg:     rgba(88,166,255,.12);
-      --success-bg:  rgba(63,185,80,.12);
-      --warning-bg:  rgba(210,153,34,.14);
       --nav-width:   240px;
     }
 
@@ -317,23 +314,6 @@
     }
     .callout strong { color: var(--warn); }
 
-    .callout-info {
-      border-left-color: var(--accent);
-      background: var(--info-bg);
-    }
-    .callout-info strong { color: var(--accent); }
-
-    .callout-success {
-      border-left-color: var(--accent2);
-      background: var(--success-bg);
-    }
-    .callout-success strong { color: var(--accent2); }
-
-    .callout-warning {
-      border-left-color: var(--warn);
-      background: var(--warning-bg);
-    }
-
     /* ── Mobile nav toggle ── */
     .mobile-header { display: none; }
     .mobile-overlay {
@@ -417,7 +397,6 @@ <h1>Spice86</h1>
   <div class="section-label">Reference</div>
   <ul>
     <li><a href="#cli">CLI Options</a></li>
-    <li><a href="#io-ports">I/O Port Handlers</a></li>
     <li><a href="#gdb">GDB Integration</a></li>
     <li><a href="#debugger">Built-in Debugger</a></li>
     <li><a href="#overrides">Code Overrides</a></li>
@@ -466,10 +445,6 @@ <h1>Spice86</h1>
       <a class="btn btn-secondary" href="https://github.com/OpenRakis/Spice86/wiki/Spice86-internal-debugger">Debugger Wiki</a>
       <a class="btn btn-secondary" href="https://github.com/OpenRakis/Cryogenic">Example project: Cryogenic</a>
     </div>
-
-    <div class="callout callout-info">
-      <strong>Quick start:</strong> Run <code>Spice86 -e game.exe</code>, inspect with GDB on <code>:10000</code>, then incrementally replace assembly with C# overrides.
-    </div>
   </div>
 
   <!-- ── What is Spice86? ── -->
@@ -761,33 +736,6 @@ <h3>Logging</h3>
     </div>
   </section>
 
-  <!-- ── I/O Port Handlers ── -->
-  <section id="io-ports">
-    <h2>I/O Port Handlers</h2>
-    <p>
-      Spice86 routes hardware port reads and writes through a dispatcher/handler model.
-      This keeps devices isolated and makes hardware behavior easier to swap during
-      reverse engineering.
-    </p>
-
-    <div class="table-wrap">
-      <table>
-        <thead>
-          <tr><th>Component</th><th>Role</th></tr>
-        </thead>
-        <tbody>
-          <tr><td><code>IIOPortHandler</code></td><td>Interface implemented by hardware device handlers.</td></tr>
-          <tr><td><code>IOPortDispatcher</code></td><td>Routes I/O port operations to the correct handler.</td></tr>
-          <tr><td><code>DefaultIOPortHandler</code></td><td>Fallback behavior when no specific handler is registered.</td></tr>
-        </tbody>
-      </table>
-    </div>
-
-    <div class="callout callout-success">
-      <strong>Replacing IOPortHandler:</strong> Implement <code>IIOPortHandler</code>, register it in the dispatcher wiring, and run with <code>--FailOnUnhandledPort true</code> to catch missing routes early.
-    </div>
-  </section>
-
   <!-- ── GDB ── -->
   <section id="gdb">
     <h2>GDB Integration</h2>
@@ -1072,9 +1020,6 @@ <h2>Game Compatibility</h2>
       This list reflects the state as of early 2026. A program crashing usually indicates
       an unimplemented BIOS/DOS interrupt or a video mode that has not been implemented.
     </p>
-    <div class="callout callout-warning">
-      <strong>Reading this table:</strong> Use it as a quick snapshot. For the latest status and detailed notes, prefer <a href="https://github.com/OpenRakis/Spice86/blob/master/COMPATIBILITY.md">COMPATIBILITY.md</a>.
-    </div>
     <div class="table-wrap">
       <table>
         <thead>