os/v3/puppy/console-tui: the console never says LIVE or INSTALLED (brief's header spec, and #711's screen half) #1162

The console TUI's header spec is "edition name, LIVE/INSTALLED, IP, Lemonade URL, API key hint". Three of those are there; LIVE/INSTALLED is not — the shipped console has no notion of it at all (Facts carries no such field), so the appliance's tty1 looks identical whether it is running from the stick (everything in RAM, nothing installed) or from the machine's own disk.

init.sh already decides this at boot and prints it once in the MODE banner, and leaves the answer in /etc/1bit (installed / live). But that banner scrolls away and the TUI is the screen a person looks at all day — so:

• after the owner's install step (demo → install → publish) the console still reads like the stick it came from, on camera;
• the console is the surface an ssh user sees, and it never answers "is this thing installed?".

Closed #711 was the boot-side half of exactly this ("live usb is loaded up" while the facts came from the NVMe). This is the console's half, unbuilt.

Fix: Mode { Live, Installed, Unknown } read from init's markers (falling back to init's own rule, /data/.installed), rendered beside "1bit OS" in the header, with Unknown rendering nothing rather than guessing.