Skip to content

Exclusions

coaxk edited this page Mar 12, 2026 · 1 revision

Exclusions

Items considered and intentionally dropped, with reasoning. These are not "backlog" — they were evaluated and rejected.

Item Source Why Excluded
CSRF protection Gemini Local-network tool, no session cookies. Near-zero real-world risk.
Multi-tab state safety Gemini Single-user local tool. Revisit if multi-user support added.
Telemetry ChatGPT Privacy-sensitive audience (homelab users). v3.0+ discussion after trust is established.
Type hints retrofit DeepSeek High effort, low value vs existing test suite. Add to new code only.
Hardlink onboarding tooltip DeepSeek + ChatGPT Analysis engine already explains failures with fixes. TRaSH Guides linked in output.
Dark/light mode toggle Gemini + Grok Dark theme matches homelab aesthetic. Nobody has asked. Revisit on demand.
Expand Image DB beyond 219 Gemini 219 images + custom-images.json covers it. Add on demand.
Atomic backup swap Grok shutil.copy2 then write is not atomic. Rate limit + single-user makes race condition theoretical.
uvicorn --workers >1 Grok Ships single-worker. Documented assumption. Session locking in v1.6 as foundation for multi-worker.

Scope Boundaries

Why Not Analyze "Other" Services?

Request apps (Overseerr, Huntarr), media companions (Tautulli, Subgen), and infrastructure (Nginx, Traefik) are shown on the dashboard but NOT analyzed. Reclassifying them into core roles would:

  • Pull them into the 4-pass analysis → generate noise conflicts
  • An Nginx container doesn't need PUID/PGID analysis
  • Overseerr doesn't need path conflict detection

The 27-service core list covers arr apps + download clients + media servers — the services that actually exchange files via hardlinks/imports.

Why Not Auto-Detect via Docker API?

Auto-detection via docker ps / docker inspect is planned for v2.0 (task SA2). It's deferred because:

  • It adds Docker SDK as a hard dependency (currently optional)
  • Compose files are the canonical source of truth for path configuration
  • Users who need MapArr most (broken setups) often have Docker issues too — adding Docker API dependency compounds failure modes

Rumplestiltskin (Banked Concept)

A framework for extracting MapArr's analysis methodology into a pluggable engine. Domain plugins (compose-hygiene, mount-topology, etc.) + Ethos Engine (confidence gating, severity grading, explanation generation). Building blocks exist across MapArr + ComposeArr, but extraction is premature. Status: banked. Re-evaluate when patterns mature across more tools.

Clone this wiki locally