docs: add Customization and Tailscale wiki pages
- New: Customization.md — logo convention, landing branding, QLC+ v4/v5 compat
- New: Tailscale.md — remote access setup guide, MCP over tailnet
- Updated: _Sidebar.md — added new pages under Advanced
- Updated: Configuration.md — branding and remote access cross-links
- Updated: Troubleshooting.md — blank web UI and USB disconnect sections
docs: post-v2.13.x sweep — mobile/PWA, visual identity, troubleshooting
- Home: mention MCP, mobile/PWA, tab persistence in key capabilities
- Quick-Start: add deploy-vs-update note, PWA install step, MCP caveat
- Troubleshooting: new Common Pitfalls section covering update vs deploy,
stale UI after deploy, lighting-mcp not installed (v2.13.1), Flask
template caching
- Command-Reference: clarify update is apt-only, add deploy.sh section
- Control-Server: bump to v2.13.2, add Visual Identity and Tab Persistence
sections, link to Mobile-and-PWA
- New Mobile-and-PWA page: iOS/Android install, offline behavior, mobile
UX details (44px targets, 16px inputs, safe-area, tabs scroll, modals)
- Sidebar: link Mobile-and-PWA under Usage
docs: full wiki sweep for v2.x agent-driven workflow
Audit pass over every wiki page after the Tier-1 → v2.7.0 buildout —
fixing real gaps where pages were silent on capabilities that now exist.
Quick-Start.md
• Add Step 5 (control-install) and Step 6 (mcp-install) — the original
quick-start ended at "doctor" and never told new users they could
install the AI web UI or the MCP endpoint. Now they get a complete
path from SD card to LLM-driven rig.
Configuration.md
• Add a dedicated "MCP Server Variables" section covering MCP_HOST,
MCP_PORT, MCP_PATH, CONTROL_URL, MCP_BEARER_TOKEN, MCP_HTTP_TIMEOUT
• Fix the firewall description: previously claimed UFW only allows
SSH + QLC+ web UI; in fact control-install and mcp-install open
additional ports as part of their installation.
Troubleshooting.md
• Add "From an MCP Agent" subsection under Quick Diagnostics covering
test_dmx / get_logs / get_system_info. Tells operators (and the
agent itself) the right escape-hatch trio to triage problems
without SSHing in.
AI-Scene-Generation.md
• Add "From an MCP Agent" section explaining that the same
generate_scene pipeline is reachable as an MCP tool, and that
agents can use describe_scene to inspect saved scenes before
activating.
No content removed — only additive gap-filling.
Add initial wiki pages migrated from hardcoded docs