Restore tests broken by post-command refactor

[Copilot]

Tests were silently disabled after PR #12 moved h5inspect_post execution inside app.run(), causing CI to pass on all subsequent master commits with zero tests running.

Why tests broke

ratatui::init() moved inside run() — panics in non-TTY CI environments (enable_raw_mode() fails without a real terminal), making TestBackend-based tests impossible.

Sync event polling replaced async handler — events.rs was changed from a tokio-spawned EventStream task to synchronous crossterm::event::poll(). A blocking call inside async fn run() starves the tokio executor, so tokio::select! timeouts never fire and tests hang.

Changes

• app.rs: run() now accepts Terminal<B: Backend> + a reinit_terminal: impl Fn() -> Terminal<B> callback, preserving the in-loop post-command behavior (no app state loss) without hardcoding ratatui::init()
• events.rs: Restored the async EventHandler using EventStream in a spawned tokio task with receiver.recv().await in the event loop — compatible with tokio::select! cancellation
• main.rs: Passes ratatui::init() terminal and reinit closure to run(); tests uncommented and updated to pass TestBackend terminal + no-op reinit

// tests now pass a TestBackend — no real TTY needed
app.run(
    terminal,
    || Terminal::new(TestBackend::new(200, 120)).unwrap(),
)

Original prompt

explain why this didn't trigger on the recent commits to master and fix it

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.