c8966477b9
Complete implementation of the production line incident response system (生產線異常即時反應系統) including: Backend (FastAPI): - User authentication with AD integration and session management - Chat room management (create, list, update, members, roles) - Real-time messaging via WebSocket (typing indicators, reactions) - File storage with MinIO (upload, download, image preview) Frontend (React + Vite): - Authentication flow with token management - Room list with filtering, search, and pagination - Real-time chat interface with WebSocket - File upload with drag-and-drop and image preview - Member management and room settings - Breadcrumb navigation - 53 unit tests (Vitest) Specifications: - authentication: AD auth, sessions, JWT tokens - chat-room: rooms, members, templates - realtime-messaging: WebSocket, messages, reactions - file-storage: MinIO integration, file management - frontend-core: React SPA structure 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
---
|
|
name: OpenSpec: Apply
|
|
description: Implement an approved OpenSpec change and keep tasks in sync.
|
|
category: OpenSpec
|
|
tags: [openspec, apply]
|
|
---
|
|
<!-- OPENSPEC:START -->
|
|
**Guardrails**
|
|
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
|
|
- Keep changes tightly scoped to the requested outcome.
|
|
- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
|
|
|
|
**Steps**
|
|
Track these steps as TODOs and complete them one by one.
|
|
1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
|
|
2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
|
|
3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
|
|
4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
|
|
5. Reference `openspec list` or `openspec show <item>` when additional context is required.
|
|
|
|
**Reference**
|
|
- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
|
|
<!-- OPENSPEC:END -->
|