Files
talktime/features
patrickandClaude Sonnet 5 f81d2d7906 feat(PROJ-14): backend for Synapse room overview (SYSTEM_ADMIN)
GET /api/system-admin/rooms and DELETE /api/system-admin/rooms/:roomId,
both gated on requireSystemAdmin from PROJ-13. No new DB table — reads
Synapse's room list directly, cross-references the existing chat_rooms
table for org/team attribution via one inArray join.

deleteRoom() uses the v2 async purge endpoint (not v1, which blocks
until the purge finishes and would time out on a large room).
normalizeCreationTs() handles Synapse versions that return seconds
instead of documented milliseconds — moot on this deployment's Synapse
version, which omits creation_ts from the rooms list entirely; verified
live, code already treats a missing value as null rather than guessing.

Known gap: audit_logs.organization_id is NOT NULL, so deleting an
unassigned room can't get a proper audit entry (falls back to a server
log warning). Flagged rather than silently worked around.

Verified end-to-end on talkhub/matrix: 403 without the SYSTEM_ADMIN
flag, 200 with it, and used the new delete endpoint to clean up a
genuinely orphaned test room left over from earlier QA.

Frontend (/system-admin route, rooms table, delete dialog) still
outstanding — the nav button added in PROJ-13 stays a dead link until
that lands.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0143yYvjesjHndBACoweyK67
2026-09-12 21:06:46 +02:00
..

Feature Specifications

Dieser Ordner enthält detaillierte Feature Specs vom Requirements Engineer.

Naming Convention

PROJ-X-feature-name.md

Beispiele:

  • PROJ-1-user-authentication.md
  • PROJ-2-kanban-board.md
  • PROJ-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

  1. Requirements Engineer erstellt Feature Spec
  2. User reviewed Spec und gibt Feedback
  3. Solution Architect fügt Tech-Design hinzu
  4. User approved finales Design
  5. Frontend/Backend Devs implementieren (dokumentiert via Git Commits)
  6. QA Engineer testet und fügt Test-Ergebnisse zum Feature-Dokument hinzu
  7. 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!