Add ban management features and update documentation

- Implement ban model, service, and router endpoints in backend
- Add ban table component and dashboard integration in frontend
- Update ban-related types and API endpoints
- Add comprehensive tests for ban service and dashboard router
- Update documentation (Features, Tasks, Architecture, Web-Design)
- Clean up old fail2ban configuration files
- Update Makefile with new commands

Docs/Tasks.md

@@ -3,12 +3,9 @@
 This document breaks the entire BanGUI project into development stages, ordered so that each stage builds on the previous one. Every task is described in prose with enough detail for a developer to begin work. References point to the relevant documentation.
 
 ---
-1. config not found issue — **DONE**
 
-Have not found any log file for bangui-access jail
-1d6112acb250 2026-03-06 18:51:31,995 fail2ban                [352]: ERROR   Failed during configuration: Have not found any log file for bangui-access jail
-1d6112acb250 2026-03-06 18:51:33,074 fail2ban                [355]: ERROR   Failed during configuration: Have not found any log file for bangui-access jail
+## Remove the Access List Feature
 
-**Fix:** Two root causes identified and resolved:
-1. `Docker/compose.debug.yml` had an incorrect volume mount path `./Docker/logs` (which resolved to the empty `Docker/Docker/logs/` relative to the compose file). Corrected to `./logs` so it correctly mounts `Docker/logs/` at `/remotelogs/bangui` inside the container.
-2. `Docker/logs/access.log` did not exist. Created the empty file so fail2ban can open and watch it for the `bangui-access` jail.
+The "access list" feature displays individual log-line matches (the raw lines that triggered fail2ban bans) in a dedicated tab on the Dashboard and as a companion table on the World Map page. It is being removed entirely. The tasks below must be executed in order. After completion, no code, config, test, type, or documentation reference to access lists should remain.
+
+---