Add SSH proxy authorization probe

README.md

@@ -123,6 +123,7 @@ The bootstrap implementation provides:
   - `geth ssh revocation export --out <path> [--format jsonl|openssh-krl-spec|openssh-krl] [--subject <principal>]`
   - `geth ssh revocation import <path> [--format jsonl|openssh-krl-spec] [--subject <principal>]`
   - `geth ssh revocation sync <node-id>`
+- SSH proxy authorization probe: `geth ssh proxy <node-id>`
 - pipe registry/connect commands: `geth pipe listen <name>` and
   `geth pipe connect <name> [--node <node-id>]`
 
@@ -166,6 +167,11 @@ Remote pipe connect uses the same protected Iroh control path and requires
 `pipe.connect` on `resource:pipe:<name>`. The current prototype records a remote
 connection attempt and whether a listener exists; byte streaming and forwarding
 are still future work.
+`geth ssh proxy <node-id>` also uses the protected Iroh control path. The remote
+peer validates the caller's endpoint/card binding and requires
+`ssh_proxy.connect` on `resource:ssh-proxy:local` before returning proxy
+connection metadata. The current prototype does not carry SSH bytes or connect
+to remote sshd yet; it only proves the authorization gate.
 Document sync is a bootstrap JSON last-writer-wins path before Automerge:
 manual `geth document sync <node-id> <name>` and background live-sync require
 `document.read` on `resource:document:<name>` and import only state that is not
@@ -182,8 +188,6 @@ When `[iroh].local_discovery = true`, the daemon also advertises and discovers
 signed peer cards on LAN using a geth-specific mDNS TXT payload. That payload is
 candidate metadata only; all geth node-to-node requests still run over Iroh.
 
-Other command groups exist as explicit stubs: `ssh proxy`.
-
 ## Resource Modules
 
 Everything meaningful is modeled as a resource. Planned resource kinds are: