fix: ChatBubble crash and DeepSeek API compatibility

- Fix ChatBubble to handle non-string content with String() wrapper
- Fix API route to use generateText for non-streaming requests
- Add @ai-sdk/openai-compatible for non-OpenAI providers (DeepSeek, etc.)
- Use Chat Completions API instead of Responses API for compatible providers
- Update ChatBubble tests and fix component exports to kebab-case
- Remove stale PascalCase ChatBubble.tsx file
This commit is contained in:
Max
2026-01-26 16:55:05 +07:00
parent 6b113e0392
commit e9e6fadb1d
544 changed files with 113077 additions and 427 deletions

View File

@@ -0,0 +1,94 @@
---
name: 'step-02-file-structure'
description: 'Validate file structure compliance'
nextStepFile: './step-03-module-yaml.md'
moduleStandardsFile: '../../data/module-standards.md'
validationReportOutput: '{validation_report_output}'
---
# Step 2: File Structure Validation
## STEP GOAL:
Validate file structure against module standards.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Quality Assurance** — checking structure
- ✅ Reference standards, ensure compliance
---
## MANDATORY SEQUENCE
### 1. Load Standards
Load `{moduleStandardsFile}` for reference.
### 2. Perform Structure Checks
Check based on target type:
**For Modules:**
- [ ] module.yaml exists
- [ ] README.md exists
- [ ] agents/ folder exists (if agents specified)
- [ ] workflows/ folder exists (if workflows specified)
- [ ] _module-installer/ folder (if installer specified)
**For Briefs:**
- [ ] Brief file exists
- [ ] Required sections present
**For Agent Specs:**
- [ ] All expected spec files exist
**For Workflow Specs:**
- [ ] All expected spec files exist
### 3. Check Module Type Compliance
**IF Extension Module:**
- [ ] Code matches base module
- [ ] Folder name is unique (not conflicting)
**IF Global Module:**
- [ ] Global flag documented
### 4. Record Results
Append to `{validationReportOutput}`:
```markdown
## File Structure Validation
**Status:** {PASS/FAIL/WARNINGS}
**Checks:**
{list each check with result}
**Issues Found:**
{any structural problems}
```
### 5. Auto-Proceed
"**✓ File structure check complete.**"
Proceeding to next validation...
Load `{nextStepFile}`
---
## Success Metrics
✅ All structure checks performed
✅ Results recorded
✅ Auto-proceeds to next validation