@agentproto/pairing-host 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,32 @@
+# @agentproto/pairing-host
+
+Host-side AIP-59 pairing for anything that wants to be a pairing host, not only
+the agentproto daemon. Depends on `@agentproto/acp`, `@agentproto/secrets` and
+`ws` only.
+
+- `createPairingRegistry(deps)`: offers, accept handshake over an untrusted
+  rendezvous, `pairings.json` persistence, epoch reconnect, revocation.
+  Dependency-injected (`loadIdentity`, `dial`, `serve`, `pairingsPath`).
+- `dialRendezvous(url, signal, { agent? })`: default WebSocket dial.
+- `serveLoopbackHttp({ target, injectHeaders?, allowPaths? })`: a `serve`
+  that forwards the paired, E2E-wrapped channel to a loopback HTTP app.
+- `registry.mintLocalDevice({ name })` / `registry.verifyDeviceBearer(bearer)`:
+  optional local-device credential for loopback clients. The bearer is derived
+  from a per-device secret kept in `pairings.json` (`localDevices`, optional,
+  mode 0600); it is shown once at mint time, never logged, and `revoke()` makes
+  the very next verify fail.
+
+```ts
+import { createPairingRegistry, dialRendezvous, serveLoopbackHttp } from "@agentproto/pairing-host"
+
+const registry = createPairingRegistry({
+  loadIdentity,
+  pairingsPath,
+  dial: (url, signal) => dialRendezvous(url, signal),
+  serve: serveLoopbackHttp({
+    target: new URL("http://127.0.0.1:8123"),
+    injectHeaders: { authorization: `Bearer ${localToken}` },
+    allowPaths: ["/mcp"],
+  }),
+})
+```

package/dist/index.d.ts

