feat: Excel template export with meeting number auto-generation

- Add meeting_number field (M-YYYYMMDD-XX format) with auto-generation
- Refactor Excel export to use cell coordinates instead of placeholders
- Export files saved to backend/record/ directory with meeting number filename
- Add database migration for meeting_number column
- Add start.sh script for managing frontend/backend/sidecar services
- Update OpenSpec documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

openspec/specs/ai-summarization/spec.md

@@ -23,18 +23,30 @@ The AI summarization SHALL return structured data with conclusions and action it
 
 #### Scenario: Complete structured response
 - **WHEN** transcript contains clear decisions and assignments
-- **THEN** response SHALL include conclusions array and action_items array with content, owner, due_date fields
+- **THEN** response SHALL include conclusions array (0 to many items) and action_items array with content, owner, due_date fields
 
 #### Scenario: Partial data extraction
 - **WHEN** transcript lacks explicit owner or due_date for action items
-- **THEN** those fields SHALL be empty strings allowing manual completion
+- **THEN** those fields SHALL be empty strings or null allowing manual completion
+
+#### Scenario: Variable conclusion count
+- **WHEN** transcript has multiple decisions
+- **THEN** conclusions array SHALL contain all extracted conclusions without artificial limit
+
+#### Scenario: No conclusions found
+- **WHEN** transcript has no clear decisions
+- **THEN** conclusions array SHALL be empty []
 
 ### Requirement: Dify Prompt Configuration
-The Dify workflow SHALL be configured with appropriate system prompt for meeting summarization.
+The Dify workflow SHALL be configured with detailed system prompt for meeting summarization.
 
 #### Scenario: System prompt behavior
 - **WHEN** transcript is sent to Dify
-- **THEN** Dify SHALL use configured prompt to extract conclusions and action_items in JSON format
+- **THEN** Dify SHALL use configured system prompt to extract conclusions and action_items in JSON format
+
+#### Scenario: Flexible output count
+- **WHEN** Dify processes transcript
+- **THEN** it SHALL return variable number of conclusions and action items based on actual content
 
 ### Requirement: Manual Data Completion
 The Electron client SHALL allow users to manually complete missing AI-extracted data.

openspec/specs/excel-export/spec.md

@@ -15,30 +15,47 @@ The middleware server SHALL generate Excel reports from meeting data using templ
 - **THEN** server SHALL return HTTP 404
 
 ### Requirement: Template-based Generation
-The Excel export SHALL use openpyxl with template files.
+The Excel export SHALL use openpyxl with template files and cell coordinate mapping.
 
-#### Scenario: Placeholder replacement
-- **WHEN** Excel is generated
-- **THEN** placeholders ({{subject}}, {{time}}, {{chair}}, etc.) SHALL be replaced with actual meeting data
+#### Scenario: Cell coordinate filling
+- **WHEN** Excel is generated from template `meeting_template.xlsx`
+- **THEN** data SHALL be filled into specific cells:
+  - D3: meeting subject
+  - D4: meeting time
+  - D5: chairperson
+  - F4: location
+  - F5: recorder
+  - D6: attendees (comma separated)
+  - C8: meeting number (M-YYYYMMDD-XX format)
+  - D8: conclusions (newline separated if multiple)
 
-#### Scenario: Dynamic row insertion
-- **WHEN** meeting has multiple conclusions or action items
-- **THEN** rows SHALL be dynamically inserted to accommodate all items
+#### Scenario: Dynamic row filling for action items
+- **WHEN** meeting has action items
+- **THEN** rows SHALL be filled starting from row 10:
+  - Column C: action item system code (A-YYYYMMDD-XX)
+  - Column D: action item content
+  - Column F: owner
+  - Column G: due date
+  - Column H: status (Open/In Progress/Done/Delayed)
+
+#### Scenario: Template path resolution
+- **WHEN** export is requested
+- **THEN** server SHALL load template from `backend/template/meeting_template.xlsx`
 
 ### Requirement: Complete Data Inclusion
