9b220523ff
## Critical Issues (CRIT-001~003) - All Fixed
- JWT secret key validation with pydantic field_validator
- Login audit logging for success/failure attempts
- Frontend API path prefix removal
## High Priority Issues (HIGH-001~008) - All Fixed
- Project soft delete using is_active flag
- Redis session token bytes handling
- Rate limiting with slowapi (5 req/min for login)
- Attachment API permission checks
- Kanban view with drag-and-drop
- Workload heatmap UI (WorkloadPage, WorkloadHeatmap)
- TaskDetailModal integrating Comments/Attachments
- UserSelect component for task assignment
## Medium Priority Issues (MED-001~012) - All Fixed
- MED-001~005: DB commits, N+1 queries, datetime, error format, blocker flag
- MED-006: Project health dashboard (HealthService, ProjectHealthPage)
- MED-007: Capacity update API (PUT /api/users/{id}/capacity)
- MED-008: Schedule triggers (cron parsing, deadline reminders)
- MED-009: Watermark feature (image/PDF watermarking)
- MED-010~012: useEffect deps, DOM operations, PDF export
## New Files
- backend/app/api/health/ - Project health API
- backend/app/services/health_service.py
- backend/app/services/trigger_scheduler.py
- backend/app/services/watermark_service.py
- backend/app/core/rate_limiter.py
- frontend/src/pages/ProjectHealthPage.tsx
- frontend/src/components/ProjectHealthCard.tsx
- frontend/src/components/KanbanBoard.tsx
- frontend/src/components/WorkloadHeatmap.tsx
## Tests
- 113 new tests passing (health: 32, users: 14, triggers: 35, watermark: 32)
## OpenSpec Archives
- add-project-health-dashboard
- add-capacity-update-api
- add-schedule-triggers
- add-watermark-feature
- add-rate-limiting
- enhance-frontend-ux
- add-resource-management-ui
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
21 lines
768 B
Markdown
21 lines
768 B
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: API Rate Limiting
|
|
The system SHALL implement rate limiting to protect against brute force attacks and DoS attempts.
|
|
|
|
#### Scenario: Login rate limit enforcement
|
|
- **GIVEN** a client IP has made 5 login attempts within 1 minute
|
|
- **WHEN** the client attempts another login
|
|
- **THEN** the system returns HTTP 429 Too Many Requests
|
|
- **AND** the response includes a Retry-After header
|
|
|
|
#### Scenario: Rate limit window reset
|
|
- **GIVEN** a client has exceeded the rate limit
|
|
- **WHEN** the rate limit window expires (1 minute)
|
|
- **THEN** the client can make new requests
|
|
|
|
#### Scenario: Rate limit per IP
|
|
- **GIVEN** rate limiting is IP-based
|
|
- **WHEN** different IPs make requests
|
|
- **THEN** each IP has its own rate limit counter
|