docs: remove NLU from v1.0 scope

- Remove Claude API integration and intent parsing (04-02-PLAN)
- REQ-08 (conversational queries) moved to out of scope
- Phase 4 renamed from "Logs & Intelligence" to "Logs" (complete)
- v1.0 now focuses on keyword-based container control

Simple substring matching works well for container management.
NLU adds complexity without proportional value for v1.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.planning/PROJECT.md

@@ -2,7 +2,7 @@
 
 ## What This Is
 
-A conversational Telegram bot that lets you manage Docker containers on your Unraid server using natural language. Think JARVIS for your homelab — ask questions, get status updates, and control containers all from your phone without needing to open a laptop.
+A Telegram bot that lets you manage Docker containers on your Unraid server. Control containers from your phone without needing to open a laptop — check status, view logs, start/stop/restart/update containers via simple keyword commands.
 
 ## Core Value
 
@@ -23,15 +23,15 @@ When you get a container update notification or notice a service is down, you ca
 - [ ] Restart a container by name
 - [ ] Update a container (pull new image, recreate)
 - [ ] View container logs with configurable line count (default 50)
-- [ ] Ask conversational questions ("what's using the most memory?")
 - [ ] Bot only responds to your Telegram user ID
 
 ### Out of Scope
 
 - Taking over Unraid notifications — keep existing notification system, this bot is for control
 - Deploying new containers — manage existing only, not create new ones
-- Local LLM — N100 can't handle it well, using Claude API instead
+- Natural language understanding — simple keyword matching sufficient for v1, Claude API adds complexity
 - Proactive monitoring/notifications — bot is reactive (you ask, it answers) for v1
+- Resource queries — "what's using the most memory?" deferred to future version
 
 ## Context
 
@@ -54,7 +54,7 @@ When you get a container update notification or notice a service is down, you ca
 
 - **Platform**: Must run on Unraid (Docker-based deployment)
 - **Orchestration**: Use n8n for workflow orchestration (already running)
-- **LLM**: Claude API for natural language understanding
+- **Matching**: Keyword/substring matching for container names
 - **Auth**: Single user only — verify Telegram user ID
 - **Logs**: Support configurable line count, default to 50 lines
 
@@ -62,10 +62,10 @@ When you get a container update notification or notice a service is down, you ca
 
 | Decision | Rationale | Outcome |
 |----------|-----------|---------|
-| Use Claude API over local LLM | N100 CPU can't run LLMs fast enough for good UX | — Pending |
+| Use keyword matching over NLU | Simple substring matching works well, Claude API adds complexity for v1 | ✓ Good |
 | Use n8n for orchestration | Already running, handles Telegram webhooks, reduces new infrastructure | — Pending |
 | Manage existing containers only | Keeps scope focused, deployment is complex and rarely needed from mobile | — Pending |
 | Single user auth via Telegram ID | Simple security model, only one person needs access | — Pending |
 
 ---
-*Last updated: 2026-01-28 after initialization*
+*Last updated: 2026-01-31 after removing NLU from v1.0 scope*