dzejkop/client improvements

[Dzejkop]

• chore: allow modifying the request prior to sending
• chore: allow sypplying external client but preserve required configuration

---

Note

Low Risk
Refactor and new public hooks around the same verify-and-seal logic; no change to attestation or channel crypto behavior beyond call structure.

Overview
Extends FaceVerifierClient so embedders can tune HTTP before send without bypassing sealing, attestation checks, or response verification.

new now builds through with_http_client_builder, which still forces cookie store (ALB affinity), connect timeout, and request timeout on whatever reqwest::ClientBuilder the caller supplies. Assignment and match flows are split into build helpers (build_assignment_request, build_match_request → builder + ResponseOpener) and send helpers (request_assignment_with, request_match_with); the one-shot request_* methods delegate to those. The private request_match_with_consumer path is removed in favor of the public request_match_with API. Endpoint path constants are inlined as /v1/enclave-assignment and /v1/matches.

Match HTTP tests move from tests/matches.rs into an inline mod tests in client.rs, using a local helper that exercises request_match_with instead of the removed private method.

^{Reviewed by Cursor Bugbot for commit 62b5bf0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Copilot]

Pull request overview

Refactors FaceVerifierClient to support more flexible HTTP customization: callers can modify reqwest::RequestBuilders before sending, and can supply an externally configured reqwest::ClientBuilder, while preserving the client’s required settings (cookie store + timeouts) and keeping the existing high-level new / request_* APIs intact.

Changes:

• Add with_http_client_builder to allow constructing the client from an externally configured reqwest::ClientBuilder while enforcing required HTTP settings.
• Split assignment/match flows into “build request” helpers and “send/verify” helpers (build_* + request_*_with).
• Inline endpoint paths in the new builder helpers (removing the old path constants).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[0xOsiris]

Can we keep these constant?

[Dzejkop]

they're used only to construct the urls? It's easier to read if they're inline imo

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7bf0046. Configure here.}