Tags: blank-query/lazyVPN-for-Omarchy

tutorial: sync in-app tutorial with current behavior (1.0.5)

- Local Network: describe it as an independent, always-in-effect layer
  instead of one that only applies 'while the killswitch is active' —
  the latter stopped being true after the 1.0.2/1.0.4 firewall refactor.
- Updates: document the in-app update path (sidebar 'Update X.Y.Z' item
  + manual check in Settings) alongside the daily auto-check and
  'lazyvpn update' CLI.
- Add Theming and Uninstall tips.

1.0.4: clear up the firewall model — single rebuild, outbound-only ki…

…llswitch

Every UFW toggle (killswitch, Local Network, IPv6) now goes through one
Reconcile(state) that tears down the entire lazyvpn ruleset and rebuilds it in
a fixed, validated order (LAN rules -> IPv6 deny -> killswitch allows -> reject
last -> deny-outgoing). This replaces the incremental rule-editing + its
reapply-killswitch and re-assert-Stealth workarounds; ordering and layer
independence are now correct by construction.

Killswitch is outbound-only: deny outgoing + physical-interface reject, never
touches the incoming policy (inbound is the Local Network layer's job; a NAT'd
host sees no unsolicited WAN inbound, and replies flow via conntrack).

Local Network owns the inbound posture, broadened so each mode is literally
true for any source: Allow = LAN in+out; Stealth = LAN out + block ALL
unsolicited inbound; Block = gateway-only local access + block ALL inbound.

Granular Enable*/EnableLAN* funcs (used by install/connect/CLI) delegate to the
same emit helpers, so they produce identical rules to Reconcile.

1.0.3: docs — refresh README for the independent Local Network model

Killswitch (force traffic through the tunnel) and Local Network (Allow/
Stealth/Block) are now documented as independent layers; Stealth noted as
the install-time default; tagged-rules list includes lazyvpn:la; install
step 4 mentions establishing the default Local Network mode.

1.0.2: independent Local Network layer + state-aware update action

Local Network (Allow/Stealth/Block) and the killswitch are now fully
independent layers. All three LAN modes lay down explicit, inspectable UFW
rules; Stealth is the default, established as a consented step at install.
The killswitch owns leak prevention only and emits no LAN rules — LAN egress
survives it by UFW first-match ordering (allow-out rules carry lower rule
numbers than the physical-interface reject; changing LAN mode while the
killswitch is on re-applies it so the reject stays last).

Settings update control is now 2-state (Check -> Install update X.X.X); the
nav-banner confirm dialog button reads "Install" to match.

1.0.1: fix manual update-check result display

The 'Check for Updates Now' result was set on the layout footer, which is
overwritten each render by the active view's CurrentDescription — so it stuck
on 'Checking…'. Route the result to the Settings view's statusText (what the
footer renders) instead; raise the nav banner via UpdateAvailableMsg when an
update is found.

LazyVPN 1.0.0 — WireGuard VPN manager for Omarchy

Single Go binary with a Bubbletea TUI for managing WireGuard VPN connections on
Linux (Omarchy primary target): direct netlink + wgctrl interface management;
UFW-based killswitch with Allow/Stealth/Block LAN modes and IPv6 leak protection;
dynamic server browser sourced from the server-data branch (mirrored weekly from
gluetun-servers); health-monitoring daemon with auto-recover and auto-failover;
leak/killswitch/MTU diagnostics; opt-in update checking (auto + manual); and
interactive install/uninstall flows.

broken by comma separated ipv4/ipv6 addresses in conf

split routes & routetable=off

Changed keybind from SUPER + L to SUPER + SHIFT + L to avoid conflict…

…s with the recent Omarchy update

Added uninstall and installation repair flow to installer

If you get stuck half-installer just run the installer again