refactor(opencode): retire PTY Hono route tree - #1450
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
💤 Files with no reviewable changes (3)
📝 WalkthroughWalkthroughRemoves the Hono-based ChangesPTY Hono Route Removal
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration. 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. Comment |
Summary
Retire the legacy Hono route tree for PTY ordinary HTTP endpoints and keep PTY HTTP behavior on the Effect HttpApi handlers.
Why
The PTY JSON and connect-token endpoints already have local HttpApi coverage. Keeping
InstanceRoutes().route("/pty", PtyRoutes())left a retired ordinary Hono boundary in production inventory, while the real native PTY websocket surface still needs to remain explicit.Related Issue
Related to #936
Human Review Status
Pending
Review Focus
Please check that ordinary PTY HTTP endpoints are no longer inventoried as Hono routes, while
/pty/:ptyID/connectremains a native websocket special surface.Risk Notes
PTY websocket compatibility is intentionally still native, not converted to ordinary HttpApi. The visible UI check is skipped because no UI or copy changed. No docs, generated files, dependencies, permissions, credentials, or local file behavior changed.
Fresh-eye result: no P0/P1 findings. I checked whether this was the simplest, most reassuring, and most complete boundary. The current split keeps only the websocket compatibility helper and removes the ordinary Hono tree without widening scope.
How To Verify
Screenshots or Recordings
Not applicable: no visible UI changes.
Checklist
bug,enhancement,task,documentation. Type labels are author-added; the labeler bot does NOT assign them. Add the label in the GitHub UI, then tick this.app,ui,platform,harness,ci. The labeler bot assigns these on PR open based on changed paths. Confirm the bot's choice (or override if wrong), then tick this.P0,P1,P2,P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.Pending,Approved by @<reviewer>, orNot required: <reason>(default isPending; "not required" is restricted to bot-authored low-risk PRs).dev, and my PR title and commit messages use Conventional Commits in English.Summary by CodeRabbit
Refactor
Tests