veronica
dc6db5f14e
ci/woodpecker/pr/ci Pipeline failed
send-message.sh confirmed delivery by grepping the captured pane for a prompt glyph (`❯`, a leading `>`, or `│ >`). Those are Claude Code shapes. pi draws its input box as two horizontal `─` rules with the input between them and no glyph anywhere, so on a pi pane the grep matched nothing, the `delivered` and `draft` branches were unreachable, and every send exited 2 with "may be UNDELIVERED" after burning all its retries — on messages that had in fact been delivered. Measured on five live seats: pi seats vision, tess and medic returned 0 glyph matches on non-empty captures (3653 / 1086 / 1890 bytes); Claude seats fred and tuesday returned 3 and 1. This is a different arm from #1257. On the measured host `tmux capture-pane -t <session> -p` and `-t <session>:0.0 -p` both return the same 3653 bytes, so #1257's empty-capture mechanism does not reproduce here; fixing only that would leave every pi send at rc=2 and would verify green against a Claude pane. The probe becomes locate_input_box(), which returns a status code instead of a string. Found-but-empty is a real answer (an empty input box is what a submitted message leaves behind) and is now distinguishable from not-found, which the old `[ -z "$promptline" ]` test conflated. Box detection anchors on the LAST pair of `─` rules: agent output can contain its own rules, but nothing is drawn below the input box except the status line. Adding a runtime means adding its shape in that one function. A missing shape does not degrade gracefully — it turns every send to that runtime into a false "may be UNDELIVERED", which is exactly what this fixes. Tests: two fixtures added to test-send-message-verdict.sh driving a glyphless box-drawn REPL, one that submits (expect exit 0 delivered) and one that holds the text in the box (expect exit 2 draft). Patched suite PASS=5 FAIL=0. Control against the pristine origin/next send-message.sh: PASS=3 FAIL=2, fixture 4 failing as `rc=2 ... REPL input prompt not locatable after 3 attempts — message may be UNDELIVERED`, which is the defect reproduced in a test. Sibling suites unchanged and green: test-send-message-socket.sh rc=0, agent-send.test.sh PASS=19 FAIL=0. Note the suite is in test-enumeration-exclusions.txt (the CI image ships no tmux), so these fixtures are verified locally only. That exclusion and its #1017 burndown reason are unchanged by this commit. Not addressed here: auto-submit-drafts.sh lines 20 and 26 carry the same Claude-only `❯` assumption. Separate surface, separate change. Closes #1362