Add shared StarIntel Discord footer #6

Closed
lost-rob0t wants to merge 9 commits from agent/add-starintel-discord-footer into main
lost-rob0t commented 2026-07-30 05:09:44 +00:00 (Migrated from github.com)

Changes

  • add the shared, theme-aware StarIntel community footer
  • link the Discord invite at https://discord.gg/R3VY8wr86Y
  • keep the CTA responsive, keyboard accessible, and safe around mobile navigation
  • load it through Vite's base-path-aware public asset path

Validation

  • shared JavaScript passes node --check
  • the footer is idempotent and remains the final body element when runtime UI is appended
## Changes - add the shared, theme-aware StarIntel community footer - link the Discord invite at `https://discord.gg/R3VY8wr86Y` - keep the CTA responsive, keyboard accessible, and safe around mobile navigation - load it through Vite's base-path-aware public asset path ## Validation - shared JavaScript passes `node --check` - the footer is idempotent and remains the final body element when runtime UI is appended
lost-rob0t commented 2026-08-19 11:23:17 +00:00 (Migrated from github.com)

Closing as superseded by the current shared-shell architecture. This PR injects UI with a public-script MutationObserver DOM enhancer, while current main deliberately moved Auto-Dig chrome into src/ui-core/QuasarShell.jsx and removed legacy DOM shell enhancement. If the Discord/community link is still desired, it should be implemented as a first-class shared-shell component instead of reviving this observer layer.

Closing as superseded by the current shared-shell architecture. This PR injects UI with a public-script `MutationObserver` DOM enhancer, while current `main` deliberately moved Auto-Dig chrome into `src/ui-core/QuasarShell.jsx` and removed legacy DOM shell enhancement. If the Discord/community link is still desired, it should be implemented as a first-class shared-shell component instead of reviving this observer layer.

Pull request closed

Sign in to join this conversation.
No description provided.