Print the banner before config validation, not after

printBanner() only ran once config finished loading, so a missing
required env var (DISCORD_TOKEN etc.) crashed the process before the
banner ever printed. Split into printFlame() (just the art) and moved it
to the very first line of main() in both entrypoints, ahead of anything
that can throw. The full "Cindermail <subtitle>" line still prints later
once config actually succeeds.

Also added `npm run banner`, prints just the flame standalone with no
config or env vars required at all, for looking at it without needing a
working setup first. Verified: reproduced the original crash-before-
banner bug directly, confirmed the flame now prints ahead of it.

Psalm 25 17committed 2 months agoparent fc26cd0ed0bd99f03dc53a42af70c1f4f34ade8bfee67a0Browse files