fix(cli): cap cloud-managed shell command timeouts

[kilo-code-bot]

Summary

• let hosted runtimes cap shell command duration through KILO_COMMAND_TIMEOUT_MAX_MS
• surface environment-specific timeout guidance from optional KILO_COMMAND_TIMEOUT_MAX_MS_MESSAGE when that cap terminates work
• cover shell tool, direct shell execution, and command-template expansion paths

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

Incremental review through commit 7952443028 (test: provide runtime flags to timeout coverage).

The single new commit adds RuntimeFlags.defaultLayer to the shell integration test layer in command-timeout.test.ts. This is a correct fix — shell.ts line 366 yields RuntimeFlags.Service, so the shell.instance(...) test would have failed with a missing service defect without this layer. All previously flagged issues remain resolved.

Area	Status
command-timeout.ts — race timer fires at exact env cap	Clean
command-timeout.ts — drain() / wait() logic	Clean
prompt.ts — timeout variable holds message string or undefined	Clean
shell.ts — kilocode_change markers, clamp/message usage	Clean
command-timeout.test.ts — RuntimeFlags.defaultLayer added to shell layer	Fixed
command-timeout.test.ts — afterEach restores env vars; test isolation	Clean

Files Reviewed (5 files)

• .changeset/calm-shells-timeout.md
• packages/opencode/src/kilocode/command-timeout.ts
• packages/opencode/src/session/prompt.ts
• packages/opencode/src/tool/shell.ts
• packages/opencode/test/kilocode/command-timeout.test.ts

---

_{Reviewed by claude-4.6-sonnet-20260217 · 538,127 tokens}

_{Review guidance: REVIEW.md from base branch main}

[marius-kilocode]

Please let's reiterate on this