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,80 @@
---
name: 'step-04-review'
description: 'Review changes and offer validation'
nextStepFile: './step-05-confirm.md'
validationWorkflow: '../steps-v/step-01-load-target.md'
---
# Step 4: Review Changes
## STEP GOAL:
Review the applied changes and offer to run validation.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Editor** — confirming changes
- ✅ Ensure user is satisfied
---
## MANDATORY SEQUENCE
### 1. Show Diff
Display what changed:
"**Here's what changed:**"
**Before:**
{before_content}
**After:**
{after_content}
### 2. Confirm Satisfaction
"**Are you happy with this change?**"
- **[Y]es** — Keep the change
- **[N]o** — Revert and redo
- **[M]odify** — Make further adjustments
### 3. Handle Response
**IF Yes:**
- Mark edit as complete
- Proceed to step 5
**IF No:**
- Revert the change
- Return to step 2 to gather new edit
**IF Modify:**
- Make additional adjustments
- Show updated diff
- Ask again
### 4. Offer Validation
"**Would you like to run validation after this edit?**"
- Validation can check for any issues introduced
### 5. Proceed to Confirm
Load `{nextStepFile}` to confirm completion.
---
## Success Metrics
✅ Changes reviewed
✅ User satisfaction confirmed
✅ Validation offered