Add wsh debugterm

[Copilot]

wsh debugterm currently decodes terminal bytes sourced from backend block files. This extends it with a stdin-driven path so FE-emitted payloads like ["...", "..."] can be decoded directly without requiring block lookup/RPC in that mode.

• CLI surface

  • Added new mode: --mode stdin
  • Updated mode help text to: hex, decode, stdin
  • Centralized mode validation via getDebugTermMode()

• Execution path split

  • Added mode-aware pre-run (debugTermPreRun):
    • stdin mode: skips RPC setup
    • hex/decode: keeps existing RPC setup behavior
  • stdin mode now:
    • reads all stdin
    • parses JSON as []string
    • concatenates entries and runs existing decode formatter

• Parsing support

  • Added parseDebugTermStdinData([]byte) ([]byte, error)
  • Error messaging explicitly requires a JSON array of strings

• Tests

  • Added focused coverage for:
    • valid stdin JSON array parsing + decoded output
    • invalid stdin JSON input

stdinData, _ := io.ReadAll(WrappedStdin)
termData, err := parseDebugTermStdinData(stdinData) // expects []string JSON
if err != nil { return err }
WriteStdout("%s", formatDebugTermDecode(termData))

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[cloudflare-workers-and-pages]

Deploying waveterm with    Cloudflare Pages

Latest commit:	4db8c15
Status:	✅  Deploy successful!
Preview URL:	https://8c2c280a.waveterm.pages.dev
Branch Preview URL:	https://copilot-add-wsh-debugterm-co.waveterm.pages.dev

View logs

[kilo-code-bot]

CRITICAL: Incorrect offset calculation for circular files

This line uses waveFile.Size - readSize which is incorrect for circular files. When a terminal file is circular and Size > MaxSize, this calculation will produce an offset beyond the actual available data.

The correct calculation should account for the data start index:

readOffset := waveFile.DataStartIdx() + dataLength - readSize

This ensures:

• For regular files: DataStartIdx() returns 0, so it becomes dataLength - readSize (equivalent to Size - readSize)
• For circular files: It correctly accounts for the starting index of available data, preventing out-of-bounds reads

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	1
WARNING	0
SUGGESTION	0

Issue Details (click to expand)

CRITICAL

File	Line	Issue
pkg/wshrpc/wshserver/wshserver.go	829	Incorrect offset calculation for circular files - uses waveFile.Size - readSize instead of waveFile.DataStartIdx() + dataLength - readSize

Files Reviewed (6 files)

• cmd/wsh/cmd/wshcmd-debugterm.go - New file, no issues
• cmd/wsh/cmd/wshcmd-debugterm_test.go - New file, no issues
• frontend/app/store/wshclientapi.ts - Generated file, no issues
• frontend/types/gotypes.d.ts - Generated file, no issues
• pkg/wshrpc/wshclient/wshclient.go - Generated file, no issues
• pkg/wshrpc/wshserver/wshserver.go - 1 critical issue

---

Fix these issues in Kilo Cloud