docs/blog: accuracy fixes + flagged inconsistencies

src/pages/blog/how-pilot-protocol-works.astro

@@ -274,7 +274,7 @@ const bodyContent = `<p>Every modern agent framework makes the same assumption:
       <tr><td>7</td><td>Echo</td><td>Ping/pong for connectivity testing and latency measurement</td></tr>
       <tr><td>53</td><td>DNS</td><td>Hostname resolution within the overlay network</td></tr>
       <tr><td>80</td><td>HTTP</td><td>Standard HTTP services over Pilot tunnels</td></tr>
-      <tr><td>443</td><td>Secure</td><td>Encrypted services (X25519 + AES-GCM per connection)</td></tr>
+      <tr><td>443</td><td>Secure</td><td>Encrypted services (X25519 + AES-256-GCM per connection)</td></tr>
       <tr><td>1000</td><td>Stdio</td><td>Interactive terminal sessions between agents</td></tr>
       <tr><td>1001</td><td>Data Exchange</td><td>Structured data and file transfer</td></tr>
       <tr><td>1002</td><td>Event Stream</td><td>Pub/sub event distribution with topic routing</td></tr>

src/pages/blog/overlay-network-ai-agents.astro

@@ -32,7 +32,7 @@ const bodyContent = `<p>An AI agent that only works when it's sitting on the sam
 <thead><tr><th>Property</th><th>Typical VPN overlay</th><th>Pilot Protocol overlay</th></tr></thead>
 <tbody>
 <tr><td>Addressing</td><td>Virtual IP tied to device membership</td><td>Permanent virtual address per agent, independent of IP</td></tr>
-<tr><td>Transport</td><td>Encrypted tunnel between members</td><td>Encrypted UDP tunnels (X25519 key exchange + AES-GCM)</td></tr>
+<tr><td>Transport</td><td>Encrypted tunnel between members</td><td>Encrypted UDP tunnels (X25519 key exchange + AES-256-GCM)</td></tr>
 <tr><td>NAT traversal</td><td>Usually supported</td><td>STUN + hole-punching, with relay fallback</td></tr>
 <tr><td>Trust model</td><td>Join the network = trusted by other members</td><td>Explicit per-peer handshake — membership and trust are decoupled</td></tr>
 <tr><td>Discovery</td><td>Device list / admin console</td><td>Rendezvous registry + nameserver — find agents by name or tag</td></tr>
@@ -49,7 +49,7 @@ const bodyContent = `<p>An AI agent that only works when it's sitting on the sam
 
 <ul>
 <li><strong>Addressing:</strong> every agent gets a permanent virtual address that survives restarts, IP changes, and moving across clouds.</li>
-<li><strong>Transport:</strong> encrypted UDP tunnels using X25519 key exchange and AES-GCM, with userspace reliability layered over UDP.</li>
+<li><strong>Transport:</strong> encrypted UDP tunnels using X25519 key exchange and AES-256-GCM, with userspace reliability layered over UDP.</li>
 <li><strong>NAT traversal:</strong> STUN plus hole-punching, with a relay (beacon) fallback so agents behind restrictive NATs stay reachable.</li>
 <li><strong>Trust:</strong> an explicit per-peer handshake that both sides must mutually approve — membership on the overlay and trust with a given peer are separate states.</li>
 <li><strong>Discovery:</strong> a rendezvous registry and nameserver, so agents and capabilities can be found by name or tag instead of a hardcoded address.</li>

src/pages/docs/comparison.astro

@@ -58,7 +58,7 @@ const bodyContent = `<h1>Pilot Protocol vs MCP vs A2A vs ACP</h1>
       <tr><td><strong>Transport</strong></td><td>Encrypted UDP tunnels</td><td>HTTP/JSON-RPC</td></tr>
       <tr><td><strong>Discovery</strong></td><td>Registry + tags + DNS</td><td>Agent cards (/.well-known/agent-card.json)</td></tr>
       <tr><td><strong>NAT traversal</strong></td><td>Built-in (STUN + relay)</td><td>Requires public endpoints or VPN</td></tr>
-      <tr><td><strong>Security</strong></td><td>X25519+AES-GCM per tunnel</td><td>Delegated to HTTP/TLS</td></tr>
+      <tr><td><strong>Security</strong></td><td>X25519+AES-256-GCM per tunnel</td><td>Delegated to HTTP/TLS</td></tr>
       <tr><td><strong>Addressing</strong></td><td>Permanent virtual addresses</td><td>URLs</td></tr>
       <tr><td><strong>Offline support</strong></td><td>Inbox queuing</td><td>Polling / push notifications</td></tr>
     </tbody>
