. "$BST_LIB"
# readline is a library, not a tool. On the fully-static wasm32-hwjs image no
# shared object survives to the rootfs (there is no runtime loader and nothing can
# dlopen; a consumer links readline statically at build time), so the readline
# package's on-target payload is its /etc/inputrc config file plus dpkg
# registration -- the library code proper is delivered into a consumer at link
# time, and readline's first consumer (bash) is recipes-extended, outside this
# Epic. Coverage is therefore the installed config + package registration; the
# interactive Up-arrow check is runtime-blocked and recorded as a skip below.

# --- the readline package is installed and its /etc/inputrc config landed ---
check     readline/inputrc       test -f /etc/inputrc
check_out readline/inputrc-body  "libreadline"  cat /etc/inputrc
# the readline package registered with dpkg (its file list carries /etc/inputrc)
check_out readline/pkg-installed "/etc/inputrc" cat /var/lib/dpkg/info/readline.list

# --- interactive Up-arrow line recall: runtime-blocked, recorded not-covered ---
# No interactive REPL on the image links readline: bash is recipes-extended and is
# not shipped, and GNU bc's --with-readline is rejected at configure on
# wasm32-hwjs, so bc ships without line editing. There is therefore nothing for a
# spawn/send-Up script to drive. (expect, the PTY driver such a script would need,
# does work here — its own linux-in-the-browser#92 blocker was fixed upstream
# 2026-07-14 — so the gap is the missing consumer, not the harness.)
bst_skip readline/interactive-history "no readline REPL on this image to drive: bash is not shipped and bc's --with-readline is rejected on wasm32-hwjs"