umputun / fya / 29659162286

86%

push

github

fix: gate prompt readiness on marker plus a settled quiet window (#21)

Fixes the readiness regression in #20. On Claude Code 2.1.214 every fya turn hung to the turn timeout and printed nothing, even though Claude answered within seconds.

**Cause.** Since #15 readiness fired on first sight of the input-ready marker `ESC[?2004h` and treated it as proof the editor was reading. On 2.1.214 that marker is emitted at terminal init, ~1% into startup (~450-500ms after spawn), while the editor keeps painting for another ~800ms. After the 250ms `--type-settle` fya typed into an editor that was not reading yet and the opening characters dropped, so `Select` never matched the mangled prompt against the transcript and the turn polled to `--turn-timeout` with no output.

**Fix.** Readiness now requires the marker AND a settled output window (the existing `QuietPeriod`, 750ms), so fya waits until the editor stops painting. The marker is latched once seen, so it stays valid even if it scrolls out of the capped PTY buffer during a long startup. This is strictly stronger than before, it can only fire later than the old gate, so the pre-#15 quiet-only early-fire cannot return. The stale glyph fallback list is refreshed for the 2.1.214 prompt (`❯`), used only when no marker is configured.

The worst intra-startup output lull measured 439ms across 5 runs, so 750ms is the right window. Verified against real 2.1.214: a de-nested `fya ... "reply with exactly: <token>"` returns the token in ~14s where it used to hang. Race tests and linter clean, `app/ready` coverage 96.3%.

Fixes #20

27 of 27 new or added lines in 1 file covered. (100.0%)

1733 of 2004 relevant lines covered (86.48%)

59.93 hits per line