Document subpath hosting limitation, capture as TODO

The server requires its own domain — subpath hosting (e.g. /taskflow)
would need a TASKFLOW_BASE_PATH config threaded through route
registration, OpenAPI generation, and dashboard links.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: bricef

README.md

@@ -222,6 +222,10 @@ just clean          # remove build artifacts
 
 Set `TASKFLOW_DEV_MODE=true` to disable all rate limiting (useful for testing and development). See [TESTING.md](TESTING.md) for the full manual QA checklist.
 
+### Deployment note
+
+The server must be hosted at the root of a domain (e.g. `https://taskflow.example.com`). Hosting at a subpath (e.g. `/taskflow`) is not currently supported — the dashboard, OpenAPI spec, and SSE endpoints generate absolute paths without a configurable prefix.
+
 ### Testing with the simulator
 
 The activity simulator generates realistic board activity for testing SSE live updates:

TODO.md

@@ -28,6 +28,10 @@ See also [TUI improvements plan](docs/plans/active/2026-03-31-tui-improvements.m
 - [ ] Due date visual indicator in TUI kanban (e.g. red highlight for past-due tasks)
 - [ ] Backup/restore: `taskflow admin backup` command (SQLite makes this easy but no tooling exists)
 
+## Deployment
+
+- [ ] Base path prefix support (`TASKFLOW_BASE_PATH`) — currently the server must be hosted at the root of a domain; hosting at a subpath (e.g. `/taskflow`) requires code changes to route registration, OpenAPI generation, and dashboard links
+
 ## Admin
 
 - [ ] Webhook management from TUI (admin users currently need CLI or API)