feat: add small route HttpApi coverage

[Astro-Han]

Summary

Add local Effect HttpApi declarations and handlers for ordinary JSON file, project, memory, and external-result routes.

Why

Related to #936.

This gives the next Hono-to-HttpApi migration slice local coverage without switching the production server off Hono.

Related Issue

Related to #936

Human Review Status

Pending

Review Focus

Please focus on Hono wire-behavior parity for JSON body parsing, project 404 handling, memory safe-mode errors, and route-inventory classification.

Risk Notes

Production server routing is unchanged and remains on Hono in this PR. The new HttpApi schemas use broad Schema.Any only where the current route wire shape is Zod-owned or app-specific and preserving Hono behavior is more important than overstating OpenAPI precision.

Skipped checklist items: visible UI/copy check is not applicable; platform/packaging check is not applicable; docs/release/dependency/permission/generated-content checks are not applicable.

How To Verify

Baseline focused routes: 24 passed before changes
Focused route coverage: 34 passed after changes, 169 expect() calls
Typecheck: GOMAXPROCS=2 bun run typecheck passed
Diff check: git diff --check passed

Screenshots or Recordings

Not applicable: no visible UI changes.

Checklist

How to use this checklist:

• Tick a box by replacing [ ] with [x]. Do not edit, add, or remove items.
• The bot-applied label items can only be honestly ticked AFTER the PR is opened and the labeler / priority-triage bots have run — return to the PR description and tick them then.
• Most items are required. The few that are conditional are explicitly marked (conditional); for those, leave unticked if they truly do not apply and explain why in Risk Notes. All other items must be ticked before requesting human review.

• Type label — this PR carries exactly one of 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.
• Routing labels — this PR carries at least one of 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.
• Priority label — this PR carries exactly one of P0, P1, P2, P3. The priority-triage bot suggests one on PR open. Confirm or override, then tick this.
• Human Review Status above is set to Pending, Approved by @<reviewer>, or Not required: <reason> (default is Pending; "not required" is restricted to bot-authored low-risk PRs).
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed, with screenshots or recordings. Leave unticked only if no visible UI or copy changed.
• (conditional) I considered macOS and Windows impact for platform, packaging, updater, signing, paths, shell, or permissions changes. Leave unticked only if no platform/packaging surface was touched.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant. Leave unticked only if none of those surfaces was touched.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

[coderabbitai]

Warning

Review limit reached

@Astro-Han, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 59 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8703cbae-4135-4cb6-8a96-a84e3a5260b7

📥 Commits

Reviewing files that changed from the base of the PR and between b9fbcef and bb5f18c.

📒 Files selected for processing (19)

• packages/opencode/src/server/instance/external-result.ts
• packages/opencode/src/server/instance/file.ts
• packages/opencode/src/server/instance/memory.ts
• packages/opencode/src/server/instance/project.ts
• packages/opencode/src/server/routes/instance/httpapi/groups/common.ts
• packages/opencode/src/server/routes/instance/httpapi/groups/external-result.ts
• packages/opencode/src/server/routes/instance/httpapi/groups/file.ts
• packages/opencode/src/server/routes/instance/httpapi/groups/memory.ts
• packages/opencode/src/server/routes/instance/httpapi/groups/project.ts
• packages/opencode/src/server/routes/instance/httpapi/handlers/external-result.ts
• packages/opencode/src/server/routes/instance/httpapi/handlers/file.ts
• packages/opencode/src/server/routes/instance/httpapi/handlers/memory.ts
• packages/opencode/src/server/routes/instance/httpapi/handlers/project.ts
• packages/opencode/test/server/external-result-routes.test.ts
• packages/opencode/test/server/file-routes.test.ts
• packages/opencode/test/server/memory-routes.test.ts
• packages/opencode/test/server/project-init-git.test.ts
• packages/opencode/test/server/project-routes.test.ts
• packages/opencode/test/server/route-inventory-harness.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/i936-httpapi-small-routes

---

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.}

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.