Consolidate the banner theme prototypes in LIFEOS/TOOLS

[anikinsasha]

Summary

LIFEOS/TOOLS/ ships seven banner implementations, but the launcher (lifeos.ts) only ever invokes Banner.ts:

• Banner.ts — the live one
• BannerMatrix.ts, BannerNeofetch.ts, BannerPrototypes.ts, BannerRetro.ts, BannerTokyo.ts, NeofetchBanner.ts — alternative theme prototypes, ~124 KB combined, referenced by nothing

Every install carries all seven; six are dead weight unless a user wires them in by hand.

Proposal (either works)

1. Consolidate: fold the theme variants into Banner.ts behind a --theme flag and delete the standalones; or
2. Relocate: move the six prototypes to a clearly-experimental home (e.g. a prototypes/ subfolder or a docs example), keeping the root to tools the launcher actually uses.

If neither is wanted, a header note per variant marking it "prototype, not wired to the launcher" is the minimum (a docs PR in flight adds exactly that, so this issue is purely about whether the files should stay).

[danielmiessler]

Deleted — you were right on all three counts: lifeos.ts hardcodes Banner.ts, the other six had zero callers anywhere in the tree, and all seven were shipping to every user. Removed BannerMatrix, BannerNeofetch, BannerPrototypes, BannerRetro, BannerTokyo, and NeofetchBanner — about 130KB of dead weight out of the payload. Verified zero references tree-wide (case-insensitive, including docs and the deploy manifest) before each deletion.

No --theme flag; if themed banners come back it should be a deliberate feature, not six orphaned prototypes. Thanks for the sweep.