fix DaisyUI semantic color misuses

[rin-st]

Fixes problems which we discussed in #1282

Main changes

• updated palette to be closer to the daisy docs. Note: See details regarding base-300 below, we can change it but I think it's good as it is
• switch default bg from base-200 to base-100 for better elevations
• make header and footer bg base-200
• created additional theme which is close to default. Created it because I didn't like how default looked after some changes, but it was just browser bugs. But kept default2 just to show you, maybe you'll like it
• some other color chages/bugfixes across the se-2.

---

Full changes list (generated)

Context

Follow-up to #1282. That PR landed the visual sweep and was opened with a description that explicitly flagged three DaisyUI semantic misuses the team agreed to fix before bumping @scaffold-ui. This PR cleans them up plus a few related palette collisions.

Problems

Palette collisions in globals.css

Light	Dark
primary = accent = info = #93bbfb	base-100 = info = #385183
	neutral inverted (#f9fbff with neutral-content #385183)

(secondary = base-300 in light and primary = base-300 in dark were left as-is — see Trade-offs below.)

Component misuses (Carlos's three from #1282)

1. btn-primary vs btn-secondary swapped — header CTAs were btn-secondary; footer dev tools were btn-primary.
2. bg-secondary used as a muted surface — debug banner, contract picker hover, theme toggle background.
3. text-neutral used as muted-text — DaisyUI neutral is for non-saturated UI, not muted text.

Page background
Page bg was base-200. DaisyUI docs: base-100 is the blank page surface, base-200/300 are elevations above it.

Surfaced during review

• Theme-switcher knob rendered grey (DaisyUI default --input-color: color-mix(base-content 50%, transparent)).
• RainbowKit dropdown items had inconsistent hover/focus vs the header nav.
• :active on menu items flipped bg → dark and text → white (DaisyUI --menu-active-bg/-fg default to neutral/neutral-content).

Solutions

Palette (globals.css)

• Light: accent #5b9bf0, info #3b9cf2 (break collision with primary).
• Dark: info #3b9cf2 (break collision with base-100); neutral #3d4250 + neutral-content #f9fbff (canonical dark non-saturated, inverted in original).
• Page bg → var(--color-base-100).
• All other tokens kept at the original Default values.

Component class swaps

• btn-primary → btn-secondary on footer price chip / Block Explorer link, Faucet modal trigger, BackButton, PaginationButton, tx-page back button. btn-primary retained where it's a genuine CTA (Connect Wallet, Faucet modal "Send", Search submit, 404 "Home").
• bg-secondary / hover:bg-secondary → base-300 / hover:bg-base-300 on debug banner, DebugContracts picker hover, SwitchTheme.
• Table headers bg-primary → bg-base-200.
• Standalone text-primary-content removed from TransactionComp <h2> and PaginationButton page-number span.
• SearchBar border-primary → border-base-300; focus:ring-accent → focus:ring-primary.
• Block-explorer external link text-accent → link link-primary.

Header / footer chrome

• Header bg-base-100 → bg-base-200 (DaisyUI-canonical elevated chrome over white page).
• Footer outer wrapper: added bg-base-200 to match.
• Header active link: bg-base-300 → bg-secondary text-secondary-content; hover/focus only on inactive items.

Theme switcher (SwitchTheme.tsx)
toggle bg-base-300 toggle-primary [--input-color:var(--color-primary)] dark:[--input-color:var(--color-base-content)] — off-state knob is SE-2 primary blue in light, falls back to base-content in dark (where Default primary = base-300 makes a primary-colored knob invisible).

RainbowKit dropdowns

• Items: hover:bg-base-300 focus:bg-secondary (mirrors the header nav non-active / active pattern).
• Destructive items (Reveal PK, Disconnect): text-error → !text-error so red survives DaisyUI's :focus-visible{color:base-content} and :active{color:menu-active-fg} overrides.
• Dropdown <ul> got [--menu-active-bg:var(--color-secondary)] [--menu-active-fg:var(--color-base-content)] so pressed state matches focus instead of flipping to dark neutral + white text.

Alternative palette

Added Default2 to palettes.ts (available in the /test picker) — same shape as Default but with secondary retuned to a desaturated cousin of primary (#bdd8f7 light / #4a6896 dark) so secondary, base-300, and dark primary are all visually distinct. Provided as a side-by-side preview, not the default.

Trade-offs

Kept Default's secondary = base-300 and dark primary = base-300 for the preferred aesthetic. Known consequences:

• Light header active link (bg-secondary) and hover (bg-base-300) render the same color. Active state is signalled by presence rather than color-by-state.
• Dark btn-primary blends into bg-base-300 surfaces (home band, inline code chips). Still pops on base-100/base-200.

Both addressable later by retuning secondary / dark primary (see Default2).

🤖 Generated with Claude Code