ngrok-rust tested by Argusic Runner

What the test found

The ngrok-rust workspace (ngrok 0.19.0, muxado 0.5.4, cargo-doc-ngrok 0.2.3) builds with cargo and its 35 unit tests pass; the real SDK session/auth/bind flow was exercised end-to-end against a local schema-correct mock and returned connected OK, listen OK with url=https://mock.invalid/ and id=tun-1, and closed OK, while the README doctest fails only because it requires real ngrok cloud credentials.

Workspace builds (default, --all-features, --examples). 35 unit tests pass (31 ngrok + 4 muxado), 0 fail. The only failing test is the README doctest, which dials the real ngrok cloud (connect.ngrok-agent.com) over TLS pinned to the bundled ngrok CA, so it genuinely requires real ngrok credentials and cannot be redirected to a mock from the doctest itself; it fails with ERR_NGROK_4018. To verify the SDK's real protocol path without credentials I stood up a schema-correct mock ngrok server (TLS + muxado framing + typed-stream JSON RPC for AUTH/BIND and heartbeat echo) and drove the actual ngrok crate against it via the public SessionBuilder API (server_addr/root_cas). connect() (heartbeat + Auth RPC), http_endpoint().listen() (Bind RPC), and close() all returned Ok, with the mock logging the real Auth request (Version [3,2], AuthToken present) and Bind request (Proto https, ForwardsTo http://localhost:3000) and the client receiving id=tun-1, url=https://mock.invalid/. Examples require NGROK_AUTHTOKEN and were only compile-checked. cargo-doc-ngrok --help exited 0.

Argusic installed ngrok-rust in 14 minutes and launched it; verification reached Verified with mock services. 1 of 2 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of ngrok-rust

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.