fix(ui): forward init refresh + tick messages while splash is showing

[torosent]

Summary

Fixes a real bug where the active screen's first RefreshedMsg and first TickMsg were silently dropped while the splash was on screen, leaving users staring at 0 items · 0 running until they happened to switch screens or press r.

Root cause

    if _, isTick := msg.(state.TickMsg); isTick { ... }
    if scr, ok := m.screens[m.active]; ok { ... route to active screen ... }
}

The active screen's Init returns a tea.Batch that includes state.MakeRefreshedCmd (immediate fetch) and state.TickCmd (first poll). These run in goroutines and emit messages while the splash is still showing — which were dropped.

That alone broke the immediate fetch, but the kicker is clock.Real().Tick() returns time.After(d) — a one-shot channel. The screen's polling loop re-arms a new TickCmd only when it receives a TickMsg. If the first tick is dropped, the polling loop dies entirely.

End result: containers shown empty until the user switches screens (which re-runs that screen's Init) or hits r. You can see this clearly in the previous demo GIF — the screen shows 0 items for the first ~30 seconds even though demo data is fully populated.

Fix

Forward TickMsg, modal traffic, and other internal messages to the active screen even while the splash is up. The splash still owns KeyMsg and WindowSizeMsg via the typed cases above. (SplashDoneMsg continues to flip showSplash = false.)

Tests

Added TestAppForwardsInitMessagesDuringSplash in internal/ui/app_test.go. Verified locally:

• Without the fix: test fails — view shows 0 items · 0 running, 0 exited.
• With the fix: test passes — synthesized container row renders after splash dismissal.

Full suite (go test ./...) green.

Demo refresh

While I was here, regenerated docs/assets/c9s.gif against the fixed build and rewrote tools/demos/c9s.tape to a single dark-theme walk-through covering every major scenario:

• Containers screen tour (help, filter, sort, inspect, pin, prune)
• Number-shortcut nav through every resource (1-9, 0)
• System sub-screens (:df, :dns, :property, :kernel)
• Action modals (build, registry login)
• v0.1.x features (:acr-login, :install-docker-shim)

The tape also sets up a fresh XDG_CONFIG_HOME so the recording always picks up the v0.1.4 default skin (k9s-gruvbox-dark) regardless of the recorder's local config.