Summary

PR #2759 (merged) broke CI's Typecheck (tsc) job on staging , the only red check on the staging→main merge (#2760); every other job (lint, deps:check, both test suites across all shards) already passed on the merged commit.

Root cause: #2759's isAdminView change narrowed handleChatStreamRequest's first parameter from a bare Context to Context<HonoContext> (to read c.var.adminViewingUserId). chat-entry.ts's own Hono app (the dedicated chat-service, a separate Node process from the Cloudflare Worker http/app.ts runs behind) was still an untyped new Hono(), so its existing cast at the call site stopped being a safe narrowing and TS refused it:

Conversion of type 'Context<BlankEnv, "/chat", BlankInput>' to type 'Context<HonoContext, any, {}>' may be a mistake

Fix

Type the app itself (new Hono<HonoContext>()) instead of casting past the error , removes the cast entirely rather than reaching for as unknown as T, which CLAUDE.md rules out ("NEVER cast").

Verified safe: nothing in chat-entry.ts or in handleChatStreamRequest's body ever reads c.env , this Node service reads process.env directly; HonoContext's Bindings only ever get populated behind the Worker. Only c.var.adminViewingUserId is read, and Hono's Variables store works identically regardless of platform, so the type is now honest about the one thing this context actually uses, with no behavior change.

Test plan

• pnpm --filter @zero/server run types , clean (was the one failing CI job)
• pnpm --filter @zero/mail run types , clean
• pnpm dlx oxlint@1.78.0 apps/server/src/runtime/chat-entry.ts --deny-warnings , clean (CI's pinned lint version)
• pnpm deps:check , clean
• Confirmed via gh run watch on the staging→main CI run: every other job (autofix/lint, deps:check, Server tests × 4 shards, Mail app tests, Deploy scope tests) already passes on the merged commit , this is the only fix needed for that run to go green

🤖 Generated with Claude Code

https://claude.ai/code/session_01SfYKPYHXdMgrPLuKhXvWed

Greptile Summary

This PR fixes the chat-service typecheck by typing its Hono application with the context expected by handleChatStreamRequest and removing the call-site assertion.

• Aligns the /chat route context with the shared handler signature.
• Removes a cast in accordance with repository guidance.
• Introduces no immediate runtime behavior change, although the selected context type promises more values than this Node entry point supplies.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking type-modeling concern that should be tightened to prevent future routes from relying on unavailable context values.

The current request path does not access the bindings or required variables missing from this Node service, so the change fixes typechecking without altering current behavior; the remaining concern is the broader unsound context contract exposed to future code.

Files Needing Attention: apps/server/src/runtime/chat-entry.ts

Important Files Changed

### Issue 1
apps/server/src/runtime/chat-entry.ts:54
**Context promises unavailable values**

Typing the whole Node app as `HonoContext` tells every route that the full `CedarRuntimeEnv` and required `auth` variable exist, but this entry point only installs CORS middleware and initializes neither. The current routes do not access those values, so this is non-blocking today, but a future route could compile against `c.env` or `c.var.auth` and then receive missing