-The exported Excel SHALL include all meeting metadata and AI-generated content.
+The exported Excel SHALL include all meeting metadata, conclusions, and action items.
 
 #### Scenario: Full metadata export
 - **WHEN** Excel is generated
-- **THEN** it SHALL include subject, meeting_time, location, chairperson, recorder, and attendees
+- **THEN** it SHALL include subject, meeting_time, location, chairperson, recorder, attendees, and meeting_number
 
 #### Scenario: Conclusions export
-- **WHEN** Excel is generated
-- **THEN** all conclusions SHALL be listed with their system codes
+- **WHEN** Excel is generated with multiple conclusions
+- **THEN** all conclusions SHALL be merged with newline separator into cell D8
 
-#### Scenario: Action items export
+#### Scenario: Action items export with status
 - **WHEN** Excel is generated
-- **THEN** all action items SHALL be listed with content, owner, due_date, status, and system code
+- **THEN** all action items SHALL be listed with system_code, content, owner, due_date, and status
 
 ### Requirement: Template Management
 Admin users SHALL be able to manage Excel templates.
@@ -47,3 +64,18 @@ Admin users SHALL be able to manage Excel templates.
 - **WHEN** admin user accesses template management
 - **THEN** they SHALL be able to upload, view, and update Excel templates
 
+### Requirement: Meeting Number Generation
+The system SHALL automatically generate meeting numbers for each meeting record.
+
+#### Scenario: Auto-generate meeting number
+- **WHEN** a new meeting is created
+- **THEN** system SHALL generate meeting number in format `M-YYYYMMDD-XX` where XX is daily sequence
+
+#### Scenario: Meeting number uniqueness
+- **WHEN** multiple meetings are created on same date
+- **THEN** each SHALL receive unique sequential number (M-20251211-01, M-20251211-02, etc.)
+
+#### Scenario: Meeting number in export
+- **WHEN** Excel is exported
+- **THEN** meeting_number SHALL be displayed in cell C8
+

openspec/specs/meeting-management/spec.md

@@ -4,11 +4,11 @@
 TBD - created by archiving change add-meeting-assistant-mvp. Update Purpose after archive.
 ## Requirements
 ### Requirement: Create Meeting
-The system SHALL allow users to create meetings with required metadata.
+The system SHALL allow users to create meetings with required metadata and auto-generated meeting number.
 
 #### Scenario: Create meeting with all fields
 - **WHEN** user submits POST /api/meetings with subject, meeting_time, chairperson, location, recorder, attendees
-- **THEN** a new meeting record SHALL be created with auto-generated UUID and the meeting data SHALL be returned
+- **THEN** a new meeting record SHALL be created with auto-generated UUID, meeting_number, and the meeting data SHALL be returned
 
 #### Scenario: Create meeting with missing required fields
 - **WHEN** user submits POST /api/meetings without subject or meeting_time
@@ -18,6 +18,10 @@ The system SHALL allow users to create meetings with required metadata.
 - **WHEN** user creates meeting without specifying recorder
 - **THEN** the recorder field SHALL default to the logged-in user's email
 
+#### Scenario: Auto-generate meeting number
+- **WHEN** a new meeting is created
+- **THEN** meeting_number SHALL be auto-generated in format M-YYYYMMDD-XX
+
 ### Requirement: List Meetings
 The system SHALL allow users to retrieve a list of meetings.
 
@@ -63,7 +67,11 @@ The system SHALL allow authorized users to delete meetings.
 - **THEN** the meeting and all related data SHALL be deleted
 
 ### Requirement: System Code Generation
-The system SHALL auto-generate unique system codes for conclusions and action items.
+The system SHALL auto-generate unique system codes for meetings, conclusions, and action items.
+
+#### Scenario: Generate meeting number
+- **WHEN** a meeting is created on 2025-12-10
+- **THEN** the meeting_number SHALL follow format M-20251210-XX where XX is sequence number
 
 #### Scenario: Generate conclusion code
 - **WHEN** a conclusion is created for a meeting on 2025-12-10