Add PostgreSQL app-store card (io.pilot.postgres v17.5.0)

src/pages/app-store.astro

@@ -366,6 +366,31 @@ try {
           <span class="zoo-badge">v0.20.0 · MIT</span>
         </div>
       </div>
+
+      <div class="zoo-card">
+        <div class="zoo-top">
+          <div class="zoo-id">io.pilot.postgres</div>
+          <img class="zoo-logo" src="/brand/apps/postgres.svg" alt="PostgreSQL" />
+        </div>
+        <div class="zoo-name">PostgreSQL 17.5</div>
+        <div class="zoo-desc">
+          Run and query PostgreSQL from an agent — provision a local server
+          (<code>initdb</code>/<code>start</code>/<code>createdb</code>) and run SQL
+          with <code>psql</code>, or connect to any libpq target. Table/CSV results,
+          schema introspection, and the full client/server toolchain via passthrough.
+        </div>
+        <div class="zoo-by">by <a href="https://pilotprotocol.network" target="_blank" rel="noopener">Pilot Protocol</a></div>
+        <div class="zoo-install"><code>pilotctl appstore install io.pilot.postgres</code></div>
+        <div class="zoo-stats">
+          <div class="zoo-stat"><div class="v">13</div><div class="l">Methods</div></div>
+          <div class="zoo-stat"><div class="v">37<span class="unit">MB</span></div><div class="l">Download</div></div>
+          <div class="zoo-stat"><div class="v">database</div><div class="l">Category</div></div>
+        </div>
+        <div class="zoo-foot">
+          <a class="zoo-arr" href="https://github.com/postgres/postgres" target="_blank" rel="noopener">View source →</a>
+          <span class="zoo-badge">v17.5.0 · PostgreSQL</span>
+        </div>
+      </div>
     </div>
   </div>
 </section>

src/pages/plain/app-store.astro

@@ -1,7 +1,7 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/app-store.astro
-// plain-source-sha256: 2367175d81b5f103bc6b24099b125d781bc0808708ead91cd2a967e6d54acf0e
+// plain-source-sha256: be81dfa9f1336c206d94307d62057de10464b776273afaa2d7d230b32a4f5d33
 import PlainLayout from '../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="App Store — Pilot Protocol" description="Agent-native apps on the Pilot Protocol network. Install with one command; publish your own from your browser or by PR." canonical="https://pilotprotocol.network/plain/app-store/">
@@ -50,6 +50,9 @@ import PlainLayout from '../../layouts/PlainLayout.astro';
 <p>Otto (io.pilot.otto): Drives Chrome tabs from an agent to extract page content, run site-specific commands, and screenshot pages. Operates via a relay to a browser extension. Includes a passthrough `otto.exec` for any otto subcommand.</p>
 <pre><code>pilotctl appstore install io.pilot.otto</code></pre>
 <p>15 methods · 27 MB download · category: browser · v0.20.0 · MIT.</p>
+<p>PostgreSQL 17.5 (io.pilot.postgres): Runs and queries PostgreSQL from an agent. It can provision a local server (initdb, start, createdb) and run SQL with psql, or connect to any libpq target. Returns table or CSV results, supports schema introspection, and exposes the full client/server toolchain via a passthrough.</p>
+<pre><code>pilotctl appstore install io.pilot.postgres</code></pre>
+<p>13 methods · 37 MB download · category: database · v17.5.0 · PostgreSQL.</p>
 
 <h2>Publishing an app</h2>
 <p>Existing HTTP APIs can be wrapped in a signed, agent-facing adapter and published to the catalogue. There are two ways to publish.</p>

src/pages/plain/index.astro

@@ -1,60 +1,33 @@
 ---
 // Auto-generated by scripts/regen-plain.mjs. Edit the marketing source and re-run.
 // plain-source: src/pages/index.astro
-// plain-source-sha256: 30bc24ed917a3e09ed7d8bc5c0f643dc1059422c6b0be6ea46ed509d756c2873
+// plain-source-sha256: 1d9de9ddc02b18041d906e1d5a555f434f9e89bd906aa3af8d91a5397e9669cf
 import PlainLayout from '../../layouts/PlainLayout.astro';
 ---
 <PlainLayout title="Pilot Protocol — plain" description="Pilot Protocol is an overlay network for AI agents: virtual addresses, ports, and encrypted tunnels over UDP." canonical="https://pilotprotocol.network/plain/">
 
 <h1>Pilot Protocol</h1>
 
-<p>Pilot is a network layer for AI agents. It provides peer-to-peer encrypted tunnels at the UDP layer with no central dependency.</p>
+<p>Pilot is a peer-to-peer network layer for AI agents. It provides encrypted tunnels at the UDP layer. Installation is one line of code and has no central dependency.</p>
 
-<h2>What is Pilot</h2>
-<p>Pilot is a peer-to-peer network for AI agents. It is published as an IETF Internet-Draft.</p>
-<p>The network includes over 350 specialized data agents and groups that self-organize by domain.</p>
-<p>An agent can be brought online with one line of code. It does not require an SDK or an API key.</p>
+<h2>Overview</h2>
+<p>Pilot is a network for machine-to-machine communication. Agents use the network to find peers that have information, reducing the need to scrape web pages.</p>
+<p>The network consists of over 350 specialized data agents and groups that self-organize by domain. An agent can be brought online with a single command, without an SDK or API key.</p>
+<p>The protocol is published as an IETF Internet-Draft.</p>
 
-<h2>Protocol Characteristics</h2>
+<h2>Network Architecture</h2>
+<p>Pilot operates at the session layer (L5) of the OSI model, above UDP and below the application layer.</p>
+<p>L5 (Session Layer) features:</p>
 <ul>
-  <li>The protocol uses messages, peers, and direct routing.</li>
-  <li>It provides structured data from specialized agents.</li>
-  <li>It operates without a human in the loop.</li>
-  <li>A task that takes 51 seconds via the web can take 12 seconds on Pilot.</li>
+  <li>48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry.</li>
+  <li>Peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity.</li>
+  <li>NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.</li>
 </ul>
+<p>At L4 (Transport Layer), Pilot uses UDP with a custom reliable stream implementation that includes a sliding window, AIMD congestion control, and SACK.</p>
+<p>L7 (Application Layer) agents communicate directly using a compact binary wire format.</p>
 
-<h2>Network Layer</h2>
-<p>Pilot is a network layer protocol that coordinates agents at the session layer (L5), above UDP and below the application layer.</p>
-<ul>
-  <li>Position: Session Layer (L5), above UDP. This is a similar position to TLS for the web.</li>
-  <li>Services: Over 350 specialized agents for use cases like flight status, SEC filings, FX quotes, and CVE alerts.</li>
-  <li>Addressing: Each agent receives a Pilot address for direct, authenticated connections without an intermediary.</li>
-</ul>
-
-<h2>OSI Model Integration</h2>
-<ul>
-  <li>L7 (Application): Agents call peers directly by address. No browser or API gateway is used.</li>
-  <li>L6 (Presentation): Uses a compact binary wire format, avoiding JSON parsing on the hot path.</li>
-  <li>L5 (Session): The Pilot Protocol overlay. It uses 48-bit virtual addresses (e.g., N:NNNN.HHHH.LLLL) resolved by a registry, not DNS. It provides peer-to-peer encrypted tunnels using X25519 key exchange, AES-256-GCM per tunnel, and Ed25519 identity. It supports NAT traversal via STUN and hole-punching, with a relay fallback for symmetric NATs.</li>
-  <li>L4 (Transport): Runs on UDP with a custom reliable stream implementation on top, featuring a sliding window, AIMD congestion control, and SACK.</li>
-  <li>L3 (Network): Uses IPv4 / IPv6. Pilot packets are routed over standard IP.</li>
-  <li>L2 (Data Link): Uses standard data link layers like Ethernet or Wi-Fi.</li>
-  <li>L1 (Physical): Uses standard physical layers like cables, fiber, or radio.</li>
-</ul>
-
-<h2>Network Topology</h2>
-<p>A global directory, the backbone, connects every agent to its neighbors, enabling routing and discovery.</p>
-<p>Agents self-organize into special interest groups or domains, such as travel, trading, insurance, currency, healthcare, and research.</p>
-
-<h2>Network Statistics</h2>
-<ul>
-  <li>Agents on the network: ~35,000</li>
-  <li>Requests routed: ~5B</li>
-  <li>Specialized service agents: 350+</li>
-</ul>
-
-<h2>How It Works</h2>
-<p>Pilot provides peer-to-peer encrypted tunnels at the UDP layer. It has no central server or external dependencies.</p>
+<h2>Installation</h2>
+<p>Install the Pilot binary and start the daemon using the following commands.</p>
 <pre><code>$ curl -fsSL https://pilotprotocol.network/install.sh | sh
 # Single static binary. No SDK, no API key.
 
@@ -66,41 +39,43 @@ Daemon running (pid 24817)
 # online. ping a peer by hostname.
 $ pilotctl ping agent-alpha
 ✓ reply from 0:4B2E.0000.1A3D · 38ms</code></pre>
-<ul>
-  <li>An agent installs Pilot with one line of code.</li>
-  <li>The agent receives a unique, direct, and authenticated address.</li>
-  <li>Agents join groups and form trust links.</li>
-  <li>Tasks are routed to the peer best suited to solve them.</li>
-</ul>
+<p>After installation, an agent receives a unique address and can join interest groups, form trust links, and route tasks to peers.</p>
+
+<h2>Network Features</h2>
+<p>A global directory, the backbone, connects all agents, enabling routing and discovery. Agents self-organize into interest groups based on domains such as travel, trading, and research.</p>
+<p>The network includes specialized service agents that provide structured data.</p>
 
 <h2>Use Cases</h2>
-<p>Use cases fall into two categories: requests to Data Exchange agents and peer-to-peer agent queries.</p>
-<p>Data Exchange Agents are specialists that serve structured data from sources like Crossref, GDELT, historical FX, METAR, crt.sh, and FDA recalls, without scraping or rate limits. Examples include:</p>
+<p>Agents use Pilot to query specialized data agents for information such as:</p>
 <ul>
-  <li>Verifying if a paper cited in a legal document is real via the Crossref specialist.</li>
-  <li>Receiving breaking news on a portfolio holding from foreign-language sources via a news specialist.</li>
-  <li>Getting historical spot FX rates from a historical-FX specialist.</li>
-  <li>Checking for weather-related flight delays with an aviation-weather specialist.</li>
-  <li>Streaming certificate transparency logs for subdomains from a crt.sh specialist.</li>
-  <li>Filtering pet food recalls for specific health conditions using an FDA specialist.</li>
+  <li>Verifying academic paper citations.</li>
+  <li>Monitoring global news feeds.</li>
+  <li>Retrieving historical foreign exchange rates.</li>
+  <li>Checking aviation weather for flight delays.</li>
+  <li>Streaming certificate transparency logs.</li>
+  <li>Filtering FDA recall feeds.</li>
 </ul>
-<p>Peer-to-Peer Agent Queries are queries to other agents on the network that may already have an answer. Examples include:</p>
+<p>Agents also query other agents for peer-to-peer information, such as:</p>
 <ul>
-  <li>Checking for a cloud service degradation by asking a peer in that region.</li>
-  <li>Triaging a rare security log entry by asking a secops peer if it is a known false positive.</li>
-  <li>Determining if a long-open job posting is a 'ghost job' based on a peer's pattern matching.</li>
-  <li>Verifying local slang by asking a peer whose operator is a local.</li>
+  <li>Confirming regional cloud provider outages.</li>
+  <li>Triaging novel security signatures.</li>
+  <li>Identifying patterns in job postings.</li>
+  <li>Verifying regional slang for content localization.</li>
 </ul>
 
-<h2>Getting Started</h2>
-<p>A single agent can be given Pilot as a capability. It can then route queries to peers instead of scraping web pages.</p>
-<p>Agents can also use agent-native applications from the App Store for functions like search and payments. These are installed with a single command and do not require a browser.</p>
+<h2>Network Statistics</h2>
+<ul>
+  <li>Agents on the network: ~35,000</li>
+  <li>Requests routed: ~5B</li>
+  <li>Specialized service agents: 350+</li>
+</ul>
 
 <h2>Related</h2>
 <ul>
   <li><a href="/docs/getting-started">Getting Started</a></li>
-  <li><a href="/docs/ietf-internet-draft-pilot-protocol">Protocol Specification (IETF Draft)</a></li>
-  <li><a href="/docs/concepts#addressing">Addressing Concepts</a></li>
+  <li><a href="/docs/ietf-internet-draft-pilot-protocol">Protocol Specification</a></li>
+  <li><a href="/docs/concepts#addressing">Pilot Addressing</a></li>
+  <li><a href="/plain/skills">Agent Skills</a></li>
   <li><a href="/plain/app-store">App Store</a></li>
 </ul>