BUG-4 (High, failed acceptance criterion) — per-tile unread badges: new use-team-unread-counts.ts runs one app-level Matrix client (separate from useTeamChat's detail-view client) that syncs every room GET /api/teams now resolves (matrixRoomId added via leftJoin on chat_rooms) and reports unread counts per team. TeamsPage tiles show the badge without the chat tab being open. Side fix: createMatrixClient() now dynamic-imports matrix-js-sdk instead of a static import, so the new always-mounted hook doesn't drag the SDK (and its 7.8MB crypto WASM) back into TeamsPage's main bundle — verified via build output (TeamDetail chunk 853KB -> 27KB, SDK now in its own on-demand chunk). BUG-3 (High) — kick-while-open: use-team-chat.ts now listens for RoomEvent.MyMembership; leaving/removal flips status to a new "removed" state instead of leaving history and the composer usable. BUG-2 (High, partially mitigated) — minted tokens are unscoped Matrix credentials by nature (Matrix has no token scoping). Disabled user_directory search on Synapse (config + live matrix.perlbach24.de instance), verified empty results instead of cross-club user listing. Direct addressing by known Matrix ID is still possible — full tenant isolation needs an explicit decision (one Synapse per club vs. an isolation module on a shared homeserver), documented as an open item in the spec rather than silently declared fixed. BUG-1 (Critical, not fixed) — backend/.env.example is outside my permission sandbox (can't read or write .env* files). Documented the required block in the spec for manual addition; talkhub's real .env already has the values. Verified end-to-end on talkhub/matrix test LXCs. Not addressed in this pass (lower priority per QA): BUG-5/6/7/8/9/10. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0143yYvjesjHndBACoweyK67
Feature Specifications
Dieser Ordner enthält detaillierte Feature Specs vom Requirements Engineer.
Naming Convention
PROJ-X-feature-name.md
Beispiele:
PROJ-1-user-authentication.mdPROJ-2-kanban-board.mdPROJ-3-file-attachments.md
Was gehört in eine Feature Spec?
1. User Stories
Beschreibe, was der User tun möchte:
Als [User-Typ] möchte ich [Aktion] um [Ziel zu erreichen]
2. Acceptance Criteria
Konkrete, testbare Kriterien:
- [ ] User kann Email + Passwort eingeben
- [ ] Passwort muss mindestens 8 Zeichen lang sein
- [ ] Nach Registration wird User automatisch eingeloggt
3. Edge Cases
Was passiert bei unerwarteten Situationen:
- Was passiert bei doppelter Email?
- Was passiert bei Netzwerkfehler?
- Was passiert bei gleichzeitigen Edits?
4. Tech Design (vom Solution Architect)
## Database Schema
CREATE TABLE tasks (...);
## Component Architecture
ProjectDashboard
├── ProjectList
│ └── ProjectCard
5. QA Test Results (vom QA Engineer)
Am Ende des Feature-Dokuments fügt QA die Test-Ergebnisse hinzu:
---
## QA Test Results
**Tested:** 2026-01-12
**App URL:** http://localhost:3000
### Acceptance Criteria Status
- [x] AC-1: User kann Email + Passwort eingeben
- [x] AC-2: Passwort mindestens 8 Zeichen
- [ ] ❌ BUG: Doppelte Email wird nicht abgelehnt
### Bugs Found
**BUG-1: Doppelte Email-Registrierung**
- **Severity:** High
- **Steps to Reproduce:** 1. Register with email, 2. Try again with same email
- **Expected:** Error message
- **Actual:** Silent failure
6. Deployment Status (vom DevOps Engineer)
---
## Deployment
**Status:** ✅ Deployed
**Deployed:** 2026-01-13
**Production URL:** https://your-domain.example
**Git Tag:** v1.0.0-PROJ-1
Workflow
- Requirements Engineer erstellt Feature Spec
- User reviewed Spec und gibt Feedback
- Solution Architect fügt Tech-Design hinzu
- User approved finales Design
- Frontend/Backend Devs implementieren (dokumentiert via Git Commits)
- QA Engineer testet und fügt Test-Ergebnisse zum Feature-Dokument hinzu
- DevOps deployed und fügt Deployment-Status zum Feature-Dokument hinzu
Status-Tracking
Feature-Status wird direkt im Feature-Dokument getrackt:
# PROJ-1: Feature Name
**Status:** 🔵 Planned | 🟡 In Progress | ✅ Deployed
**Created:** 2026-01-12
**Last Updated:** 2026-01-12
Status-Bedeutung:
- 🔵 Planned – Requirements sind geschrieben, ready for development
- 🟡 In Progress – Wird gerade gebaut
- ✅ Deployed – Live in Production
Git als Single Source of Truth:
- Alle Implementierungs-Details sind in Git Commits
git log --grep="PROJ-1"zeigt alle Änderungen für dieses Feature- Keine separate FEATURE_CHANGELOG.md nötig!