@@ -101,7 +101,7 @@ const bodyContent = `<h1>Pilot Protocol vs MCP vs A2A vs ACP</h1>
     <tbody>
       <tr><td>Permanent agent identity</td><td>Yes</td><td>No</td><td>Agent cards</td><td>—</td></tr>
       <tr><td>Virtual addressing</td><td>48-bit</td><td>No</td><td>No</td><td>No</td></tr>
-      <tr><td>End-to-end encryption</td><td>X25519+AES-GCM</td><td>No</td><td>TLS</td><td>TLS</td></tr>
+      <tr><td>End-to-end encryption</td><td>X25519+AES-256-GCM</td><td>No</td><td>TLS</td><td>TLS</td></tr>
       <tr><td>NAT traversal</td><td>STUN+relay</td><td>N/A</td><td>No</td><td>No</td></tr>
       <tr><td>Mutual trust model</td><td>Yes</td><td>No</td><td>No</td><td>No</td></tr>
       <tr><td>Peer discovery</td><td>Registry+tags</td><td>Tool manifest</td><td>Agent cards</td><td>Directory</td></tr>

src/pages/docs/pubsub.astro

@@ -37,7 +37,7 @@ const bodyContent = `<h1>Pub/Sub</h1>
   <ul>
     <li>Each node is both a potential publisher and broker</li>
     <li>Subscribers connect <strong>to the publisher</strong>, not to a shared server</li>
-    <li>No single point of failure - if one node goes down, other nodes' brokers continue operating independently</li>
+    <li>No single point of failure for event delivery - if one node goes down, other nodes' brokers continue operating independently. Peer discovery and trust still resolve through the registry.</li>
     <li>Subscriptions are per-connection - if the connection drops, the subscription is gone</li>
   </ul>
 

src/pages/plain/docs/comparison.astro

@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/docs/comparison.astro
-// plain-source-sha256: 252e82ec065c268a15114496f4a9c2056befbb5418d082f726f52f57c056d085
+// plain-source-sha256: 93ac735c664e3e15809e6c946530c0b4510c6bc2e3496da19d2ff602b5767d0b
 import PlainLayout from '../../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pilot Protocol vs MCP vs A2A vs ACP — Pilot Protocol (plain)" description="Compare Pilot Protocol with MCP, Google A2A, and ACP. Understand the differences in architecture, security, and use cases for AI agent communication." canonical="https://pilotprotocol.network/plain/docs/comparison/">
@@ -37,7 +37,7 @@ import PlainLayout from '../../../layouts/PlainLayout.astro';
 <ul>
   <li>Permanent agent identity: Yes</li>
   <li>Virtual addressing: 48-bit</li>
-  <li>End-to-end encryption: X25519+AES-GCM</li>
+  <li>End-to-end encryption: X25519+AES-256-GCM</li>
   <li>NAT traversal: STUN+relay</li>
   <li>Mutual trust model: Yes</li>
   <li>Peer discovery: Registry+tags</li>

src/pages/plain/docs/pubsub.astro

@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/docs/pubsub.astro
-// plain-source-sha256: 97728a4ddd0c8ab054e0b997544290dd841fbf11275015177c2525814150927e
+// plain-source-sha256: 45cdd72dd4d190dee1238534880e659fbb1263d4b694596ca9055005ab5dfff3
 import PlainLayout from '../../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pub/Sub — Pilot Protocol (plain)" description="Subscribe to topics, publish events, and use wildcard filtering with Pilot Protocol's event stream." canonical="https://pilotprotocol.network/plain/docs/pubsub/">
@@ -22,7 +22,7 @@ import PlainLayout from '../../../layouts/PlainLayout.astro';
 <ul>
   <li>Each node is both a potential publisher and broker.</li>
   <li>Subscribers connect to the publisher, not to a shared server.</li>
-  <li>There is no single point of failure; if one node goes down, other nodes' brokers continue operating independently.</li>
+  <li>There is no single point of failure for event delivery; if one node goes down, other nodes' brokers continue operating independently. Peer discovery and trust still resolve through the registry.</li>
   <li>Subscriptions are per-connection. If the connection drops, the subscription is gone.</li>
 </ul>