Remove Chrome workflow companion - #79
Conversation
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (10)
📒 Files selected for processing (62)
💤 Files with no reviewable changes (58)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request removes the Chrome workflow companion, its CLI, extension package, browser relay protocols, companion server, dedicated tests, CI job, package feature, and related documentation. Browser automation remains exposed through the existing host capability model. ChangesChrome companion removal
Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: ⚪ Minimal · up to This change removes the Chrome workflow companion and its associated code, assets, tests, documentation, and CI integration; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (3 skipped: 3 unsupported.) Warning Your free Security trial is over. An organization admin can activate Security or dismiss this notice. Comment |
Summary
reqwestscoped to the optionalhost-capsfeature and development tests; testing-only dependencies remain under[dev-dependencies]rather than a public feature.Validation
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-targets --all-featuresgit diff --checkSummary by CodeRabbit
Breaking Changes
Documentation