docs(coder): point runbook §0 at the PTY harness

a3c8197d4eb6 · AtlantisPleb · · parent 7325bb84672b

docs(coder): point runbook §0 at the PTY harness

§0 forbids closing an interactive-TUI issue on headless evidence but did not
say what satisfies it. Name the harness, and state that the completion gate
reaches neither it nor `cargo fmt` for this crate (#124), so it is run by
hand.

Refs #116
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K7q2vA5LJroLTR6ZFbRq6j
Co-Authored-By
Claude Fable 5 <noreply@anthropic.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

  • modified docs/coder/runbook.md

Diff

1 file changed, +7 -0

docs/coder/runbook.md modified +7

@@ -32,6 +32,13 @@ forge remote, never GitHub (best practices R2, R3). For CLI code changes

32 32
the completion gate is `pnpm run check`; docs-only changes push with
33 33
`--no-verify` after the docs checks.
34 34
35
A change to the coder-lite TUI has one more step, because `pnpm run check`
36
does not reach it. `cargo test -p coder-lite --test interactive_pty` drives
37
the real binary on a pseudo-terminal and asserts on the rendered cells; it is
38
what "headless evidence does not close a TUI issue" now points at. The
39
completion gate runs neither it nor `cargo fmt` for this crate (#124), so run
40
it by hand and say in the issue that you did.
41
35 42
## 1. Prerequisites
36 43
37 44
- **Docker with amd64 emulation that works.** Terminal-Bench images are

This page updates live while a promote is in flight · changelog