@@ -0,0 +1,350 @@
+import { FrameSink, E2eFrameSink } from '@agentproto/acp/tunnel';
+import { RouteAuthTokens } from '@agentproto/secrets/pairing';
+import { DaemonIdentity } from '@agentproto/secrets/identity';
+import { Agent } from 'node:http';
+
+/**
+ * Host-side pairing registry (design: DESIGN §3/§4, PLAN deliverable 2). Lives
+ * in `@agentproto/pairing-host` so any AIP-59 host — the agentproto daemon is
+ * one, a standalone app is another — can embed it; `@agentproto/runtime`
+ * re-exports it unchanged.
+ *
+ * Owns everything a host needs to be *paired with* over an untrusted
+ * rendezvous:
+ *
+ *   - **Offer store** — in-memory, single-use, expiry-checked one-time offer
+ *     secrets minted by `pair offer`. A daemon restart voids outstanding offers
+ *     (acceptable + documented). The daemon parks on the offer's ROUTE token and
+ *     the handshake's `verifyAuthToken` predicate checks the sealed AUTH token,
+ *     SPENDING the offer on the first successful handshake (a wrong token spends
+ *     nothing).
+ *   - **Pairings store** — `~/.agentproto/pairings.json` (0600, atomic write),
+ *     one record per paired client: `{clientPub, name, fingerprint, createdAt,
+ *     lastSeen, pairRoot, rendezvousUrl}`. `pairRoot` is the long-term shared
+ *     secret (`derivePairRoot`) from which reconnect routing tokens derive.
+ *   - **Rendezvous connections** — for a fresh offer, and for every persisted
+ *     pairing on boot (autoconnect), the daemon dials the rendezvous *outbound*
+ *     (`side=daemon&t=<route>`), runs `daemonHandshakeOverSink` with the P1
+ *     crypto, and — on success — serves the spliced, E2E-wrapped channel exactly
+ *     like `serve --connect` serves a tunnel host. The serving path itself is
+ *     injected (`serve`) so this module stays free of pty/adapter concerns and
+ *     the CLI can reuse its `createTunnelServer` config verbatim.
+ *   - **Reconnect epochs** — a persisted pairing's standing connection parks on
+ *     the pairing-derived route `HKDF(pairRoot, "rv-route"‖epoch)`, rotated per
+ *     UTC day. The daemon parks on BOTH the current and previous
+ *     epoch tokens so a client whose clock straddles midnight still finds it;
+ *     reconnect-with-backoff keeps the standing connection alive.
+ *   - **Revocation** — removing a pairing drops its rendezvous connections, so
+ *     it can no longer be served. For a grace period (`revokedGraceMs`, default
+ *     14 days) the daemon keeps a *tombstone*: it still parks on the pairing's
+ *     epoch ROUTES, completes the (daemon-signed) handshake only for a hello
+ *     carrying that epoch's AUTH token, and answers with a single E2E-encrypted
+ *     `error{code:"pairing_revoked"}` frame before closing — never serving the
+ *     channel. That is what lets a client tell "unpaired" from "daemon
+ *     offline" (which both otherwise look like a park timeout at the broker)
+ *     and stop retrying. The signal is authenticated like every tunnel frame:
+ *     it arrives inside the AEAD channel of a handshake whose transcript the
+ *     client verified against the pinned daemon key, so the broker can't forge
+ *     it; and the broker, which knows the routes, can't elicit it either (no
+ *     auth token). A tombstone keeps only the per-epoch route + auth tokens for
+ *     its window — the pair root is dropped at revoke.
+ *
+ * ## Reconnect authentication (why no stable client key)
+ *
+ * The handshake carries only a client *ephemeral* key (regenerated per
+ * handshake) — there is no persistent client identity key. So a reconnect
+ * authenticates the client by **possession of the epoch AUTH token**
+ * `HKDF(pairRoot, "rv-auth"‖epoch)`, which derives from `pairRoot` — a secret
+ * only the paired client and daemon share (it fell out of the original ECDH).
+ * The daemon parks on the pairing's epoch ROUTE, and on that connection the
+ * `verifyAuthToken` predicate accepts a hello whose sealed auth equals the same
+ * epoch's auth token (constant-time). The route and auth are separate one-way
+ * HKDF outputs: the broker sees every route and can't compute an auth from it.
+ * (pair/v1 used ONE value for both, so a broker could replay a logged route as
+ * the proof and be served.) The stored `fingerprint` (of the first handshake's
+ * ephemeral key) is a stable display/revocation handle, not an auth input.
+ *
+ * ## Legacy (pair/v1) pairings
+ *
+ * A v1 `pairings.json` is loaded with every record flagged `legacy`: listed and
+ * revocable, never served. The daemon still parks on a legacy pairing's routes
+ * (the epoch route is unchanged from v1) so that pairing's not-yet-upgraded
+ * client reaches it and is told to re-pair — see `respondToLegacyHandshake` —
+ * rather than timing out. v1 records are not upgraded in place: v1 let the
+ * broker pair as a client, so any v1 record may be the broker's own.
+ */
+
+/** `pairings.json` format. v2 = pairings made under pair/v2 (route/auth
+ *  split). A v1 file still loads, every record flagged `legacy`. */
+declare const PAIRINGS_VERSION: 2;
+/** One persisted pairing. Written verbatim to `pairings.json`. */
+interface PairingRecord {
+    /** The client ephemeral public key from the FIRST handshake (a snapshot —
+     *  reconnects use fresh ephemerals; this is not an auth input). */
+    clientPub: string;
+    /** Human-facing label the client chose on `pair accept`. */
+    name: string;
+    /** `identityFingerprint(clientPub)` from the first handshake — the stable
+     *  display + revocation handle. */
+    fingerprint: string;
+    /** ISO-8601 first-pair timestamp. */
+    createdAt: string;
+    /** ISO-8601 of the most recent successful (re)connect. */
+    lastSeen: string;
+    /** Long-term shared secret (base64), from which epoch routing tokens derive. */
+    pairRoot: string;
+    /** Rendezvous endpoint to reconnect through. */
+    rendezvousUrl: string;
+    /** Set on a pairing made under the retired pair/v1 protocol: listed and
+     *  revocable, never served — its client is told to re-pair. */
+    legacy?: true;
+    /** Set when this pairing was made under an offer minted with
+     *  `agentproto pair offer --host` (PR-C) — i.e. the offering daemon's own
+     *  intent, recorded server-side at handshake time from the OfferEntry it
+     *  itself created, never from the (unauthenticated) `scope` param a client
+     *  presented in the offer URL. Absent for an ordinary remote-control
+     *  pairing. Purely informational here — it does not change how this
+     *  pairing is served. */
+    scope?: "host";
+    /** Set on a record returned by `list()` for a local device (see "Local
+     *  devices"): it has no rendezvous, `clientPub`/`pairRoot`/`rendezvousUrl`
+     *  are empty strings. Never written to the `pairings` array of the file. */
+    local?: true;
+}
+/** A revoked pairing still answered with `pairing_revoked` until `expiresAt`
+ *  (see "Revocation" above). Persisted in `pairings.json` under `revoked`. */
+interface RevokedPairingRecord {
+    /** The revoked pairing's fingerprint. */
+    fingerprint: string;
+    /** Its client label. */
+    name: string;
+    /** Rendezvous endpoint its client reconnects through. */
+    rendezvousUrl: string;
+    /** ISO-8601 revocation time. */
+    revokedAt: string;
+    /** ISO-8601 end of the grace window; the tombstone is dropped after it. */
+    expiresAt: string;
+    /** The epoch route (parked on) + auth (verified) tokens covering the window
+     *  (previous epoch at revoke time through the epoch of `expiresAt`) —
+     *  derived from the pair root at revoke time so the root itself need not be
+     *  kept. */
+    routes: ({
+        epoch: number;
+    } & RouteAuthTokens)[];
+}
+/** The tunnel `error` code a revoked pairing's client receives. */
+declare const PAIRING_REVOKED_CODE: "pairing_revoked";
+/** Mode of a served channel — first-contact offer vs. an established reconnect. */
+type PairingChannelMode = "offer" | "reconnect";
+/** Context handed to the injected `serve` when a channel comes up. */
+interface PairingChannelContext {
+    mode: PairingChannelMode;
+    /** Stable pairing fingerprint (present for reconnect; for an offer it's the
+     *  freshly-derived one). */
+    fingerprint: string;
+    /** Client label. */
+    name: string;
+    /** This pairing's OWN recorded scope (mirrors `PairingRecord.scope`) —
+     *  `"host"` when the offer that produced it was minted with
+     *  `agentproto pair offer --host`, absent for an ordinary remote-control
+     *  pairing. Present on BOTH the offer and every reconnect context, so
+     *  `serve` can gate scope-restricted routes (e.g. device-inference
+     *  proxying) the same way on first contact and on every later reconnect. */
+    scope?: "host";
+}
+/** Handle to a live served channel — the registry closes it on teardown. */
+interface PairingChannelHandle {
+    close(): Promise<void>;
+}
+interface CreatedOffer {
+    /** The one-time offer secret (base64url) — the URL's `s`. Never on the wire:
+     *  the broker only ever sees its derived route. */
+    secret: string;
+    /** Offer expiry, unix seconds. */
+    exp: number;
+    /** The full `agentproto://pair?…` offer URL. */
+    url: string;
+    /** The daemon's identity fingerprint (shown to the human at accept time). */
+    fingerprint: string;
+    /** The rendezvous the offer routes through. */
+    rendezvousUrl: string;
+    /** True when `rendezvousUrl` is the hosted default — i.e. neither an explicit
+     *  `--rendezvous` nor a configured `pairing.rendezvous` applied, so the offer
+     *  falls back to `HOSTED_RENDEZVOUS_URL`. Surfaced so `pair offer` can flag,
+     *  never silently, that the daemon is relaying through our infrastructure. */
+    rendezvousIsHostedDefault: boolean;
+    /** Echoes `CreateOfferInput.scope`. `"host"` when minted with `--host`;
+     *  absent for a plain offer. */
+    scope?: "host";
+}
+interface CreateOfferInput {
+    /** Time-to-live in ms. Default 10 minutes. */
+    ttlMs?: number;
+    /** Rendezvous URL override; falls back to the configured default. */
+    rendezvousUrl?: string;
+    /** Mint a HOST-scoped offer (PR-C): the accepting side may register this
+     *  daemon as a driveable host (`devices add`), not just remote-control it.
+     *  Recorded on the resulting `OfferEntry`/`PairingRecord` server-side — this
+     *  is the authoritative record of what was granted, independent of the
+     *  `scope` param an accepting client's offer URL happens to carry. */
+    scope?: "host";
+}
+interface PairingRegistryDeps {
+    /** Lazily load (create on first use) the daemon identity. Kept lazy so a
+     *  daemon that never pairs never writes an identity file. */
+    loadIdentity: () => Promise<DaemonIdentity>;
+    /** Path to `pairings.json`. Defaults to `~/.agentproto/pairings.json`. */
+    pairingsPath?: string;
+    /** Configured rendezvous URL (from `config.pairing.rendezvous`). Three states:
+     *  - `undefined` (key absent) → `createOffer` falls back to the hosted default
+     *    (`HOSTED_RENDEZVOUS_URL`).
+     *  - a non-empty URL → that endpoint is the default for offers.
+     *  - `""` (explicitly empty) → an explicit opt-out: no default applies, so an
+     *    offer without `--rendezvous` fails closed. Wire it through verbatim (do
+     *    not coerce `""` to `undefined`) or the opt-out silently reverts to the
+     *    hosted default. */
+    defaultRendezvousUrl?: string;
+    /** Dial a rendezvous WS and adapt it to a FrameSink. Injected by the CLI
+     *  (uses `ws` + `wrapWebSocket`). Rejects if the dial fails. The `signal`
+     *  aborts on registry shutdown. */
+    dial: (wsUrl: string, signal: AbortSignal) => Promise<FrameSink>;
+    /** Serve the E2E-wrapped channel (the CLI builds `createTunnelServer` over
+     *  it with the same config `serve --connect` uses). */
+    serve: (sink: E2eFrameSink, ctx: PairingChannelContext) => PairingChannelHandle;
+    /** Injectable clock (ms). Defaults to Date.now. */
+    now?: () => number;
+    /** Diagnostic log sink. */
+    log?: (line: string) => void;
+    /** Reconnect backoff floor / ceiling (ms). Defaults 1s / 30s. */
+    reconnectMinMs?: number;
+    reconnectMaxMs?: number;
+    /** How long a parked daemon socket waits for a client hello before recycling
+     *  the connection. Kept just under the broker's park timeout. Default 110s. */
+    handshakeTimeoutMs?: number;
+    /** How long a revoked pairing is still answered with `pairing_revoked` (see
+     *  "Revocation" above). Default 14 days; `0` disables tombstones, so a
+     *  revoked client just stops finding the daemon. */
+    revokedGraceMs?: number;
+}
+interface PairingRegistry {
+    /** Mint a one-time offer + start dialing the rendezvous for it. */
+    createOffer(input?: CreateOfferInput): Promise<CreatedOffer>;
+    /** All persisted pairings (copies). Loads `pairings.json` on first call. */
+    list(): Promise<PairingRecord[]>;
+    /** Rename a pairing by fingerprint or name (cosmetic only — no effect on
+     *  auth or routing). Returns false when nothing matched; throws on an
+     *  empty `newName`. */
+    rename(idOrName: string, newName: string): Promise<boolean>;
+    /** Drop a pairing by fingerprint or name; stops its rendezvous connections.
+     *  Returns false when nothing matched. */
+    revoke(idOrName: string): Promise<boolean>;
+    /** Is a channel (offer or reconnect) currently served for this fingerprint? */
+    isOnline(fingerprint: string): boolean;
+    /** Start standing reconnect connections for every persisted pairing. Call
+     *  after the gateway is up (so the injected `serve` can reach it). */
+    startAutoconnect(): Promise<void>;
+    /** Tear down every offer + reconnect connection and served channel. */
+    shutdown(): Promise<void>;
+}
+/** What `mintLocalDevice` hands back. `bearer` is shown ONCE to the caller
+ *  (write it to the client's config); the host never logs or stores it. */
+interface LocalDeviceCredential {
+    bearer: string;
+    fingerprint: string;
+    name: string;
+    createdAt: string;
+}
+/** The registry `createPairingRegistry` returns: the daemon-facing
+ *  `PairingRegistry` plus the optional local-device credential. */
+interface PairingHostRegistry extends PairingRegistry {
+    /** Mint a paired-device record for a loopback client and return its bearer.
+     *  Visible in `list()`, revocable with `revoke()`. Throws on an empty name. */
+    mintLocalDevice(input: {
+        name: string;
+    }): Promise<LocalDeviceCredential>;
+    /** Constant-time check of a device bearer. `null` for anything unknown,
+     *  malformed or revoked; a revoke is honoured on the very next call. */
+    verifyDeviceBearer(bearer: string): Promise<{
+        fingerprint: string;
+        name: string;
+    } | null>;
+}
+/**
+ * Read-only snapshot of `pairings.json` for callers that just want the
+ * persisted records — no `dial`/`serve`/`loadIdentity` deps, no rendezvous
+ * connections started (e.g. `agentproto doctor`'s devices check). Mirrors
+ * `ensureLoaded`'s parse + v1-legacy flagging; never throws — a missing or
+ * malformed file just yields `[]`.
+ */
+declare function readPairingsSnapshot(path?: string): Promise<PairingRecord[]>;
+declare function createPairingRegistry(deps: PairingRegistryDeps): PairingHostRegistry;
+
+/**
+ * Rate-limited failure logging for reconnect loops.
+ *
+ * A standing reconnect loop (the outbound tunnel, a pairing rendezvous) whose
+ * peer is permanently gone re-dials on backoff forever. Logging every single
+ * failure buries the daemon log — a single dead pairing produced ~85% of one
+ * 2.9MB never-rotated `~/.agentproto/daemon.log`, and the tunnel reconnect
+ * spam another chunk. This gate logs the FIRST failure per key immediately,
+ * then at most one line per `windowMs`, and when it does emit again it carries
+ * the count of failures it swallowed in between. A successful connect resets
+ * the key so the next outage logs promptly again.
+ *
+ * Deliberately dependency-free: a per-key `{ lastLoggedAt, suppressed }` map.
+ * `now` is injectable so tests can advance the clock without real timers. This
+ * only changes logging cadence — reconnect timing/backoff is untouched.
+ */
+interface ReconnectLogGate {
+    /**
+     * Record a failure for `key`. Returns the line to log now — the given
+     * `message`, with a `(N failures suppressed)` suffix when repeats were
+     * swallowed since the last emit — or `null` to stay quiet this time.
+     */
+    onFailure(key: string, message: string): string | null;
+    /** Reset suppression for `key` after a successful connect. */
+    onSuccess(key: string): void;
+}
+declare function createReconnectLogGate(opts?: {
+    windowMs?: number;
+    now?: () => number;
+}): ReconnectLogGate;
+
+interface DialRendezvousOptions {
+    /** A `ws`-compatible agent (e.g. an HTTPS proxy agent). `ws` ignores
+     *  `HTTPS_PROXY` on its own, so a host behind a proxy passes one here. */
+    agent?: Agent;
+}
+/**
+ * Dial a rendezvous broker outbound and adapt the socket to a `FrameSink`.
+ * The default `PairingRegistryDeps.dial`. Rejects if the dial fails; honours
+ * `signal` so a registry shutdown tears down an in-flight dial promptly.
+ */
+declare function dialRendezvous(url: string, signal: AbortSignal, opts?: DialRendezvousOptions): Promise<FrameSink>;
+
+interface ServeLoopbackHttpOptions {
+    /** The local HTTP app the paired channel is forwarded to. Must be a
+     *  loopback http(s) URL (127.0.0.0/8, ::1 or localhost): a paired peer must
+     *  never be able to steer the host at another machine. */
+    target: URL | string;
+    /** Headers set on EVERY forwarded request, overriding any same-named header
+     *  the peer sent (e.g. the host app's own bearer). */
+    injectHeaders?: Readonly<Record<string, string>>;
+    /** Pathnames a peer may request. `"/mcp"` matches exactly, `"/api/*"`
+     *  matches `/api` and everything below it, a RegExp is tested against the
+     *  pathname. Omitted: any path. `[]`: nothing. A denied request gets a 403
+     *  `path_not_allowed` response and never reaches the target. */
+    allowPaths?: readonly (string | RegExp)[];
+    /** Label in the tunnel hello. Default "loopback-http". */
+    label?: string;
+    httpForwardTimeoutMs?: number;
+}
+/**
+ * Build a `PairingRegistryDeps.serve` that forwards the paired, E2E-wrapped
+ * channel to a local HTTP app: `http_request` frames become fetches against
+ * `target` (with `injectHeaders` applied), responses stream back. Spawn, PTY
+ * and WebSocket frames are not served.
+ */
+declare function serveLoopbackHttp(opts: ServeLoopbackHttpOptions): (sink: E2eFrameSink, ctx: PairingChannelContext) => PairingChannelHandle;
+
+export { type CreateOfferInput, type CreatedOffer, type DialRendezvousOptions, type LocalDeviceCredential, PAIRINGS_VERSION, PAIRING_REVOKED_CODE, type PairingChannelContext, type PairingChannelHandle, type PairingChannelMode, type PairingHostRegistry, type PairingRecord, type PairingRegistry, type PairingRegistryDeps, type ReconnectLogGate, type RevokedPairingRecord, type ServeLoopbackHttpOptions, createPairingRegistry, createReconnectLogGate, dialRendezvous, readPairingsSnapshot, serveLoopbackHttp };