feat(python): async send_op + AsyncDaemonConnection (partial #65)

[zackees]

Summary

Extends the AsyncDaemon scaffold (PR #78) with the method set that issue #65 explicitly targets: "Daemon/DaemonConnection: send_op and any other HTTP call".

Async methods added

• send_op_async -- tokio/reqwest counterpart to the blocking send_op helper (used by every DaemonConnection HTTP call).
• AsyncDaemon.ensure_running() -- async daemon bring-up; health poll uses tokio::time::sleep so the event loop isn't pinned.
• AsyncDaemon.stop() -- async counterpart to Daemon.stop.
• AsyncDaemonConnection -- new class with:
  • build, deploy, monitor -- async bool-returning wrappers.
  • build_result, deploy_result, monitor_result -- async structured-dict wrappers (same keys as the sync *_result methods: success, message, exit_code, stdout, stderr).
  • __aenter__ / __aexit__ so callers can async with AsyncDaemonConnection(...) as conn:.
• connect_daemon_async() factory, mirroring connect_daemon.
• Re-exports: AsyncDaemon, AsyncDaemonConnection, connect_daemon_async from fbuild; AsyncSerialMonitor from fbuild.api.

The sync surface is untouched -- this is purely additive per the issue's Non-goals.

Still remaining for #65

• AsyncSerialMonitor.read_lines / write / write_json_rpc. These need the persistent WebSocket state on AsyncSerialMonitor refactored to be Send + Sync across .await points (flagged in the scaffold comment added by PR feat(python): AsyncSerialMonitor scaffold via pyo3-async-runtimes (partial #65) #73). Follow-up PR.

Test plan

• uv run cargo test -p fbuild-python -- 11 tests pass (8 existing + 3 new).
• uv run cargo clippy -p fbuild-python --all-targets -- -D warnings -- clean.
• uv run cargo check --workspace --all-targets -- clean.
• New tests spin a minimal in-process HTTP mock (raw tokio::net::TcpListener, no extra dev deps) and exercise send_op_async against three paths:
  • send_op_async_parses_success_response
  • send_op_async_parses_failure_response (guards exit_code / stderr parity with the sync API)
  • send_op_async_returns_failure_outcome_on_connection_error (guards against panics when the daemon is down)

The shared parse_outcome / outcome_to_pydict helpers are now exercised from both the sync and async paths, so the structured-result schema stays identical for callers migrating to async.

---

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

[coderabbitai]

Warning

Rate limit exceeded

@zackees has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 43 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 57 minutes and 43 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: df8313da-fa74-410a-9cbe-98e4b831d3f6

📥 Commits

Reviewing files that changed from the base of the PR and between 41982b2 and 7560b30.

📒 Files selected for processing (3)

• crates/fbuild-python/src/lib.rs
• python/fbuild/__init__.py
• python/fbuild/api/__init__.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/65-async-send-op

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}