Skip to content

feat(ui): init banner + dashboard shield favicon#30

Merged
WZ merged 1 commit into
mainfrom
feat/ui-uplift
May 7, 2026
Merged

feat(ui): init banner + dashboard shield favicon#30
WZ merged 1 commit into
mainfrom
feat/ui-uplift

Conversation

@WZ
Copy link
Copy Markdown
Owner

@WZ WZ commented May 7, 2026

Summary

  • agent-gate init now opens with an accent-green ASCII wordmark + tagline + version line, printed to stderr so --print-config stays clean. Suppressed under --quiet and --print-config. Lipgloss handles no-color degradation for non-TTY writers.
  • Dashboard ships a 64×64 SVG shield favicon (dark rounded square, gradient green silhouette, white audit-pulse line). Wired via <link rel="icon" type="image/svg+xml"> in base.html and served from the embedded static FS. /favicon.ico 302s to the SVG so legacy browser probes don't 404.

Banner preview:

   ▄▀█ █▀▀ █▀▀ █▄ █ ▀█▀     █▀▀ ▄▀█ ▀█▀ █▀▀
   █▀█ █▄█ ██▄ █ ▀█  █      █▄█ █▀█  █  ██▄
   ◆ local traffic audit gate · v0.3.1

Test plan

  • go test ./internal/initwizard/... — banner unit tests (wordmark + tagline + version)
  • go test ./internal/dashboard/... — favicon serves at /static/favicon.svg, /favicon.ico 302→SVG, base page includes <link rel="icon">
  • go vet ./... clean
  • gofmt -l . clean
  • Visual: qlmanage -t -s 256 of the favicon → legible shield silhouette with audit pulse, on-brand at small sizes
  • Smoke: agent-gate init --dry-run --non-interactive shows banner on stderr, stdout untouched
  • Smoke: agent-gate init --print-config keeps stdout clean (banner suppressed)

…hboard

`agent-gate init` now opens with an accent-green wordmark + tagline +
version line, printed to stderr so `--print-config` stays clean.
Suppressed under `--quiet` and `--print-config`. Lipgloss handles
no-color degradation for non-TTY writers.

Dashboard ships a 64×64 SVG shield favicon (gradient green silhouette
with an inner audit-pulse line) wired via `<link rel="icon">` and
served from the embedded static FS. `/favicon.ico` now 302s to the
SVG so legacy browser probes don't 404.
@WZ WZ merged commit 118333d into main May 7, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant